-
proxy matching issues between 1080 and 2K after epic journey that I’m glad I didn’t take
HI,
I cut several rough cuts of a feature in the most recent version of Premier using 1080 ProRes Proxy media. the DIT also make a set of DNx 2K files that matched the ProRes Files for the online.
After I turned over the project, the director recut the film with an intern using FCP X. After that they ported it back to Premier in a new project (yeah, I know). Now they would like to use my old project sequences to copy my first version.
They want to use my old project to open sequences in the new project.
But…
It turns out that the interns used the 2K DNx footage to cut with and not the 1080 ProRes.
Now they want to link the clips in my project sequence to the 2K footage (are you with me?). They link it back and they get this error:
” Proxy Media and Full Resolution Media mush have matching audio channels.”
I thought they did. I’m contacting the DIT to see if he synced the external audio to the DNx files or just used the prodcution audio. Would this matter?
Anyone have an idea how I might assist them?
thanks!!
Rachel
-
3 Replies
-
usually its because a codec is used that doesn’t support as many audio channels. cineform, for instance, can handle a lot of channels.
some codecs only support 2 channels. -
Its also sometimes due to the original being flagged as dual mono and the proxy being created with a stereo preset.
This is a HUGE design flaw in proxy creation.
The presets should have “pass through” audio audio mapping, so that this cannot happen. I cannot envision a scenario where someone would want their proxies to differ from the original files.
-
the ProRes files have 8 tracks of audio and the DNx files have 2 tracks.
Would this cause the problem? If so, is there a work around? They really have to link it back to the ProRes QT’s with the 8 tracks of externally recorded sound.
thanks,
Rachel
Reply to this Discussion! Login or Sign Up