Controls and Menu Items

[Finner]

Have you fixed how level control will be implemented? Will it be a menu item or a physical control on the camera?

Martin

Great question. This is one thing I have been really concerned about because if sound level controls are a menu thing I can see it becoming a big pain in the butt.

[Trevor Meier]

Using "look" files we can create any color corrected 4:2:2 HD-SDI output (or for that matter 1080p or 720p RGB video for recording to the Digital Magazine) we desire for each scene off-line and then load that data into the camera via SD cards or via wireless or USB interfaces....

The USB port on the camera allows us lots of flexibility to offer additional control surfaces for special applications.

IF RED makes their API available, a third party (or RED themselves) could develop a camera remote. This could be a hardware device or in software (say, in Java or some other platform-agnostic language). Run it on a laptop, a PDA or a cell phone, connect via USB or better, wirelessly (via bluetooth or WiFi connected to the USB or SD slots).

There's three 'domains' this could be useful in: camera control, metadata, and audio control. One device could operate in all three domains, or if the crew is large enough, it could be divided amongst departments:

1. Camera Control is given to the device operated by the First AC. Camera start/stop, enter timecode, frame rate, load "look" LUT, etc.
   
2. Metadata read/write is given to the device operated by the Script Supervisor: use it to input metadata (Scene number, take, etc.) to create a digital slate (a la David Fincher's S-Two tapeless workflow); use it to read the current metadata for entering into digital or analog script notes.
   
3. Audio control is given to the audio guys: remote audio level metering, remote level control and/or remote fader control of audio levels using a simple USB device like the tascams: http://www.tascam.com/Products/US-224.html
   (You could even stream audio to the camera from a digital mixer over the USB ports... But USB audio is notoriously unreliable)

This would feed into the data-centric workflow we're talking about over in the 4K workflow forum