TC syncing

[Rainer Fritz]

thx noah again for your help...

[Noah Kadner]

Just a fun thought

If you use something like episode, (which exports qt-formats), would it be possible to batch process?

Gunleik

Episode or Compressor- but you'd be batch processing the QT proxies created by the camera. Only Red Alert can directly open the .R3D files.

My question for Graeme would be- if I open say a 2K QT proxy in Episode and export a 4K ProRes- am I actually getting access to the 4K .R3D original for the conversion or just upconverting the 2K proxy to 4K?

-Noah

[Gunleik Groven]

Ah... So there's still no RAW QT component...

Got it.

Cheers!

Gunleik

[Rob Lohman]

Noah: you will be upconverting. A 2K input source is a 2K input source (for applications that can't access the R3D directly, unlike RED ALERT! / REDCINE / Scratch)

[humanwire]

I'm new to this forum. Hello everyone.

I'm doing production sound on a Red shoot right now, and the timecode I see on the monitor always seems to be a bit off, maybe about a 1/2 second. The only way to tell has been to check it by eye. The Denekey slate and the TC on the recorder are solid, but the TC display on the Red monitor is always 1/2 second off and it does not seem to drift from that the whole shoot. I have a Clockit timecode generator (jammed from my recorder) connected to the camera at all times via the 5 pin Lemo cable. The Denekey slate was jammed from the Clockit box, so the slate and the camera should theoretically be running perfectly in sync.

Note: The Red does not jam the timecode being input until you are recording. When it jams, the little chain link icon appears at the top center of the monitor after the first take is stopped.