-
1. Re: AME CS6 and % of cpu used
Rallymax-forum Jun 13, 2013 7:14 PM (in response to Joe Riggs)What is the output codec?
AME can't render frames fast enough for simple ones.
If the output is complex like h.264 something is wrong with the rendering (not to be confused with the encoding) of the frames.
Does it play in the ppro sequence ok?
-
2. Re: AME CS6 and % of cpu used
Joe Riggs Jun 14, 2013 2:41 AM (in response to Rallymax-forum)Avchd footage, output to blu ray h264. Plays fine in PPro sequence.
I had some flash frames in my previous export (user induced) so I'm re-exporting part of it.
It's a 12 minute section, has colorista, magic bullet, and an adjustment layer on 90% of clips.
Media is on 1 tunderbolt drive and I'm exporting to another thunderbolt drive.
I'm getting that fluctuating cpu usage described above and
AME is estimating 6 hours, does that seem normal or excessive with my setup?
-
3. Re: AME CS6 and % of cpu used
Rallymax-forum Jun 14, 2013 10:42 AM (in response to Joe Riggs)AH... there it is.
Magic Bullet takes a long time and based on the fact that you're not at 100% across all cores, it would also mean that it hasn't been written (or the algorithm isn't possible too) as multi-threaded (so that it can run on multiple cpus at the same time).
-
4. Re: AME CS6 and % of cpu used
Joe Riggs Jun 16, 2013 7:35 PM (in response to Rallymax-forum)so is that what is causing the fluctuation, magic bullet plug in?
-
5. Re: AME CS6 and % of cpu used
Rallymax-forum Jun 17, 2013 11:06 AM (in response to Joe Riggs)it's gotta be an Fx, most likely Bullet.
further, it's got to be a significant percent of the time to render and encode each frame if you're using h.264 output. h.264 is usually about 70+% of the per frame time so if your cpu are not pegged then Bullet is taking 90% or so of the time per frame.
You can easily test this hypothesis. Preview the sequence first and then encode with "User Previews" checked. If it's fast then it's the rendering of the frame not the encoding that's the problem.

