-
Sequence Conforming and “Same as Source” in CC / Pro Res
Hello all.
Using Premiere CC – on both a Mac 10.8.2 and 10.7.x. Both machines have CS6, as well as FCP 7 and FCP X installed.
The goal is to import 1 ProRes file with captions, do a few cuts, then export with as minimal transcoding as possible. No other clips, no other codecs, nothing but cuts and dissolves and captioning.
I import a ProRes file, and create a new sequence based on that file (planning on doing an export after the edit which was based on sequence settings. I thought this would be the easiest way to maintain the same settings through the entire process.)
On my 10.8. CC machine, dropping a ProRes 422 HQ file on a new timeline, and I select to change sequence settings to match the clip, the sequence settings display DNxHD145. On my 10.7.x box, the timeline comes up as AVCHD. An associates machine comes up as ARRI. Timebase and frame size are right, but not the codec.
I understand that the sequence settings are less important for output, as the transcode pulls from the raw media, not the sequence esettings.
However, without the sequence accurately conforming to the media clip, I am unable to export using sequence settings. This means I need to manually transpose the codec properties into the export window. This can be tedious and is easy to mess something up.
So:
1) why is the sequence not conforming to the ProRes clip? And why is it different on 3 different machines?
2) How can I get the export settings to mirror the clip properties? – without manually transposing the properties?
3) The end goal, in Avid parlance, is “Same As Source”. Does this function exist in Premiere?Thanks all!
~Michael
.: michael kammes mpse
.: director of technology and marketing
.: michaelkammes.com
.: twitter: @michaelkammes
.: facebook: /mkammes -
4 Replies
-
I have experienced something like this. On one machine, matching settings works correctly for a ProRes source. On another, the size and frame rate change, but the “match” results in AVCIntra codec.
I think it is a bug.
What I figured out, and it doesn’t make much sense to me, is that Premiere takes the sequence preview codec as the output codec when “matching” sequence settings. So if the sequence has ProRes previews that match the original footage, then it will output correctly using the match function.
On the machine that results in AVCIntra, the preview codec doesn’t get changed.
Bizarre. I ended up creating a ProRes preset to avoid this issue.
Hope this helps.
Gerald Goldman
Director of Post Production
Grace Creek Media
http://www.gracecreek.com
http://www.sportskool.com -
Premiere Pro’s ability to “detect” what codec is in a QuickTime file for purposes of creating a sequence just doesn’t seem to work.
If it’s QuickTime or Adobe…(it can’t be the OS as it’s done this on Windows for a long time as well), I have no idea, but it’s a well-known issue.
You’re best off manually creating a ProRes preset as Gerald did to properly configure your preview format, etc.
TimK,
Director, Consultant
Kolb Productions,Adobe Certified Instructor
-
What would be the best way of exporting a “same as source” clip, short of manually transposing clip properties to the export window?
.: michael kammes mpse
.: director of technology and marketing
.: michaelkammes.com
.: twitter: @michaelkammes
.: facebook: /mkammes -
[Michael Kammes] “What would be the best way of exporting a “same as source” clip, short of manually transposing clip properties to the export window?”
If this is specific to ProRes, I would think you’d want to test it after you make a sequence setting that’s correct as the “match settings” may get it right…otherwise you can set up an output profile preset in AME so you wouldn’t have to do it manually more than once.
TimK,
Director, Consultant
Kolb Productions,Adobe Certified Instructor
Reply to this Discussion! Login or Sign Up