Adobe support just spent two hours fixing this issue. It was a problem with the graphic card.
Edit by Moderator:
The editor chose Project Settings > General > Renderer > Mercury Playback Engine - Software Only to work around the issue.
Why this worked:
- With Software Only mode, the GPU is bypassed so the video can be rendered and exported without it.
- A Software Only export will take much longer, however.
- Typically, the fix involves purchase of a more powerful GPU if your warning contains any reference to a GPU accelerated process, like Lumetri.
- Another workaround would be to use smart rendering, which involves changing the rendering codec to a smart rendering one, like ProRes, then checking the "Using Previews" option when exporting, and using ProRes as the output codec instead of H.264.
- In this thread, some editors have also experienced the error by
- Including a punctuation mark in the output naming of the file.
- Using oversized still images. The technique is to prep images so that they are no larger than twice your sequence size prior to importing them.
Adobe support just spent two hours fixing this issue. It was a problem with the graphic card.
Edit by Moderator:
The editor chose Project Settings > General > Renderer > Mercury Playback Engine - Software Only to work around the issue.
Why this worked:
- With Software Only mode, the GPU is bypassed so the video can be rendered and exported without it.
- A Software Only export will take much longer, however.
- Typically, the fix involves purchase of a more powerful GPU if your warning contains any reference to a GPU accelerated process, like Lumetri.
- Another workaround would be to use smart rendering, which involves changing the rendering codec to a smart rendering one, like ProRes, then checking the "Using Previews" option when exporting, and using ProRes as the output codec instead of H.264.
- In this thread, some editors have also experienced the error by
- Including a punctuation mark in the output naming of the file.
- Using oversized still images. The technique is to prep images so that they are no larger than twice your sequence size prior to importing them.
thanks for the response kevin,
HERE IS THE ERROR REPORT:
Export Error
Error compiling movie.
Accelerated Renderer Error
Unable to produce frame.
Writing with exporter: H.264
Writing to file: /Users/jossdonald/Desktop/Current projects/Logo animation/Deep lerning/Master V5_AME/Logoanimationprepv5_2_12_3.mp4
Writing file type: H264
Around timecode: 00;00;12;26 - 00;00;13;12
Rendering at offset: 12.880 seconds
Component: H.264 of type Exporter
Selector: 9
Error code: -1609629695
I managed to find a work around as I narrowed it down to one particular PNG image - I opened the image in PS, saved it as a jpeg then relinked the png file in after fx to the new jpg file which solved the issue. It wouldn't have been due to any complex effects as the time within the composition that was causing the issue had only one simple liniar wipe effect (whereas other parts of the comp had much more complex and intensive effects).
I have come across this issue before though and it seems to have multiple things that can trigger it.
Bobby
I just resolved my Error code -1609629695 My error message was Rendering effect: AE.ADBE Geometry. I explored every frame in the timecode estimate provided in the message and found a single frame that was going black due to a text motion effect I was using with a color block swiping out of the scene. Something in the effect was causing the entire scene to blackout for 1 frame. When I deleted that color block from the effect, the problem was solved. Hope that helps anyone.
AdChoices