Before you get too comfy in your switch . . . .

[Tim Wilson]

[Don Walker] “[Tim Wilson] “Anything else you’d like me to disclose, just ask.”
Kirk or Picard?”

Dude. C’mon.

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

Seriously.

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

[Tombabauta]

Wow. You can cut through the fan-boyism in this room with a box cutter.

It’s just like those May 21 doomsday followers. And when the end didn’t come on the said date, they still blindly believed the same guy when he said that the end will come in October.

[Jeff Bernstein]

The problem with MXF is that is was too open and did not have a tighter spec. As a result, you see different implementations of MXF which are not compatible. Prime example would be how Sony and Panasonic did theirs. In addition, since typical MXF implementations break up files between different components such as audio and video and metadata, it becomes are royal mess to manage your files in a file-based workflow.

Unfortunately, MXF did not become the ‘open standard’ answer to the need to replace to supplement QuickTime.

[Dennis Radeke]

[Hector berrebi] “but Avid’s DNX is actually optimized for MXF, is it so complicated for premiere to properly support it? (it does somehow, but less than satisfactory)”

Indeed you’re right. Avid’s DNX is simply a licensing issue and therein lies the challenge. Our support of it exists through Avid’s Quicktime Avid Codecs LE pack which supports QT wrapped Avid files but not the native MXF.

[Hector berrebi] “i thought MXF was rather open…
RED’s free REDCINE-X does a great job writing them for one… and there are many other tools around to read and write these files..”

You could say that MXF suffers from being TOO open. I actually sit on the AMWA board (Advanced Media Workgroup Association). This is what the AAF became (long story). Essentially, the mission of AMWA is to create useful specifications by putting constraints on what you put in your MXF.

[Hector berrebi] “for a short wonderful time it was even possible to open Avid’s AAF in premiere and link to media… now its broken… last time i checked it worked only for DV files…”

This is true. When Avid introduced AMA to Media Composer 5.0, it broke our workflow. We’ve been evaluating the limitations and ways to provide a robust interchange between Avid and Adobe much as we have between FCP (XML) and Adobe.

Since we’re talking MXF, Adobe outputs Panasonic P2 flavor MXF with associated file structure and Sony OP1a MXF. For editing, we support P2/AVC-Intra, XDCAM-HD.

Hope this helps.
Dennis

[Bill Davis]

I think I would be just fine with 40% of 250 million potential customers – particularly since that represents the entire populations of virtually ALL of the major cities in the country.

If you couldn’t drive business sustaining revenue in a situation like that with essentially NO cost of goods sold outside initial development. – it would be entirely about the lack of a successful marketing strategy – not in any way shape or form the dearth of a viable market.

FWIW.

“Before speaking out ask yourself whether your words are true, whether they are respectful and whether they are needed in our civil discussions.”-Justice O’Conner