XDCAM Transfer crashes Suite 1.6 on import

[Olof Ekbergh]

Jay,

I find that in order to work efficiently with XDcam footage in FCP I have to transcode it. Otherwise I am forever rendering to see how things really look.

So the way I look at it is do the transcode up front in M100 and then work really fast. FCP will let you edit the mpeg video but you have to render all the time, even cross fades, it drives me crazy. In M100 even titles play real time in full res. This is a huge plus for me.

I see the compact mpeg files as tape, great for archiving. But not a good editing codec.

So this is why I like to sometimes even do very simple rough cuts in FCP and then bring only the footage I need into M100 as ProRes or whatever.

This works really well for me anyway, I use both programs for what they are good at.

I would love be able to edit the mpeg files in M100 and I have talked with M100 about this. It may happen in the future. But the reason M100 is so fast at editing is the very efficient architecture, and currently it does not work with long GOP codecs (I can see why).

Life is always a compromise. I use at least 10 different programs and plug ins when editing and delivering my projects. All have strengths and weaknesses. M100 is incredible fast and efficient at what it does, in my opinion.

Olof Ekbergh

[Floh Peters]

[olof ekbergh] “The Apple XDCAM EX 1080p30 (35 Mb/s VBR), 1920 x 1080 (1888 x 1062), Millions, is the rewrapped EX file. This is basically what XDcam Transfer app does. “

The other option you could do is to let the ClipWrap software do the transcoding to ProRes 422 as well as the rewrapping. This way you end up with only one file instead of 2; it still will be larger than the original stream, though, but it is much easier to edit ProRes footage than MPEG2 streams.

[Jay Ryscki]

Thanks for all the feedback on this examination. While I have deep understanding and respect for the M100 environment, I struggle with the incomplete “solution” that the Suite 1.6 delivers. I have hung on to the SD M100 model a year longer than I thought I could get away with and continue to produce content on it.

But I am done with tape now. I am happy to compromise to produce the same results I deliver now, compelling content. Where I see the challenge is in the sometimes convoluted media management area. M100 has always let me excel in this area, the current tool falls short primarily with challenges in sorting out files for archive. When the digital model truly emulates the tape model for restoring footage, I’ll be there. In the meantime, this cobbled together approach to integration could use a champion. Calibrated Software has some good ideas, but they are still short on the execution.

If Suite 1.6 could overcome the XDCam conforming choke point, I could live with the results. What I have trouble justifying is sacrifice I make in creative editing energy, every time I need to put the computer geek hat on. M100 has let me leave that hat on the hook for years. I’d like to leave it there…

thanks again to all…

[Matt Mullen]

Jay,

Are you getting the crash only when importing directly from the SxS cards? I don’t believe we have any of these in house to test with.

What is the nature of the crash, does it produce an error report?

If it does could you please send it to mattm@borisfx.com or support@media100.com

-Matt M.

[Jay Ryscki]

Hey Matt- Did you get my email?

[Jay Ryscki]

Hey Flo,
ClipWrap does not support the XDCam files in native format

[Floh Peters]

Sorry, I got lost somewhere. I thought you were speaking about AvcHD