LXF Format

[Jeremy Garchow]

Sounds proprietary or linuxy to me. Where did the footage orginiate? What was it shot on?

[Andy Mees]

from Leitch Velocity Jeremy (previously DPS Velocity)

off the top of my head, the only system I think of that might transcode these is Rhozet’s Carbon Coder

… you might want to have them export these for you in a more suitable intermediate format

[Simon Hustings]

Thanks for your input guys.
This lxf container holds 26, 30 or 50 mbits/sec mpeg2 422 i-frame footage. (As held on their media server) I’m guessing that as the footage is comprised completely of i-frames, this is one of those times it’s ok to edit in mpeg2!?

He can export out from Velocity in other formats, but I just wanted to see if there was a way to take the LXF format into FCP natively, as to make the work flow more efficient. If that isn’t an option then, a cut back to tape or to disk in an FCP compatible format will suffice. It may increase the render times, but at least the footage will be in a format that I can use!

All the best,
Simon

[Jeremy Garchow]

The only thing I could find was what Andy mentioned, and it’s not exactly cheap for one project. It’s just a transcoder anyway so if you can, you might as well have them transcode the footage on their end.

Jeremy

[Bjoern Adamski]

Hi Simon,

LXF is a proprietary file container format from Harris/Leitch. As far as I know no one beside Harris/Leitch can read this natively.

You can probably just re-wrap the “30 and 50 mbits/sec mpeg2 422 i-frame footage” to standard MXF D10/IMX. This is readable by our MXF4QT Import software and natively editable by FCP. Not sure about this 26 mbit version, I doubt this must be transcoded to use in FCP.

At NAB Harris also showed a native access to MOV and MXF files in parallel to the LXF files. The MOVs and MXFs were completely virtualized in realtime so you could access them in directly in other applications.

Hope this helps.

Best
Bjoern

———————
Product Manager
MXF4mac
https://mxf4mac.com