-
Avid MXF files and FCP X questions (long)
-
Jeremy – I can email. Address?
-
[Jeff Markgraf] “Jeremy – I can email. Address?”
You should ping Jeremy, Oliver, or Bueller. lol As the saying goes, this is above my pay grade.. 😉
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
Meant to reply to Jeremy. Apparently the threading structure of this forum is too much for my pretty little head to handle.
-
editstation (at) gmail
-
[Jeff Markgraf] “Avid won’t even let you do it at all.”
Huh? Which version are you on? Media Composer has allowed mixed frame rate timelines for quite a few years. You have to import files of different frame rates into separate compatible projects. Then open those bins into your main editing project and drop any and all on a single timeline. Media Composer will adjust the non-matching frame rate clips to whatever the frame rate is of that main project.
So, 23.98 clips should be imported into a 23.98 native project. Then open that bin in your 29.97i project and cut the clip to the timeline. Avid’s motion adapters will take care of the rest, such as adding the correct 3:2 cadence.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
I’m quite interested in the outcome on this one – we are primarily a FCPX shop, but frequently work with others who are primarily Avid. Any chance I could have a look at this file as well?
dmetz (at) anode
Doug Metz
Anode
-
Hello again Cows.
Success! The jerky video that has been giving me fits has been fixed with an updated driver for the T-Tap. I guess Yosemite borked it just enough to be flaky, if not fully broken. All frame rates and combinations of progressive or interlaced appear to be playing fine now. The whole 23.98 vs 29.97 thing seems to have been an artifact of the driver problem.
At this point, I’m going with Jeremy and calling the false progressive flag a bug. I was able to look at some of these files in the Avid and Avid says they’re interlaced. I also imported one of the show files directly into FCP (delivered as MXF from the studio) and it also comes in interlaced but with the progressive flag set in FCP. Toggling to upper field dominance fixes it immediately.
Thanks to all for suggestions.
-
[Oliver Peters] “You have to import files of different frame rates into separate compatible projects.”
Hi Oliver. My mistake. I’ve done almost no mixed frame rate work in Avid. I was basing my comment on not being able to digitize or import different frame rates in the same project. For the record, my work avid is 6.5.3.
-
Good to hear!
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Jeff Markgraf] “I was basing my comment on not being able to digitize or import different frame rates in the same project.”
I completely understand. The current Avid solution isn’t very good and hopefully at some point in the future that will be unified to work within the same project. So, clearly not as fluid as with FCP X or PProCC. OTOH, you have a very clear understanding of the frame rates you are dealing with.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com
Reply to this Discussion! Login or Sign Up