Matt Vanecek
June 17th, 2009, 06:51 PM
I'm sitting here trying to prep a test project for a trouble ticket I have open, and noticed something. I cut out about a minute from a longer clip, where the longer clip has an associated First Light profile. When I export that 1 minute clip to a CFHD AVI, the export takes about 6 minutes. No other effects aside from the First Light profile.
When I bring that 1 minute export back into Premiere and monkey around with getting my test export setup, and then export the 1 minute clip again (this time, NO First Light, and no other effects), the 1 minute export takes about 2.5 minutes.
In this instance, it seems that the clip without First Light attached took a much shorter time to export and used a good 55% of the CPU, while the clip WITH First Light took a long long time (relative to clip length), and only sucked up about 15% of the CPU.
Is this expected behavior when rendering out to CFHD AVI from CFHD AVI? Or could the First Light linkage be the reason that Premiere Pro appears to be starving the CF encoder engine?
Thanks,
Matt
When I bring that 1 minute export back into Premiere and monkey around with getting my test export setup, and then export the 1 minute clip again (this time, NO First Light, and no other effects), the 1 minute export takes about 2.5 minutes.
In this instance, it seems that the clip without First Light attached took a much shorter time to export and used a good 55% of the CPU, while the clip WITH First Light took a long long time (relative to clip length), and only sucked up about 15% of the CPU.
Is this expected behavior when rendering out to CFHD AVI from CFHD AVI? Or could the First Light linkage be the reason that Premiere Pro appears to be starving the CF encoder engine?
Thanks,
Matt