From FCP to APP

Chad_from_Chad

Active member
So I shot a short for MonsterFest with my friends HVX. I was going to be using his MacPro with FCP to edit, but he had to head home suddenly and now I have to use my Premiere Pro CS3. He has this software that processes the MXF files off the P2 cards into MOV's. Now on my HP PC these mov's not only are not supported by my Premiere, but my Quicktime Pro doesn't even seem to have the proper codec. Does anyone have a solution for me, or am I just gonna have to drop out of the fest? FYI, he deleted the MXF files.
 
You cannot edit the DVCProHD footage without the DVCProHD codecs. FCP installs those.

Can you view them at all in the QT Pro player?
 
You cannot edit the DVCProHD footage without the DVCProHD codecs. FCP installs those.

Can you view them at all in the QT Pro player?

He's on a PC for FCP Codec Pac with DVCPRO HD(100) not an option.

Quicktime DVC PRO 100 to Windows did not work (I made many experiments post FCP ingest at DVC PRO 100 - SMPTE 370M) The QT atom codec header was always wrong. The work-around was to develop a custom re-wrapping program for Quicktime into AVI. It is still under development.

I believe the tag atom in question was "dvh6". Past that there are a couple of vendors of this CODEC including Main Concepts, inc and Matrox.
This was at both 960x720 and 1280x1080 resolutions.
 
If you have Premiere CS3 (v.3.1 or later) you do not need the FCP captured MOVs. You need the original raw P2 file from the cards. CS3 reads these directly, just open a new project and import. (Yes, CS3 has the DVCProHD codec.)

Copy each P2 card lastclip.txt and CONTENTS folder to a new folder to your hdd and you're all set.
 
If you have Premiere CS3 (v.3.1 or later) you do not need the FCP captured MOVs. You need the original raw P2 file from the cards. CS3 reads these directly, just open a new project and import. (Yes, CS3 has the DVCProHD codec.)

Copy each P2 card lastclip.txt and CONTENTS folder to a new folder to your hdd and you're all set.

I appreciate your info, but that is my exact problem, the friend that I was going to be editing with who has the MacPro and had to visit the east coast had already copied the files to FCP and deleted the P2 folders. He gave me the MOV's and I didn't have a chance to check them until after he had left. I have half the footage cut that he had never moved over. I much prefer to edit the MXF files, if only FCP could do that native, this whole problem wouldn't exist.
 
Not to rub salt in a wound but...this is a perfect example of why mxf files should never be erased/deleted. They are your raw "tapes" of your video and should never be discarded. I wish you luck in solving your problem.

Jim
 
Sorry, saw QT Pro player, and assumed a Mac.
Never ever is there a need to say that to me :-). Actually ,excuse me for correcting you :-). Seriously.

I was trying to lleave a crumb trail for the poster for some "un-succeful" experiments regarding the DVCPRO-100 encoding with Quicktime when brought over to a Windows system, which I experimented with at some place that shall remain nameless. Realising that even given their degree of failure - the poster would most likely not have enough time to convert the MOVs in enough time for the fest submission deadline.

Though there is that MOV-2-MXF thing.... And then there is that MXF to Windows thing.. So one would only need access to a MAC-PUTER and the MXF thing for a day or so..
 
Ah, (throwing caution to the wind) --- here goes.

DVCPRO100 stream inside Quicktime is identical on both AVI Windows platform and Mac Platform,

Whether wrapped in MXF with its own byte headers, AVI, Quicktime the datastream and 4 or 2 audio PCM audio channels are identical.

The big "Apple Consipracy" with only certain quicktime codecs working in windows is 100% true. They want you to buy their hardware, their software and you're pretty much stuck if any of your footage passed through their systems during your workflow.

MXF, Quicktime, AVI are just packaging for a codec, the codec is identical on all plaforms (by different vendors though), the devil is in the headers of the package, the compression headers in Quicktime MOV's on Windows and MAC are different, so a foreign codec, even with a QT or a DirectShow filter on windows won't read the stream, since Windows does not know what codec to assign to the SMPTE 307M spec codec which is DVCPRO-HD.


Final Cut's log and transfer, on purpose labels all MOV's 720p60 - though the rest of the atoms re-time the framerate in a very convoluted way.
Final Cut's log and transfer, on purpose writes a 4 letter header to all 960x720 and 1280x1080 material that is INCOMPATIBLE, on purpose with the way Windows labels it's DVCPRO 100 codecs, with specific intent of it not operating on Windows, on purpose.

So basically Chad_from_Chad: you're looking for foreign codecs, and produccs that are able to transform MOV files to MXF, you will not be able to directly read the DVCPROHD/100 MOV generated by FCP on a windows platform, so you'll need to use a friends MAC on a loaner basis or be stuck writing your own Quicktime interpreter like I did, meaning not let quicktime interpret the MOV for you, but use your own and read the stream into some other packaging like MFX or AVI.

There is also this product... (Which is more recent than my recent clue about DVCPRO-HD)

http://www.calibratedsoftware.com/QDVCProHD.asp

^^^^--- I don't guarantee this will work. I've not tried this one.

This post will self destruct in .... ..... ....
 
Last edited:
I at this point have obviously not made it to competition. I greatly appreciate everyones involvement in this thread. Many thanks to everyone who posted. I will still be cutting the project once they get back at the end of the week. Other than not making the fest deadline it's better all around, because I'll be able to use FCP, Color, and all that other good stuff. Thanks all.
 
Back
Top