-
AME hangs-what are some possible causes and solutions?
Hi
Pulling my hair outTwice AME has hung during a render 70% thru at exactly the same spot.
Tried clearing the AME cache
https://forums.adobe.com/thread/682009?tstart=1Nothing in the error log
Hangs in the exact same spot twice in a row
No corrupt, missing or unlinked files I can seeusing dynamic linking and outputting using Vimeo 720P preset with CBR 1 pass.
I’ve lost an entire day just trying to render a 6 minute clip.
My beef- Why can’t AME somehow give you a an error message when it hangs so you can debug?
VERY frustrating and losing my confidence in this workflow…
Local is the new global
-
5 Replies
-
That would suggest a clip at that exact point is no good.
You might want to find the “rough” spot, export the original clip in and uncompressed format and then replace it in the edit. Try to isolate the problem area with a render area instead of waiting the entire render.
Or you could try to export the whole thing as uncompressed. I suggest Quicktime Animation, you may need to rejig your settings manually to match the frame rate, dimensions, aspect ratio etc.
Use the details shown in the export settings that detail the source and export settings to get the details to manually set. Then I highly recommend you save the preset! 🙂
Once you have the Uncompressed export use that to create any other export formats. like a Master file to slave out. This is not common practice, but when this kind of error appears this is generally considered the fail safe workflow. I export directly from the timeline in all kinds of formats and never have to use this process, but I don’t use a wide variety of formats and codecs.
What kind of media are you editing?
– JB
Jon Barrie
Adobe Video Solutions Consultant ANZ
Jon’s YouTube Tutorial Page
follow Jon with twitter -
Thanks. All DSLR H.264 footage.
I was able to render the entire sequence yesterday..may have made some minor changes to adjustment layers in AE.
I’ll try once more this evening after clearing all caches, rebooting.
As a last resort will try rendering uncompressedLocal is the new global
-
Thru some trial and error, isolating exactly where this was occurring, was able to resolve.
Outputting uncompressed the render consistently hung, but 1 frame later, enabling me to confirm where the issue was.I’m using dynamic linking for most of my 6 minute sequence.
In AE, I am using an animation reset on 1 short 5 second clip. In that preset is an effect that only works up 16bpc. My project was in 32bpc. In addition, there was a yellow exclamation mark next to that one effect.
I disabled that 1 effect in the preset (rather than switching my entire project to 16bpc, did another render defining my work area just where my render was hanging, and it outputs fine!.Moral of the story I guess is to pay attention to yellow exclamation marks! Though I don’t think this should have stopped my entire render chain. Pretty sure this must be a bug. Have lost several days trying to resolve this. And not only did this issue stop my render, I was required to do a force quit on both AME and Premiere to start again.
Local is the new global
-
Hi Jon,
I’m having a similar problem and wanted to try your solution. I’m using Premiere 5.5 on a Mac and I don’t have Quicktime Animation as an uncompressed output option.
Can I get that or is there another option?
Thanks
-
Hi Jon,
I’m having a similar problem and wanted to try your solution. I’m using Premiere 5.5 on a Mac and I don’t have Quicktime Animation as an uncompressed output option.
Can I get that or is there another option?
Thanks
Reply to this Discussion! Login or Sign Up