FCP6 -- native editing from P2 cards?

Just wondering . . .

What is the "native MXF problem?"

I'm still not certain.

We've been using FCP with the HVX200 since March 2, 2006 without any native support and with no issues
 
It's not a "problem", it's an increased capability. Nobody's saying the FCP solution doesn't work (clearly it does, as something on the order of 95% of HVX users are using Mac/FCP).

But it doesn't do everything it could do. Every other editor on the market allows you to edit the MXFs directly (either by themselves or through Raylight), so if you have a drive full of offloaded card contents, you can edit that footage immediately instead of waiting for it to be converted to quicktimes. Or if you have footage on a card that you want to edit right from the card, you can on any other editor, just not on FCP.

Raylight for the Mac will allow that for FCP users too.
 
Hey Barry.

Is Raylight for Windows a plug in for various programs that allow drag and dropping of mxf file directly into a sequence or timeline?

Is that the benefit, or prime benefit?
 
I didnt mean to imply that it was a problem, its just a different way of getting the footage into the editor. The main issue to me is that it takes more time to import, and there are many times I would be much further along in a project if I could cut out 10-30 minutes of import time. Talking with Barry Green at the Texas Production Roundup last week made me see what I was missing with native MXF handling. I think that if more FCP users saw what programs like EDIUS do with the native MXF handling they would all be screamin at apple for not implementing it into FCP. For me FCP is still the best tool for the job, and I have a ton of money invested in my editing system, so I am somewhat stuck. I just really wish apple would get off their butts and put that feature in FCP.
 
David S. said:
Is Raylight for Windows a plug in for various programs that allow drag and dropping of mxf file directly into a sequence or timeline?
Click to expand...
Yep. With Raylight installed, Vegas or Premiere Pro can now edit MXF files just as easily as if they were .AVI or Quicktime files. You plug in your card, and drag the MXF files right to the timeline and edit.

You can do so straight from the cards, or straight from a P2 Store, or your external drive or wherever you've copied the cards to.

It has many other features, but that's the main reason I say it's a must-have for Vegas or Premiere users. I mean, it can also convert the MXF files into AVI files (same workflow as FCP uses to convert MXF files into QT files) but editing the native MXFs just blows away the converted-file workflow.

And it's coming for the Mac, soon.
 
Actually, it's kind-of a problem. Seein as how you have to store those Quicktime files somewhere, right? So that's the Quicktime files AND the MXF files that you have to archive, unless you want to reconvert the MXF later when/if you come back to the project.

That's kinda whack, IMO. But, it works still. I'm stoked about FCS2 regardless of non native .MXF editing.
 
While I would love Apple to fix this (and they will say it isn't broken), I will look forward to Raylight. But the flip side, which is just to immeadiatly dump the P2 cards straight into FCP isn't that bad and then you can dump the cards.

About 6 to 8 months ago it was a big deal and Jan at Panasonic said that your MXFs should be treated like a negative. I argued that if the MXF was just a wrapper, than who cared if the new wrapper was now Quicktime. As long as the pixels are not changed, just the wrapper then I really think you are good to go.

I changed my work flow to RAID level 1 so I always have identical copies of everying while working, and then back that up too.

Right now I am an Apple FCP shop only so I don't need to work MXF natively, but I'd like to so that I may more easily work with non FCP editors if need be.

--
Rob
 
You must log in or register to reply here.
Back
Top