![]() Stopped Windows & Kaspersky (my antivirus) updates,Ģ. īasically, 14.3.1 isn't working for me so I rolled back through prior versions & I got the export to work in 14.0.1 but like I said, it took 29 hours.ġ. One thing that worked for me (half way down this post) is something you probably don't want to do because it turned a normal 10hour export into a 29 hour export! I posted about it on this thread. Nothing in my timeline was that unusual or complex. I'd say there's still something wrong with Premiere Pro causing this error. For some reason that worked, and if I did my output with "Use Previews" checked, the final render worked. Then I moved the Work area bar into the unrendered spot, made it one frame long, and rendered one frame at a time. Something else that worked was to render up to the error, then set the Work area bar a few frames after the error and render another second or two. ![]() ![]() So I zoomed into that spot and experimented by setting the Work Area bar around the problem spot and doing a Sequence/Render entire work area. That created a log file with the time code of the error. I first found the failure at the end of a 90 minute render in Adobe Media Encoder (AME). Make the dissolve one frame longer, and the render succeeds: The fix was to just make that dissolve one frame longer.įirst, the render failed at the end of the dissolve (note the green/red transition). The render error started hitting the last frame of the dissolve. It's not complex, but it does take two nested sequences, and I dissolve into the final composite. I have a closing sequence that I put on the end of all my shows. I started running into this when I upgraded to CC.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |