This is very interesting. One question though: was the polywav information embedded in the AAF? Or to rephrase the question to avoid any misunderstandings:
When where the polywavs first brought into the session? Where they imported during the cut in Media Composer and subsequently (somehow) made it in the AAF? Or did Scott had to import all the polywavs AFTER opening the importing the AAF? If it is the former, this is something I didn't know Media Composer could do!
Is this a workflow fro Pro Tools HD only . I am running Pro Tools 9 here and the Field Recorder Channels Match Criteria is not available when I click the Channel's name.
I am working on an indie and it wold be a life saver as the session is exported in OMFII and I am facing issues with metadata track naming, meaning that I loose loads of precious time to locate production tracks.
I am editing on a Mac Book Pro and the Ctrl + 5 shortcut doesn't work either.
Thank you for the reply. I am assuming your footage is in HD, so are you exporting as a QTRef or doing a video mixdown first then QTRef exporting the seq?
What is the footage resolution being exported from MC? If it's HD what piece of hardware are you using to watch it in Pro Tools... SD has the DV toolkit2 working for it, but I can't get HD out of MC5.0 without dummying it down to SD... Thoughts?
@RiggiMediaInt We used Avid's Quicktime DnXHD Codec to view the video on the desktop. It will play in any version of Pro Tools and it's easy on the playback performance of your machine. We then use the DVI output to a projector or any such device. The nice thing too for the Media Composer video editor is, it's slightly faster than realtime export, much quicker than any other QuickTime resolution.
Very well done & really interesting!
FotographerTV 2 months ago
This is very interesting. One question though: was the polywav information embedded in the AAF? Or to rephrase the question to avoid any misunderstandings:
When where the polywavs first brought into the session? Where they imported during the cut in Media Composer and subsequently (somehow) made it in the AAF? Or did Scott had to import all the polywavs AFTER opening the importing the AAF? If it is the former, this is something I didn't know Media Composer could do!
Nemosonics 7 months ago
Is this a workflow fro Pro Tools HD only . I am running Pro Tools 9 here and the Field Recorder Channels Match Criteria is not available when I click the Channel's name.
I am working on an indie and it wold be a life saver as the session is exported in OMFII and I am facing issues with metadata track naming, meaning that I loose loads of precious time to locate production tracks.
I am editing on a Mac Book Pro and the Ctrl + 5 shortcut doesn't work either.
Is there an alternative ?
ArashAtman 7 months ago
Too bad I don't have ProTools :P
OCUBOX 7 months ago
@OCUBOX buy it
wizprodux 7 months ago
@wizprodux which will mean I have to Buy a Mac Book Pro too, I'll stick with Nuendo :P
OCUBOX 7 months ago
@OCUBOX it works on PC too!
eatsleepgolf 7 months ago
@eatsleepgolf of course it does, with a whole load of hoops to jump
OCUBOX 7 months ago
Thank you for the reply. I am assuming your footage is in HD, so are you exporting as a QTRef or doing a video mixdown first then QTRef exporting the seq?
RiggiMediaInt 7 months ago
What is the footage resolution being exported from MC? If it's HD what piece of hardware are you using to watch it in Pro Tools... SD has the DV toolkit2 working for it, but I can't get HD out of MC5.0 without dummying it down to SD... Thoughts?
RiggiMediaInt 7 months ago
@RiggiMediaInt We used Avid's Quicktime DnXHD Codec to view the video on the desktop. It will play in any version of Pro Tools and it's easy on the playback performance of your machine. We then use the DVI output to a projector or any such device. The nice thing too for the Media Composer video editor is, it's slightly faster than realtime export, much quicker than any other QuickTime resolution.
eatsleepgolf 7 months ago
Nice!
dlyle46 7 months ago