Camera Preset Persistence / Memory?

[beast257]

I know we are in danger of what we have with the sound desk, but I just thought: wouldn't it be nice if we could have sets of camera presets for visuals operators who use the same or similar presets each week, or for events that require certain positions every time?

Eg, I have to setup the same 3 camera positions every week at the marriage course, and I know that normally at least 3 if not 4 or 5 of my camera presets stay the same each week. Plus being able to load a preset would make it easier to transition between sets if I for example need access to 8 or 9 presets in a service - I can set some in advance in a different memory bank.

I don't know how feasible that is, just a thought. It might need to be more stringently regulated than on the sound desk, eg tracking date of entry, and deleting if unused for more than say 6 months.

[jamesremuscat]

Certainly possible; the first step would be to keep the UI the same, but internally stop using the cameras' built-in preset mechanism and instead use the "tell me your position" and "go to this position" commands to store presets client-side (and I do mean client, not controller).

Patches welcome ;)

[jamesremuscat]

I discovered last night that the camera's white balance setting is also stored in the presets. (Which sort of makes sense, if you think about it.)

[rjmunro]

When you say "I do mean client, not controller", what is client and which is controller? Is the controller not the thing with the touch screen, i.e. a type of client?

[sedontane]

I would assume client is the RPi connected to the touchscreen and the
controller is the server room RPi doing the actual control of the devices

On 19 August 2013 11:54, Robert (Jamie) Munro [email protected]:

When you say "I do mean client, not controller", what is client and which
is controller? Is the controller not the thing with the touch screen?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/29#issuecomment-22864111
.

[jamesremuscat]

I would assume client is the RPi connected to the touchscreen and the
controller is the server room RPi doing the actual control of the devices

That is correct.