FCP import Native (L&T) - Large files

[roryhinds]

When you import a R3D via FCP's Log&Transfer using NATIVE as the setting why does the imported file come in as a REDCODE QT file the same size at the .R3D file?

It seems to be coping the R3D file and wrapping the QT Proxy in the same file.

Why can't it just make a "Proxy" ref file which links to the R3D instead of duplicating the data?

 

[Noah Kadner]

That's not how it works unfortunately- it's a rewrapped QuickTime- not native .R3D editing. Only Adobe CS4 has that but not perfected by any means. If you want proxy- edit with the camera proxies, that's still the most expedient workflow.

Noah

 

[Luca Immesi]

Try this:
http://www.reduser.net/forum/showthread.php?t=22562

 

[JD Marlow]

Like Noah said, editing with QT proxies would be what you're looking for. Although the processing power needed to edit with the proxies is similar to the QT wrapped R3Ds.

One workflow that I like is transcoding at low debayer for offline, then media managing and reimporting QT wrapped R3D via Log & Transfer.

From there you can go out to anything, including DPX if you have GlueTools.

The clipfinder method works, too.