MXF file for you to "experiment" with.

stephenlnoe

Well-known member
Hi guys and gals,

I've bundled an MXF file for you to test your NLE with. Here are the steps to use it.

1. Download it to your computer Click Here
2. Rename the file extention to MXF (from TIFF)
3. Attempt to import it into your NLE and use it.

The MXF is bundled 720x480 I frame (MP@ML) 12Mb with 16bit 48kHz stereo audio. I had to rename the extention to TIFF so that you could download the file from the server (there is a restriction on the types of files it will serve).

Good luck on trying it out.

S.Noe

PS ****THIS IS NOT HVX FOOTAGE!****
 
I relinked the file to a 12Mb I frame MP@ML instead of the original broadcast MP 50Mb 422 file. It will probably fare better for you. Give it another shot when you get the chance.

The one linked above is
Iframe 12Mb MP@ML 411 instead.

best,

BTW The broadcast files can be exchanged between Liquid and News Cutter/Media Composer. Not all NLE's can accept broadcast stream MXF.
 
I was able to import it with VelocityHD, which converts it non-realtime into the file format of the Altitude board. This was a bit surprising, as the MXF format isn't officially supported in the version I'm running. Pleasant surprise.

I need to check the next beta of Velocity, as it is supposed to allow realtime playback of SD P2 media from the timeline without conversion...

Thanks! Do you have any material that is fielded video? Just a short shot to see some live action...

Jim Arthurs
 
Jim Arthurs said:
Thanks! Do you have any material that is fielded video? Just a short shot to see some live action...

Jim Arthurs

Jim,

What size was the file you downloaded? 40MB or 156MB?

The 156MB file I first linked was a 50Mb 422 I frame broadcast file.
The 40MB file I linked later was a 12Mb 411 I frame from a DV25 timeline.

If VelocityHD opened up the 156MB file then that is good indeed. I do have PLENTY of material but this is just for testing purposes. We also exchange OMFI as well but MXF is being supported more lately and it seems to be better because it carries the timecode in the metadata unlike OMF.
 
stephenlnoe said:
Jim,

What size was the file you downloaded? 40MB or 156MB?

The 156MB file I first linked was a 50Mb 422 I frame broadcast file.
The 40MB file I linked later was a 12Mb 411 I frame from a DV25 timeline.

If VelocityHD opened up the 156MB file then that is good indeed. I do have PLENTY of material but this is just for testing purposes. We also exchange OMFI as well but MXF is being supported more lately and it seems to be better because it carries the timecode in the metadata unlike OMF.

Stephen, I first grabbed the 156 meg file, then after reading your latest e-mail tried again and got the smaller one. Both imported without complaint and appear visually identical despite the large difference in file size.

During import I was surprised to see a mpeg file of each created in the same directory as the originals were in, along with .wav's of the audio. Not sure why the mpegs were created, will try and find out. Velocity uses an adaptive variable bit-rate wavelet based codec for both SD and HD playback, not mpeg.

Thanks, it's great to play with this media instead of just talking about it all the time. :)

Jim Arthurs
 
rgdfilms said:
Error, unknown file - in FCP 5
My understanding is that FCP does not understand MXF. You'll have to debundle the file to use it with Final Cut and maybe Vegas too. The only products (that I'm aware of) that can edit MXF (SD) directly are Liquid, Avid and Edius. It's good to hear Leitch has it's own built in debundler and that it can handle I frame files!

@MtSurf, in Vegas5, did you get the audio and the video streams? Can you render the file to your timeline codec to play back a full speed?
 
no audio and I can get full frame rate if I render it. We are getting the HVX in December so its good to figure out what the solution is going to be for post now instead once we get the camera.
 
Whats with this MXF file? Is this what we will be getting when we record to P2?
I tried opening in FCP5 and I got nothing but error. I thought FCP would support P2.
 
vuzz said:
Is this what we will be getting when we record to P2?
The short answer is no.

There are 2 types of MXF: XDCam MXF and P2 MXF

The linked file is an I frame MXF or in other words an XDCam MXF (mpeg based). P2 MXF, on the other hand, is a DIF file in an MXF wrapper. An MXF is an MXF is an MXF. They are all the same, but the contents could be either MPEG or DIF, audio, timecode, picons etc. Google MXF.

vuzz said:
.... I thought FCP would support P2.

I don't think FCP will ingest MXF P2. You'll need to debundle it first and then bring in the elementary streams. I hope I'm wrong about that but I don't think I am.
 
stephenlnoe said:
The linked file is an I frame MXF or in other words an XDCam MXF (mpeg based). P2 MXF, on the other hand, is a DIF file in an MXF wrapper. An MXF is an MXF is an MXF. They are all the same, but the contents could be either MPEG or DIF, audio, timecode, picons etc. Google MXF.

Ah, that explains why on import my VelocityHD system automatically created the mpeg file before reading that into it's own format for playback... Also confirmed that the upcoming Velocity dot release handles P2 and DVCPRO-50...

Jim Arthurs
 
Hi stephenlnoe, Thanks for posting this file but I think there is something wrong with it. I can import and use XDCAM MXF files in Vegas 6 but this file causes a crash the moment I click on it.
 
Celluloid Dream said:
Hi stephenlnoe, Thanks for posting this file but I think there is something wrong with it. I can import and use XDCAM MXF files in Vegas 6 but this file causes a crash the moment I click on it.
The file is OK. You may not be able to open it. There was another poster that said the same thing about Vegas 6, but VelocityHD can open it fine. The file is an I frame file from a Liquid Broadcast edit suite. Maybe Vegas can't open I frame MXF files and it must be IBP instead?

I have no idea about Vegas. If you can check your online help and see what type of MXF's it supports maybe we can get it to work.
 
"AVID and APPLE's NLE's will recognize MXF clips right out of the box" this is the quote from the P2 Article here by Jarred.

Can Jarred or Barry set the record strait about workflow or is this still a gray area? I see someone has posted the same question about using P2 Mxf on the Cow, and it makes me very confused.
 
vuzz said:
....set the record strait
Avid, yes, definately.

FCP, is not a straight path: "A file transfer from MXF to QuickTime provides Final Cut Pro 5 with the necessary camera-native DVCPRO, DVCPRO50 or DVCPRO HD files for editing." Click here to go to apples site.

Seems there is a couple extra steps to get to the files in FCP. You'll have to run them through Quicktime first to make them available, so no direct edit of MXF. As I wrote above, for FCP you'll need to debundle the MXF to get to the content first.


BTW OT: I read the report on Avid Xpress Pro's implementation of HDV (for their current release) and it does not include Native HDV editing. They did not have time to get it implemented from Liquid's timeline. Click here to get info on Xpress Pro's HDV effort This leaves Liquid and FCP as Native HDV long GOP editors.
 
oh , damn it, AVI, QuickTime, and now MXF, why , why these damned wrappers, I mean I can use the same codec and wrap it in QT and AVI, yet some programs will refuse to open the QT file even though the read the same file if it where wrapped in AVI.

Oh well

Anhar
 
stephenlnoe said:
The linked file is an I frame MXF or in other words an XDCam MXF (mpeg based).

I have no idea about Vegas. If you can check your online help and see what type of MXF's it supports maybe we can get it to work.

Vegas 6.0c readme: "A full-resolution MXF reader for XDCAM has been added to allow you to use MXF files on the Vegas timeline."

Vegas 6 is my primary NLE. I have edited XDCAM MXF files in Vegas so I know they do work. What I was trying to say when I said "something is wrong with this file", is that this is not an XDCAM MXF, because if it was it would work in Vegas 6.0c instead of crashing it.
 
Back
Top