Код ошибки 1609629695 adobe media encoder
Способ №1. CCleaner
Самое простое решение заключается в том, чтобы воспользоваться программой для чистки реестра. Как это работает?
Все просто – чистильщик реестра, собственно, и предназначен для того, чтобы исправлять всевозможные проблемы, вроде той, которую рассматриваем мы, систематизировать файлы и добавлять то, чего недостает ему для нормальной работы.
Лучшей по праву считается CCleaner, хотя вы можете воспользоваться и другой.
Способ №2. DirectX
Вполне вероятно, что ее появление вызывают какие-то проблемы с DirectX. Возможно, какие-то файлы исполняемых библиотек были повреждены или же существующие библиотеки банально устарели.
В любом случае, лучше всего просто установить наиболее актуальные варианты и, опять же, перезагрузить компьютер.
Для этого зайдите на сайт Microsoft, на страницу с возможностью скачать DirectX ( вот ссылка ). Запустите скачанный файл и выполните все действия, подразумевающие установку исполняемых библиотек. Здесь нет никаких особых рекомендаций – обычная. Если после установки и перезагрузки компьютера ошибка не исчезла, идем дальше.
Способ №3. Visual C++
Бывают в данном случае и другие ситуации, когда установленная C++ попросту не подходит для вашей операционной системы. Ниже приведена таблица с вариантами, которые подходят для разных версий ОС.
Так вот, в зависимости от того, какая у вас ОС, вам следует скачать и инсталировать на свой компьютер C++2008, C++2010, C++2015 или новее.
Ошибка Adobe Media Encoder не установлен
Adobe Media Encoder – это мощный инструмент предназначен для перекодировки мультимедийных файлов в любой формат. Но иногда при работе с приложением можно столкнуться с ошибкой, что Media Encoder не установлен. Ошибка проявляет себя в двух случаях: когда приложение установлено и во время обращения с другой программы.
Почему возникает ошибка
Есть несколько причин, из-за которых система выбрасывает уведомление, когда не может получить доступ к приложению.
Установка Media Encoder
Уведомление об ошибке вполне уместно, если действительно не установлено приложение Media Encoder. Некоторые продукты Adobe требуют функцию кодирования для полной функциональности.
Перейдите на официальный сайт Media Encoder и загрузите установку в любое место на диске. Также программу можно загрузить прямо из Creative Cloud.
Кликните правой кнопкой мыши на исполняемый файл, выберите «Запуск от имени администратора». После установки перезагрузите компьютер и проверьте, остается ли проблема.
Каталог установки по умолчанию
Для решения проблемы попробуйте вручную переместить приложение обратно в каталог по умолчанию:
Если после переноса ошибка остается нужно выполнить такие действия:
Откройте Creative Cloud и удалите все программы, которые переместили вручную в другое место.
После завершения заново установите приложение из Creative Cloud. Прежде проверьте, что каталог назначен по умолчанию. Нажмите на значок шестеренки в верхнем правом углу, затем выберите «Установки». Здесь проверьте правильно ли выбран каталог.
После переустановки перезагрузите компьютер. Проверьте, остается ли проблема.
Изменение каталога установки через командную строку
Во-первых, убедитесь, что версии компонентов обоих модулей совместимы друг с другом.
В консоли командной строки введите команду:
Удаление продуктов Adobe CC
Если все перечисленные методы не работают, то возможно продукты СС повреждены или имеют неправильную структуру. Для этого их нужно полностью удалить, а затем попробовать переустановить их заново. Для этого решения потребуется учетная запись Creative Cloud.
Откройте официальный сайт Adobe CC Cleaner Tool. Затем выберите версию установленной на ПК операционной системы. В нашем случае Windows.
После выбора ОС выполните следующие действия. Нажмите комбинацию Windows + R, впишите команду appwiz. cpl и подтвердите вход в раздел Удаления / Изменения программ. Найдите Adobe CC и после клика по нему правой кнопкой мыши выберите «Удалить».
Теперь перейдите к 6-му шагу и загрузите исполняемый файл в доступное место.
После завершения загрузки кликните правой кнопкой мыши по исполняемому файлу и выберите Запуск от имени администратора. Отобразится командная строка со списком параметров. Выберите вариант в соответствии с проблемой и нажмите Enter.
Теперь инструмент очистки полностью удалит программу с компьютера.
Перезагрузите ПК и снова установите Creative Cloud. Затем инсталлируйте инструменты, включая Media Encoder и проверьте, возникает ли ошибка.
Welcome to the Community!
We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.
Adobe Support Community
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.- Home
- Adobe Media Encoder
- Discussions
- AME error code -1609629695
Copy link to clipboard
Hi, I'm using AME to render my video from After Effects.
I used to get the same error code for the renders (-1609629695) all the time, but all of sudden it was working fine for a few renders.
And now I'm getting the error again.
For different compositions, this has been occuring often, and I couldn't figure out what is causing this error or find any information about this online.
I'm using AME CC 2018 version 12.1 / After Effects CC 2018 version 15.1.0
Processor Intel(R) Xeon(R) CPU E3-1505M v5 @ 2.80GHz, 2801 Mhz, 4 Core(s), 8 Logical Processor(s)
Windows Version 10.0.15063 Build 15063
Intel HD graphics P530
NVIDIA Quadro M1000M
and here's what I get about why my rendering is failing
- Encoding Time: 00:00:41
11/28/2018 04:00:20 PM : Encoding Failed
Error compiling movie.
Render returned error.
Writing with exporter: H.264
Writing to file: \\?\C:\Users\seungmi_lee\Documents\Personal Project\deliverable-test\asset\WIP\wip_AME\scene-07_1.mp4
Writing file type: H264
Around timecode: 00;00;08;18
Rendering at offset: 4.037 seconds
Component: H.264 of type Exporter
Error code: -1609629695
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
Hi there, Seungmeelee!
Here are some threads that have had similar issues. Please try these ideas while I look into this error for you!
- Make sure your NVIDIA GPU card has the latest drivers installed. Check the NVIDIA site directly to see if there's a newer driver available for your model.
- Try a different GPU setting in the Renderer menu at the bottom of the Queue panel. If it's set to "CUDA", try "OpenCL" or "Metal" and re-import your sequence or source media. If that doesn't help, try "Software Only" rendering to bypass the GPU.
- If you have a Logitech webcam installed, remove it and uninstall any related drivers/software
- If you're exporting to H.264 or HEVC, check if "Hardware Encoding" is enabled in export settings.
Let me know if any of these ideas work for you!
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
Thanks for your comment, but I tried everything but none of them is working for me.
I'm curious if there's any way we can figure out what the error code means, cuz I'm getting that error code in every render failure.
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
I've done some more research and found other similar threads with a lot of different workarounds.
The common denominator seems to be an issue with the GPU that's doing the rendering.
I've also collected a YouTube tutorial that's worked for some users but not others.
And a uservoice post!
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
i7-3770k / Asus Maximus V Formula / DDR3 Corsair 16gb / SSD Samsung 750 Evo 250Gb / EVGA 1080 Ti FTW3
Windows 10 x64 (1809) / Adobe Media Encoder CC 2019 (13.0.2)
I have the same problem. Disappears only if I increase the paging file to 50GB
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
Thanks for trying all the suggestion provided above. You've mentioned that the error disappears when you increase the paging file size to 50GB. I would recommend having a look at this article: How to fix issues that cause errors when rendering or exporting
Clearing up space in your hard drive is the first thing that Adobe suggests in case of export errors.
Is that the same step that you tried? Please go through it and check if there is anything else that can be done.
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
I have 100GB free on my system hard drive. On the disk where I export video 500GB free.
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
i had the same Problem. i cleared mediacache of AE,PR and Mediaencoder, but ive got the same issue. After reinstalling quicktime and restarting AE and mediaencoder it works.
Hope it workes for you too!
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
Thank you! It works!
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
What drivers are you using? when you said "restarting AE and AME" did you mean you unistall and install them again?
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
Hi Yerick10, with restarting AE and AEM I meant: closing aftereffects and mediaencoder and starting them again. I’m not sure which driver i had installed at that time. I think for the graphics card it was the default driver of NVIDIA.
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
Same error here. Started when I switched to a new pc.
Render returned error.
Writing with exporter: H.264
Writing to file: \\?\C:\video\lam-gods-master_2_3.mp4
Writing file type: H264
Around timecode: 00:00:09:04 - 00:00:09:20
Rendering at offset: 9,133 seconds
Component: H.264 of type Exporter
Selector: 9
Error code: -1609629695
Copy link to clipboard
In my experience, this error often appear when one file of a sequence asset is corrupted.
for exemple if a jpeg file in sequence is corrupted, it will be fail when it will try to encode this frame.
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
Reading some other forums I found that the combination of the Hue/Saturation effect and blur can effect the encoder with this error (or sometimes just Hue/Saturation on its own). By using the search feature in the layers panel - I click+drag turned off all of the Hue/Sat effects on my layers, let the preview refresh a frame, then turned them all back on again. For whatever reason - now exporting to encoder isn't crashing with this error.
Another thought for people who maybe stumble upon this, try turning your effect on your layers off (to test) and see if that does anything. then at least you have another troubleshooting idea
Welcome to the Community!
We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.
Adobe Support Community
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.- Home
- Premiere Pro
- Discussions
- Error code: -1609629695 PREMIERE AND MEDIA ENCODER.
Copy link to clipboard
Premiere and Media Encoder have been giving me a lot of trouble lately, both returning the same error code.
Here's a screenshot of the error:
My sequence is a 4K 24p created directly from the "New Sequence from clip" feature. I heavily used Warp Stabilizer and Lumetri Color. I've disable the stabilizer, yet it still crashes when I'm trying to work on color grading.
Here are my computer specs:
GTX 960 3GB VRAM
OS on an SSD, everything else on separate HDDs.
Can someone please help me identify the source of my problem? And let me know if you need more information about my project sequence or anything!
Thank you in advance! : )
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more1 Correct answer
Adobe Community Professional , Jul 29, 2017 Jul 29, 2017 R Neil Haugen • Adobe Community Professional , Jul 29, 2017 Jul 29, 2017 Ok . first question . is this the same on different projects, or have you only been working the one project?If only on this project, create a new project, via the Media Browser panel import a few assets, and test there. If on multiple projects created in this version of PrPro, well . skip that.Next, what's the media involved in your projects? Frame-size/rate and created by what . camera, phone/device, screen-capture?And last . do you have the same problem if you go into the project set.Copy link to clipboard
Ok . first question . is this the same on different projects, or have you only been working the one project?
If only on this project, create a new project, via the Media Browser panel import a few assets, and test there. If on multiple projects created in this version of PrPro, well . skip that.
Next, what's the media involved in your projects? Frame-size/rate and created by what . camera, phone/device, screen-capture?
And last . do you have the same problem if you go into the project settings and set Mercury Acceleration to "Software Only"?
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
It's all the same project, I've imported my Premiere project into AE for further editing and met with the error when I tried to export out with AME. I've done this all before, the problem has just shown up now.
I also get this issue when I try to render previews in Premiere, but it only seems to happen with clips that have Lumetri Color and Stabilizer stacked.
I use a Panasonic GH5, shooting 3840x2160 UHD 4K. I shoot in 8 and 10-bit 60fps and 24fps respectively. I haven't tried the software only—I'll give that a shot!
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
Hey Neil, I exported it using software only, and it worked!
Thanks so much for your help, cheers!
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
I had the same problem and found it to be a corrupt .jpg file that had some motion and a mask on it. I deleted it, brought a new one in. Created a new comp, replacing the old with the new and it rendered fine.
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
I have had the same issue periodically over the last while -
Originally, this was happening to me when I used LUTS that i had made myself, and imported into Premiere. This was fixed, when I exported my colour settings as a Premiere LUT. I now use Premiere LUTS that I made myself, and have been for about a year.
As of this week, (premiere was recently updated to Version 12.1.2 Build 69 ) I've been getting the error code again. My issue isn't with rendering or exporting (for now, it was in the past), it's that random clips in the timeline will go blank until I remove effects, and reapply them again. Issue temporarily resolves if I restart Premiere, but doesn't fix it. Creating a new project and importing the sequence does not change anything either. Switching to software rendering gives me the lovely red and white checkerboard, instead of just blank clips. What's very weird is that I exported this project, and have now gone back to it to make changes, and these errors are suddenly all over my timeline.
Any help would be much appreciated!
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
That's a frustrating issue, and what you're getting is just . weird. Wow!
File this over on the UserVoice system, where they track (and now often even respond!) to bugs . it's vastly improved.
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
Now, if I have a clip selected in my timeline, and just click in to the Lumetri module, the clip disappears. But it's not every clip, and there doesn't seem to be a pattern. If I remove all effects, it returns - but if I simply just click to adust exposure (no LUTS or other effects at all) it goes blank in the timeline.
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
Um . wow . that's so unique I've never heard of that behavior before. An engineer approach might be to say you should feel special as he/she sits down to examine this.
Most editors would prefer to deal rather harshly with such thoughts however.
And I do hope you update your UserVoice filing with this information. This is so bizarre, want this puzzled out.
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
Here is the solution! It has to do with GPU. You must change in File->Project Settings->General->Renderer to . Software only, next delete preview files in a project folder and here you go!
Copy link to clipboard
I tried this and the error still pops up
Export Error
Error compiling movie.
Render returned error.
Writing with exporter: H.264
Writing to file: \\?\C:\Users\Herman\Desktop\Who Are We_AME\Main.mp4
Writing file type: H264
Around timecode: 00:07:00:27 - 00:07:01:05
Rendering at offset: 420,900 seconds
Component: H.264 of type Exporter
Selector: 9
Error code: -1609629695
Any help please??
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
I have this issue as well. Using custom LUTs for a project. I've tried disabling the LUTs and the issue still arises. At first I only had the issue in AME so was exporting from Premiere, but now I am also getting it from Premiere. Both are updated. When I monitor the export in Task Manager, the GPU is maxing out in the 80-99% level.
I've tried many different things to figure out the issue, only thing that has worked is exporting in pieces and stitching together to reexport. These are only 10-30 min videos. I have some simple effects like luma curve masks, blur, cross fades, some audio denoise effect. That's it. I'm working with multicam sequences and 1080 proxy files.
The error messages I get are -1609629690 and -1609629695
Here are my computer specs:
CPU Intel Core i7-8700K
Here is an example error messages:
- Encoding Time: 00:10:37
12/10/2020 12:26:32 PM : Encoding Failed
Error compiling movie.
Render returned error.
Writing with exporter: H.264
Writing to file: \\?\C:\Users\. \. \. _CH2.1_RC2_201209.mp4
Writing file type: H264
Around timecode: 00:04:08:20 - 00:04:09:20
Rendering at offset: 249.082 seconds
Component: H.264 of type Exporter
Error code: -1609629695
- Encoding Time: 00:00:02
12/12/2020 08:54:10 AM : Encoding Failed
Offline media was encoded using proxies.
Missing Asset: A001_11221357_C003_. braw
Missing Asset: B001_11221357_C003_. braw
Error compiling movie.
GPU Render Error
Unable to process frame.
Writing with exporter: H.264
Writing to file: \\?\A:\. \. _CH2.2_RC2_201211.mp4
Writing file type: H264
Around timecode: 00:00:00:08 - 00:00:01:01
Rendering effect: AE.ADBE Opacity
Rendering at offset: 0.000 seconds
Component: EffectFilter of type GPUVideoFilter
Error code: -1609629695
- Encoding Time: 00:02:03
12/12/2020 08:56:31 AM : Encoding Failed
Offline media was encoded using proxies.
Missing Asset: A001_11221357_C003_MICROHZ.braw
Missing Asset: B001_11221357_C003_MICROHZ.braw
Error compiling movie.
Accelerated Renderer Error
Unable to produce frame.
Writing with exporter: H.264
Writing to file: \\?\A:\. _RC2_201211.mp4
Writing file type: H264
Around timecode: 00:00:17:02 - 00:00:18:02
Rendering at offset: 17.100 seconds
Component: H.264 of type Exporter
Error code: -1609629690
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
Where are your LUTs stored on the computer?
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
The LUTs are custom made by the company I am editing for. I dropped them in C:\Program Files\Adobe\Adobe Media Encoder 2020\Lumetri\LUTs\Creative and in the same spot for premiere. Other people editing with these luts haven't reported issues. I was able to use them successfully up until yesterday for some reason when using premiere. I tried exports with them disabled and had the same issue. I also have a blackmagic effect on masterclips that I disabled (but since I'm working with proxies, the black magic reader is not important for my editing)
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
Never, ever, EVER put LUTs in the program/package folders! It's asking for all sorts of headaches. The app uses relative use of those folders . as in, the 15th one down in computer-sorted order. NOT by name! And it expects the same things to be in the various apps.
Use the system provided for adding LUTs into the system. The following chart shows the areas to use, and for some reason they make you add the final folders, the Technical (Basic tab use) and Creative (Creative tab use). Park them there, and they will pop up in the appropriate list drop-down.
I add a prefix system to mine so they always come up grouped as I want at the top of the list.
So remove them from those folders, put them in the proper ones, and apply from there.
The other thing . is if you're using the BlackMagic plugin, well . that one can be problematic at times. I finally gave up and got the Autokroma BRAW Studio plugins. So . realistically, this could be an issue also.
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
Well I'll be damned. I took your advice and moved the LUTs all to C:\Program Files\Adobe\Common\LUTs and created the two folders, placing my LUTs in Creative. That works. Thank you.
I still have the export issue on certain sequences with the AME exports failing. I've disabled blackmagic in premiere but that had no effect I can see. Maybe I'll try uninstalling. After rendering one sequence it sent fine to AME and exported, but that was a sequence with less effects applied. If I don't render they just fail. I think effects are part of the problem but I haven't had issues with effects in the past so unsure why now, and I'm not adding anything crazy, just some simple crossfades, blurs and vignettes. I'm guessing the proxy linking and/or blackmagic and LUTs are the source of my ordeal.
I appreciate your help, Neil!
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
I had occacional issues of oddness, and finally Nicolas from Autokroma asked me if the BM plugin was still listed in the project plugins. Yea, it was, hadn't even seen it, though I'd not used that in months. Had to go hunt it down & kill it, dump all cache files, then go through my projects. A couple I needed to create a new project file & then import the old project.
Took care of some of the crazies at least.
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
I have the same problem trying to r5ender a after effects file with media encoder. or render with a linked comp in premiere.
I try to export in 6k prores422. but that didn't work 4k didnt work eiteher. Even an other machine didnt help.
Computer specs are AMD Ryzen 5 2600 6 core 32gb gddr4 ram an rtx2070 8gb vram.
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
No clue what's happening on your machine, as you haven't included any details.
What media are you working with, what are you doing to it for effects, is this direct from Ae or a dynamically linked comp from Ae on a Premiere sequence, does it render directly from Premiere, and when whatever doesn't work doesn't work, what were you doing, and what potential error message or behavior occurred instead of what you expected?
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
The underlying reason for this error is running out of VRAM for your GPU accelerated effects. The "Around Timecode" is usually the failure point. If you are working with big resolutions, you simply need to throw a bigger GPU at it and your issue will be solved. Using a smart rendering workflow, you can workaround your underpowered system by attacking at a different angle (rendering up front, and then using those renders for output - therefore, bypassing any GPU limitations that crop up during export). I hope that makes sense.
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
Hi, we are also having the same problem.
Here is the error code.
Encoding Time: 00:15:40
04/13/2021 08:05:53 PM : Encoding Failed
------------------------------------------------------------
Export Error
Error compiling movie.
Accelerated Renderer Error
Unable to produce frame.
Writing with exporter: H.264
Writing to file: \\?\L:\1_Clients\UP\Graduations\Graduation 2021\Autumn Gradution\Project\Export\Part 6\Part 6 - VETERINARY SCIENCE.mp4
Writing file type: H264
Around timecode: 00:01:49:02 - 00:01:50:09
Rendering at offset: 109,080 seconds
Component: H.264 of type Exporter
Selector: 9
Error code: -1609629695
Export Error
Error compiling movie.
GPU Render Error
Unable to process frame.
Writing with exporter: H.264
Writing to file: \\?\L:\1_Clients\UP\Graduations\Graduation 2021\Autumn Gradution\Project\Export\Prof Kupe Speech_E2.0.mp4
Writing file type: H264
Around timecode: 00:00:29:11 - 00:00:30:18
Rendering effect: AE.ADBE Cross Dissolve New
Rendering at offset: 29,440 seconds
Component: TransitionFilter of type GPUVideoFilter
Selector: 9
Error code: -1609629695
We are experiencing it on multiple different computers. We are unable to set to software only for rendering as it causes glitches in the export (strangely it causes those on an mp4 file in the sequence). This problem persists even if we move to a hard drive or work from the NAS device or directly from an SSD.
Here are the specs for the PCs:
Windows 10 Pro 64 bit
Windows 10 Pro 64 bit
Windows 10 Pro 64 bit
Windows 10 Pro 64 bit
There are 3 different projects both have dynamic links to after-effects, lumetri colour, and warp stabiliser on some clips:
Project 1: Only renders on PC 2 but does not render on PC 1 at all. All the settings were identical for export and in the project and the computers are identical.
Project 2: This has dynamically linked after effect files and green screen in the after effects. Unable to render on software only as there are colour glitches (it discolors the image on certain sections) on mp4 files in the sequence that has no effects on it at all. The project is unable to render on PC-1, 2 and 3 and only renders on PC- 4. When set to render on PC 2 is complete;y unable to render from the start and then PC 1 starts rendering and says 4 hours to complete the render but always fails. PC 4 has no problem. This project does not even open on PC 5.
This had no green screen and only some dynamically linked after-effect files. It was a 4 hour long sequence. It was unable to render on any of the PCs GPU or software, and this rendered on PC 5 only.
Please assist. These are top-of-the-line CPUs and GPUs on various machines with various projects. I don't understand why the smallest PC is able to export while the larger ones are absolutely useless. The rules are never the same for these errors. It might export happily on the one PC then the next day it refuses on that one and only exports on another. No regard for size of GPU or CPU.
Lately in Premiere Pro 2017.2, I keep getting a GPU render error when I have Lumetri on clips. Render error 1609629695. I have Geforce GTX 980, all drivers updated. Once in a while it will work fine but I keep getting this error message. Any help or advice?
Here are five questions to help people help you:
What operating system are you using?
What is your premiere build version?
What are your system specs?
What is the source footage format/codec?
If there is an error message, what exactly does it say?
Please reply to this with your answers. Thanks.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
Using a GTX 980, Intel i7-5820, 32gb Ram. Samsung SSD 850 Pro, Samsung 950 NVMe
1609629695 - GPU Render Error. Only happens when Lumetri is Applied.
Export your video as DNxHR HQ (quicktime > DNxHR/DNxHD. Second dropdown above resolution, choose DNxHR HQ. Match settings.) Then encode that to h.264.
Also, does rebooting help? Is your GPU overclocked? Remove the overclock, let the card handle itself.
Is this an older sequence perhaps? Try making a new project, import the old, make new sequence, copy & paste all from old into new.
Also, are you using Lumetri on the clips or on an adjustment layer? Try switching the method.
Some have fixed this by deleting their cache files.
Could also be the video drivers-- try rolling back to 382.53 or older.
Some nVidia cards come factory overclocked. Try a bit lower speed w/ MSI Afterburner or EVGA Precision.
Last, you should be able to get around it (if nothing else works) by disabling CUDA.
Читайте также: