1 person found this helpful
Does anybody know if PremierePro CS5 imports NanoFlash mxf-files native and uses the given bitrate of 220 mbps or does it automaticly convert it down to a compression of 50 mbps?
They import--video, audio, timecode--and there is no conversion. Premiere Pro doesn't do any kind of conversion with any kind of media that it supports--that's the crux of "native editing." So, you're getting access to every pixel and bit of image information as it was recorded by the camera.
The note about the memory leak is probably worth heeding; there is a bug in CS5 that leads to all available memory being used with these MPEG assets. There's a very hot thread right now about this issue, as it pertains to the Canon XF format (it also uses MPEG-2 at 50Mbps in an MXF container), but I would suspect that it's this issue that that note is referring to. As the note also points out, this is corrected in CS5.5, but will remain in CS5. There is a memory cleaner linked to in the Canon XF thread that has worked for some folks. I don't personally work with either format, so the trials and tribulations of either of these is based solely on others' reports.
funny, we are getting the same thing and i just downloaded all their test files and experimented in cs5 with them.
they all worked excellent in one of my CS5/Axio systems and played back and decoded/rendered very fast and effeciently. I overlayed 3 copies of each and played all 3 layers without a hiccup. I think these files edit VERY effeciently in CS5 and recommended to our engineers that we order them for our field recording over the cinedeck units we were looking at.
in rendering tests these files could be rendered out exactly twice as fast as the cinedeck quicktime prores files i tested.
Thanks you all helped me a lot. My confusion about importing mxf-assets had come to an end now.