REDCINE, Proxies, and Sound

[Tim Fassnacht]

are the QT refs displaying changes to R3D metadata in FCP?

For Example:
If you were to say start cutting with a slew of proxies in FCP then run back into REDCINE because you noticed some coolness in a particular shot and corrected and saved that R3D in REDCINE-- would that color info change translate to your proxy already cut into your timeline? All theory aside here- has anyone tested this?


And whats the deal with sound. Is the plan to have that translate track for track along with the QT proxy? -Or, merge all data to a stereo scratch-track in the proxy for offline? I know it doesn't work yet, (bummer) but I'm curious what Red plans to do with it in regards to the workflow they've already established.

Thanks Guys

 

[NateWeaver]

If you were to say start cutting with a slew of proxies in FCP then run back into REDCINE because you noticed some coolness in a particular shot and corrected and saved that R3D in REDCINE-- would that color info change translate to your proxy already cut into your timeline? All theory aside here- has anyone tested this?

Yes, I've done it. It works as expected, the changes made in Red Alert to exposure, color temp, etc show up in FCP.

As far as I know though, RedCine does not save out QT proxies as the camera and RedAlert do.

 

[Tim Fassnacht]

Thanks Nate-

Anyone have any ideas about the SOUND?

Jim- care to weigh in here? Graeme?

Thanks

 

[Rob Lohman]

1) nothing can save or alter R3D files

2) REDCINE can't save QuickTime reference files

3) RED ALERT can save QT reference files, and so these can be updated with most of the settings you can set in RED ALERT, but not all (like curve, color space & gamma)

4) QuickTime files will have 4 audio tracks if you recorded 4 tracks etc.