-
File Naming From Master mxf file to QT file via FCP 6
I use FCP6 to for traditional offline edits, and forward the EDL to my on line facility for bells and whistles and final output to broadcast tape.
I have an external drive containing my P2 Card .mxf files with their Panasonic assigned file names. I want to transfer them into FCP6 and re name the new QT clips so I can manage my bins and edit process. However, I am now realizing when I export an EDL for my online bay to cut the final show version, they may not be able to reference the files because they have a duplicate external drive of the .mxf files, not the re named QT files.
Should I one, Deliver to the on line bay the FCP6 renamed QT files along with the EDL, or two, leave the original file names in tact during transfer so they appear on the EDL and use the Description field or something like that for my use in FCP6 offline, or does anyone have a better management solution for this?
My biggest concern is are the wrapped (converted) QT files the same quality as the original mxf files?
Thank you everyone for your support and responses!
Wherever I am…I’m lost!
-
14 Replies
-
Unfortunately, FCP does not access the MXF metadata at this time. Please write Apple and tell them to implement this feature in FCP.
The best way to do this is to use P2CMS to name the metadata in the MXf files themselves, then in your log and transfer process, name the files exactly the same as you did in P2CMS. that way, everything should track.
What format are you shooting, DVCPro HD or AVC-I?
What system is used to do the online? If it’s FCP, I have another idea.
Jeremy
-
Okay, that makes sense. If the on line bay can work directly with the wrapped QT files from my FCP6 transfer, that also sounds like an easy way to trade files. I just need to confirm that the QT files maintain the same quality as the original mxf files.
Answering your question, we shot with a Panasonic HPX-500 in DVCPro50 format. The on line bay works with a Media 100 edit system.
They are going to play with the mxf files and a QT test file I sent with a short EDL to see if it is straight forward in bringing in the QT file as the master source and working with it. If so, it solves my naming convention problem. If not, I’m going to test your answer by updating the mxf file name to match my QT FCP6 file names, send another sample EDL and see what happens.
Wherever I am…I’m lost!
-
I am not sure how Media100 deals with p2 media, but I do know that the very atest version of Media100 touts XML compatibilty with FCP. If oyu give them the media (wrapped QTs) or media managed a paried down version of your final timeline with only the media you need, media100 hsould be able to read those files. If not, export an XMl of your final timeline and see what happens.
Make sense?
jeremy
-
Yes, I think we’re on the same page. It’s probably right there and straight forward. The on line bay is testing both methods today, looking directly at the mxf file, and directly at my converted QT file, both with my same exported EDL (which they have worked with my EDL’s many times, so I know that part is good to go.)
Even if their Media 100 converts the mxf file to their workable format, it should still bring over the updated file name (which I would do with the P2CM Software) and we would be in sync with my EDL.
As a matter of fact, I believe the Media 100 converts and works with QT files as well, so this might be a no-brainer.
I’ll update you with the result if you are interested.
Thanks for the guidence and any other imput you have!
Wherever I am…I’m lost!
-
When you say EDL, do you mean XML?
This is what I am talking about:
https://www.media100.com/tutorial/FCPXML.php
-
Yes, we are talking about the same thing. My EDL is the Edit Decision List which is the exported XML text file. I’ve been passing that file type back and forth between my on line bay for years. So, that part is fine. It’s this new P2 format which is new to us and I’m editing with it for the first time.
Wherever I am…I’m lost!
-
OK, as EDl and XML are totally different. Media100 JUST started accepting XMLs from FCP with v13.
-
Yes, now that I’ve looked up what an XML is, you are correct. It is the EDL that I’ve been swapping with them up to now.
Wherever I am…I’m lost!
-
The best would be to have custom clip names set in the P2 XML (UserClipName). You can do this by using P2CMS but also a simple XML editor can do it if you are aware of XML.
Our software MXF4QT Import in combination with P2 Flow CM can map the user clip name to FCP clip names while accessing the native MXF assets. Beside this P2 Flow CM maps all the metadata over to FCP. You find workflow documentations and movies in the SERVICE – DOCUMENTATION section on our website.
Not sure about the Media 100 but if this one can access the native P2 MXF as well then the FCP XML to Media 100 transfer should work.
P2 Flow CM is not part of the free MXF4QT demo. Drop me an e-mail if you want to test this and I can send it to you.
Best
Bjoern———————
Product Manager
MXF4mac
https://mxf4mac.com -
Hey Bjoern. I’d like to chat with you, should I just use the contact you through the website or do you have a direct email?
Reply to this Discussion! Login or Sign Up