-
DNxHD import speed
I am exporting DNxHD QT (1080p 24fps 175Mb 8 bit) from Premiere Pro.
But when I am trying to import it to Avid it takes terribly long time.
It goes very slowly with long pauses after which it increases estimated time.I had 12 minutes shot which was importing for about 7 hours.
Is it really what the “fast import” is about?Working on Avid MC 5.0, 64bit Windows 7, 4Gb RAM, 2.83Hz Core2 Quad CPU
-
7 Replies
-
Iva,
If you ‘hit the mark’ with the way the DNxHD QuickTime clips are created, they should open in MC in 1.25 Real time…not 7 hours.
Also, toss them into a folder and try AMA.
Best,
Jeff G
Apple Master Trainer | Avid Cert. Instructor DS/MC | Adobe Cert. Instructor
————
You should follow me (filmgeek) on twitter. I promise to be nice.
Come See me speak at NAB!
Compressor Essentials from Lynda.com
(older but still good) Marquee, Media Composer (3.5) and Basic/Advanced Color DVDs (1.0) from Vasst.com
Contact me through my Website -
I wrote up a guide to correctly creating DNxHD files for Fast Import, perhaps it may help:
https://michaelkammes.com/encoding/avid-is-self-aware-fast-import/
~Michael
.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com
.: twitter: @michaelkammes
.: facebook: /mkammesHear me pontificate: Speaking Schedule .
-
Thank you, Michael. This is a very nice tutorial, but it doesn’t solve my problem.
-
Respectfully, you must be missing something. Fast Import is being used by thousands of editors, thus I can only conclude your export settings from Premiere, or Avid import settings are incorrect.
Things to double check:
-Frame Rate mismatches (Premier export vs Avid project)
-Import settings in Avid
-Millions of colors vs millions of color+
-Try NOT doing a fast import (i.e. import a movie file not optimized for fast import) and see if the time is different from the Fast Import – lets make sure there IS a time difference.
-Make sure DNxHD codec versions are the same on both boxes (this should not affect import time, but it doesn’t hurt to make them the same)
-Try MC 5.0.3.8~Michael
.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com
.: twitter: @michaelkammes
.: facebook: /mkammesHear me pontificate: Speaking Schedule .
-
Thank you for taking this issue so seriously.
I made a test: export 1 min material same as source (DNxHD 175 X) from my project (took 3 mins) and import it back with the same quality. Guess what? The estimate is 26 minutes and growing.. How is that?
My thought is that it has something to do with my project frame rate (24)
-
Lets limit some variables.
Have you verified the codec versions are the same? Are you at MC 5.0.3.8 and does your QT version match what is supported for 5.0.X? (should be 7.6.6)
Export 175 (8bit) NOT 175X. Use Millions of colors, NOT Millions of colors+. Make note of the frame rate (24 vs 23.98, etc)
Now, attempt to import that file into the same project or a brand new one, as long as the project rates are the same, making sure to change your import settings. YCbCr 709, not RGB, Pixel mapping is set to 601 or 709, and select Use Source Files resolution. I hate to say it, but mirror my settings (step 9, 10, and 11).
~Michael
.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com
.: twitter: @michaelkammes
.: facebook: /mkammesHear me pontificate: Speaking Schedule .
-
If you suspect the frame rate, go into the console and type
ignoreQTrate=True
And try again.
But i suspect something else. Even rendering the most comlex input to DNxHD should be faster than what you see.
Bouke
https://www.videotoolshed.com/
smart tools for video pros
Reply to this Discussion! Login or Sign Up