[John-Michael Seng-Wheeler] "I don't think the 32bit limitation is going to slow down DNxHD encoding all that much. Remember, the only problem with 32bit is the amount of RAM it can access. So as long as it can do the encode efficiently with only 4GB of RAM (which, because the system is 64bit, it can have that 4GB all to itself, unlike a 32bit computer where it would be 4GB for the entire system) then you won't see a speed reduction. Remember, Premiere is handeling the rendering in a 64bit process, then handing the completed frames to Quicktime to encode into DNxHD."
That's where the slow-down comes from. Premiere, a 64-bit process, cannot interface with the 32-bit QuickTime libraries directly. Adobe runs a 32-bit helper application and communicates with it from Pr/Ae via the network stack, using TCP/IP to pass frames and control data back and forth.
If Premiere Pro's renderer is synchronous (as I believe Ae's renderer is), then rendering the next frame cannot begin until the prior frame has been written. This might be worth testing.
Walter Soyka
Principal & Designer at
Keen Live
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
RenderBreak Blog - What I'm thinking when my workstation's thinking
Creative Cow Forum Host: Live & Stage Events
Reply
Like
