Exporting long video consistently failing at the end

[MATTHEW5CD8]

I've been trying to export a very long project for a few weeks now and could use some help figuring out why it is crashing. The video is a VOD from a 24 Hour long charity livestream I did, and all I really did was stitch the two parts of it together and adjust some audio levels. Every time I attempt to export using the Youtube 1080p full HD preset, with consistency, it fails with the timestamp being exactly one frame before the very end of the video. You can imagine how infuriating this is, being that it is nearly a 24 hour long video, it takes a very long time to process each time it fails.

I have attempted to export via media encoder with hardware encoding on, and ive attempted software encoding only. I've also tried both methods as a direct export from premiere instead of queueing into ME. I have also tried trimming a few frames off the end of the video, but the new error timestamp is always at the second to last frame no matter the edit. I'll post the error code information and my system specs below. If anyone could help me figure this out I would be eternally greatful. I've wasted a significant amount of time just trying to export this and I feel stuck. If you need any other information please let me know. Thanks!

Error Info:

Error Compiling Movie
Export Error
A low-level Exception has occurred

Writing with Exporter H.264
Around Timecode 23:59:14:26
Selector: 9
Error Code: 3

System Info:

OS: Windows 10 x64

Pr Version:15.2

Specs:

CPU: Ryzen 3600XT
GPU: Sapphire Nitro+ Radeon 5700XT
RAM: 8x4(32)GB Corsair Vengance Pro DDR4 @ 3600Mhz
Premiere installed on M.2 NVME SSD

Exporting to 2TB HDD with 1.11TB free

Raw File format: MP4

[FlyingFourFun]

I couple of quick questions.

what's the total size of the video you are sticking together?  is it around 500gb (0.5tb)?

The reason I ask is that I have noticed that in some exports, it will export the entire file, then create a second copy of about the same size, then mux the files together, delete the extra one.

so, the message you're getting might be 'out of free space'.   

Here is a link to a post earlier that seems to align with your issue:

Solved: Error Code 3 - Error compiling movie - Export erro... - Adobe Support Community - 11613255

I have also corrected the same error code myself by triming a few frames from the start or end of clip around the time code error location.  It might be a frame or two that the encoder doesnt like.  Which might explain why switching to software encoder works too.  There is a bit of trial and error.  This link included talks about a few thinks I think will help you if its not the out of drive space (with your 24 hour I felt that might be more likly which is why I went there first).

[MATTHEW5CD8]

The raw footage consists of two videos, one at 7:12:57 and 18.6GB, and the other is 17:11:29 and 44.4GB for a total of 63GB. I cant remember exactly but I remember deleting a failed file recently that I believe was around 153GB. Estimated file size on the export screen right now says 176172 MB.

[FlyingFourFun]

Sounds like you're not running of disk space.

Can you scroll through the other post I linked in and see if one of those solutions helps you?  there are several ideas people tried, doesn't seem like a pattern of success that works every time, but different solutions worked for different people with the same error codes you are seeing.

My personal experience has been bad frames or at least frames the hardware encoder didn't like.  Cutting them out saved my project.  I ran a render preview for the whole thing, and often the process failed, btu I could see that last successful clip, fix the not rendered one, by cutting a few frames until it finished.   with 24h of footage it doesn't sound like fun to do it this way. I was annoyed with just the 20 min clip I had.

[MATTHEW5CD8]

I agree it seems that it has something to do with the encoding of the actual frames rather than the disk space. I suppose my only solution is to keep cutting out parts and trying to export until it works. It is gonna be a pain but that seems to be the only way to go. I appreciate your help.

[FlyingFourFun]

I am wondering if you used the timeline in out points and cut that video into 4 to 8 parts, render those out and find another program to stich them together.  In that process, you would find the section of the video that is causing you grief and keep rendering parts of that section until you find the exact time code?

I imagine your timeline is the clips and no effects or them, no fades or anything?

Your trouble shooting is compounded by the fact this is such a long clip and rendering to find the problem area sucks up so much time.  If you could narrow it down to the precise problem area somehow it would really save you time applying a fix.

Have you tried to build a new project, and literaly copy the timeline to the clipboard, and past it into the new project?

If your source files were not so big, I would offer to [try] render it out for you to help you out.   hell, if worst comes to worse for you, I will leave that offer open (since its a charty event).

[MATTHEW5CD8]

I think cutting into 4s or even 8s and rendering one at a time might actually be an effective method. It should only take about an hour or two for each segment and I can narrow it from there.

Also I really appreciate the offer, you're too kind, but I've already taken more of your time than I have any right asking for. I'll give the short renders a try and let you know if that works on finding the problem spot. Thanks again for the insight.

[FlyingFourFun]

I hope this works out.  I am interested in what the outcome is.  As for my time, I offer it without strings.  I've been stuck and struggling and benefited from the 'kindness of strangers'.  We would all be better off if we pay it forward.   If you get to the place you need to take me up on the offer, its real and genuine.   I look forward to learning the solution.

btw,  I read you are on 15.2   - it's risky, have you considered updating to 15.4?  15.3 was a bit of trouble of me, but 15.4 so far is not haunting me.  I was reading some older posts and it seems that in 15.2 they put some work into fixing render issues and made some changes from how 15.1 handled it. in 15.3 they made substantial changes to the render again (if memory serves me correct it started using a directX vs OpenGL).  It's possible that the side effects of these upgrades bypass the issue your seeing, despite not directly beign in the change log.  IF you decide to try this,  make a copy of the project in 15.2 before opening it in 15.4 in case you have to revert back to the 15.2.