RED One SDK?

[Gregory Karydis]

I know time is of the essence for the release of RED One so new features will not be very easy to implement from the ground up at this juncture.
So this may not be feasable at all OR other plans are in motion to allow third party developers to build plugins or custom software functions to take advantage of the cameras' hardware features.
My self coming from a bit of a programmers' background, I would like to have the ability to make custom menus for faster operation; by limiting the number of options, be it as an XML (like others have suggested) or a plugin for the cameras' firmware.

I have a feeling I may have placed this thread in the wrong forum... then again I may be wrong

 

[Phil Becque]

Well I think that's a great idea - some way to customize the things that people get so worked up about on this forum would be really good. Maybe some kind of serial interface that you could upload code or XML or pick your preferences would be feasible - but maybe not in RED ONE?

All the best, Phil

 

[Gregory Karydis]

What I have in mind is; as many devices' instruction manuals state:
This device complies with so and so rules. Operation is subject to the following conditions:
This device may not cause interference, and this device must accept any interference, including interference that may cause undesired operation of this device.

That way, anyone can build custom functions to thier hearts' desire without requesting features that won't be implemented by the official release of the firmware.

To that effect, RED One could have a "Master Reset" function so in case some %$#@ messes things up by trying to customize it, you could still return to having a functional camera (that %$#@ person will remain an %$#@ no matter the Master Reset)

 

[Stuart English]

Customisable menus

Customisable menus

Its our goal to strip out all the menu clutter that has found its way into video cameras because of the need to paint the image to fit an 8 bit very limited dynamic range and color space tape or disk transport. So as a general guideline we are following a film camera body + video assist + telecine operational philosophy - just speeding that workflow up & making that "equipment package" much more affordable and much more mobile = RED_ONE + REDCINE.

So from that background, yes there is still some scope for 3rd party / user menu adjustment - not necessarily in-camera, but certainly when running it from an external application. We'll have to wait to explain more until after we finish in-field testing.

Over time, with end user feedback, we have the infrastructure to adjust our own in-camera menus using application templates.

 

[Sean Michael Johnston]

We'll have to wait to explain more until after we finish in-field testing.

So does that mean you're in field tests now?
Are y'all documenting the field testing? If so, it would be great to see some pics of the camera in action.

 

[Gregory Karydis]

We'll have to wait to explain more until after we finish in-field testing.

Need any help with in-field testing?
Pleeeeease, I can fly from Greece
I wish, but my dentist will kill me if I quit while we are half way through

 

[donatello b]

"Its our goal to strip out all the menu clutter ...."

thank you , thank you , thank you !!!!