Adobe Premiere Pro Encoding Error

[Lucrecio Houle]

Theknown issue of NVIDIA and Premiere Pro not working together and crashing has been causing me more issues than just crashing. I first ran into error code 39, then it started giving me other errors that I don't exactly remember what they said, though it exported 1 video 3 times when I clicked export once, and all of the videos were corrupt files. I also ran into this problem last night while trying to export the same video, waiting around 10 minutes for the 100% to go away and give me the notification that it had been exported, but I got tired of waiting, tried canceling, and Premiere crashed.

The issue I had is that my harddrive/storage was full. I deleted some files and the file exported successfully. Right click your harddrive and select properties(windows) and make sure you have enough space for the new exported file to save on the harddrive. I recommend freeing up double the space of the new file.

So I have about a 15 minute long video that I am trying to export but for some reason it is failing to export every single time and it is always near the end of the video and I can't work out why. I get 39 and I am writing with exporter H.264. The file type is H264 and the average timecode when it fails to finish the encode is 00:15:17:13. The video is mp.4 and the audio is AAC. Please help!

I worked aroudn this by choosing software render instead of using hardware render. Donwside: render time multiplied by 5. Adobe, any idea on when this will be solved? Is it really an Nvidia issue? Are you coordinating to solve it?

same issue on most current version of nvidia game ready, and studio drivers. tried rolling back to studio and game ready from feb 2023, same issues, tried rolling back to version that adobe recommends, same issues. several restarts and reinstalls of everything as well. cannot fix this issue. please help adobe.

I started getting exactly the same issue yesterday in the evening. Before that all worked perfectly fine. I have NVIDIA Ge Force GTX 1050 Ti, the system says that drives are up to date. Just updated the Premiere itself, the issue remains.

I dropped Premiere and Encoder back to 23.2 and it is still failing. Just like someone else said (and verified in the log), it almost gets done, then fails. AMD proc, NVIDIA 2070 super, Win 10, tried both game and studio drivers on previous version. Error report follows:

@Raz295366934cp2 [I've tried everything people have suggested on the thread] what suggestions, I just see post saying 'same thing here'. How about some file type info, editing with h.264? (Bad choice). Since there seems to be no suggestions, I would for certain try deleting my cache. 3 people mentioned a version#. Mac or PC. We need more to go on.

Did you try exporting to a different format? If you've been using h.264 exports try to export in ProRes. Maybe LT or even Proxy. If that works you could make a 264 from there. ProRes files are typically visually lossless. Since most of you didn't specify a version, I'll give you this method to delete the cache.

Thank you for the reply!

Well I guess they weren't suggestions, just what other people were trying. And I'm using a PC, file type I've been using is h.264 I've never had a problem exporting videos around 30 mins long before, but I've just done one for 1 hour and 40 mins and thats the one I get the error on and doesn't seem to work.

I've followed your instructions and deleted all media cache, I tried exporting again and still had the same problem but I'll try changing the format , I'll try ProRes first and hopefully that does it. I only use h.264 because for some reason I thought it was one of the best formats to use for uploading on YouTube. But I'm guessing thats not the case.

2. Is there a way to fix this error? It seems to export occassionally to my C drive (which is not raid) but it fails to my F drive (Raid 10). But usually if I export as a wmv or something smaller it exports fine to F.

The export dimensions do not default to 1920x1080 because AME CS5.5 and prior versions do not have h.264 presets for QuickTime for the program ot default to, and the individual settings for that format do not have a "Same as Source" option. If you will be using a particular set of settings regularly, I recommend saving a custom preset. To do so, click the Save Preset button to the right of the Preset pulldown in the Export Settings dialog.

Sorry it took so long to get back to you I had to go out of town. Error message doesn't say anything to me... maybe to you. I'm not really sure what to set for "Field Type" so I just leave it at Lower. Not sure if I should set it to higher or progressive instead.

excuse me but im having this problem too i was just encoding my last video and it randomly stopped.. after i tried doing it again it randomly keept failing.. i dont have the file saved so i need it coded please help!

Having the same problem, I'm actually running latest CC version on windows 10. Oddly I have a laptop that doesn't fail to encode FullHD .mov h.264 files. So I always have to copy my files and encode them on my laptop. Any solutions so far?

i, too, have been having trouble rendering a video. it is only 1 minute. (i have since the summer been unable to render longer videos--i usually don't do videos over 6 minutes. but i found that i could do very short videos.)

When I get render errors, I go in to the program folders and manually delete all media cache files and previews. It has worked every time for me. You can try going in from >edit>preferences>media>clean, But I found that a manual clean usually works best.

hello! idk what to delete from the program folders after i tap on the media encoder one, bc idk which one are the media cache files/previews, pls pls help ive been trying to export my edits for 2 months and they keep failing ?

Hey im actually quite new to the forums. even though this thread is really old for like so many years, i actually came across this same problem today 07. 09. 2020. And after going through the forum i found a solution. I got the same issue trying to render ia media encorder 2020 gave me a failed icon and when i clicked it the log was empty. it just showed me the yellow failed icon. solution is to change the location that has more space. i was keep trying to export into my C drive it only had 90GB free, then i switched it to my D drive which had almost 200 gigs free it exported smoothly without an error. Hope this helps if anyone come across this same problem even after years.

Thank you for this response. I was having a similar issue when attempting to encode my annual video. And it would always fail, but at different times in the encoding process. I found that somehow the cache got switched to my OS drive as well, and changing it back to the dedicated media cache drive resolved it. In my case I did have enough disk space on the OS drive to handle the cache, but it was still failing anyway.

I think I solved the problem. For me, I got the error, failed was when I used the WMV pre-set created by Adobe. When I customized the pre-set, I changed audio and video from VRB to CRB, I was able to export without failure.

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.

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 had the same problem and found it to be a corrupt .png 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.

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.

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.

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 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)

3a8082e126