[Mark Fanjoy]

Jerry, Jeremy, Bob, one those!!! 😉

Thank you, guys for your support. I hope I don’t abuse my privilege of asking too many questions, but this forum is OUTSTANDING! It allows me to hurdle the obstacles and continue meeting client deadlines.

BRAVO!

Wherever I am…I’m lost!

[Mark Fanjoy]

Okay, so there is no need for me to be concerned about the import settings as I do with tape in bringing in the media low, med, high, resolution to manage disk space? The P2/MXF file to QT format is what it is, just a wrapper change?

Thanks,

Wherever I am…I’m lost!

[Mark Fanjoy]

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!

[Mark Fanjoy]

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!

[Mark Fanjoy]

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!

[Mark Fanjoy]

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!

[Mark Fanjoy]

I figured it out! I was trying to bring in the Video files into FCP and needed to be choosing the parent folder itself to bring in. Now I know why the folder name would be black and everything else inside was always grey.

I’m cruising along now! Thanks, everyone!

Wherever I am…I’m lost!

[Mark Fanjoy]

I’m trying the P2 format for the first time. Transfered from P2 to external RAID nicely, the contents folder (with all the directory files,) and the all-important LASTCLIP.txt file. So why doesn’t FC Studio 6 see the files and allow them to import with the Log & Transfer function? What am I not doing correctly I wonder?

Thanks for any ideas.

Wherever I am…I’m lost!