dchenevert
Member
My home router (a $79 Cisco) has a WWW-based user interface, to allow
users to modify its status and settings.
Could the RED camera support this kind of interface? I'm assuming that
the RED internal electronics are already going to be built around something like the
following... if not, then "never mind" for this idea.
* a CPU running an RTOS or other operating system
* a network interface (Wi-Fi? IP over USB?)
* software to serve web pages (supplied by the OS vendor, I would guess)
* camera-controlling drivers used by the regular button-and-screen user-interface
software.
The point to this idea would be to (a) lighten the requirements list for the button-and-screen
user interface, which needs to be completed in a tight time frame; and (b) allow
an arbitrarily powerful, extendable, and upgradable UI through the WWW interface. The user
would hook his PC to the RED one (using Wi-Fi or USB or whatever), and starting viewing
and controlling camera internal features and wonderfulness. You know, "rendering
obsolescence obsolete" and all that.
The button-and-screen user-interface could be shipped with version 1.0 of RED-one,
and then the WWW UI could be in a future firmware upgrade.
David
EDITED LATER: The 3d item on my list ("software to serve web pages") is
probably *not* already include in the RED-one parts list. What I mean is that
maybe it is available from the OS vendor or a 3rd party that sells software
for that OS. If there is an OS (see the 1st item).
I may have this wrong, but I vaguely remember hearing that even
low end consumer cameras run an RTOS like VxWorks from Wind River.
users to modify its status and settings.
Could the RED camera support this kind of interface? I'm assuming that
the RED internal electronics are already going to be built around something like the
following... if not, then "never mind" for this idea.
* a CPU running an RTOS or other operating system
* a network interface (Wi-Fi? IP over USB?)
* software to serve web pages (supplied by the OS vendor, I would guess)
* camera-controlling drivers used by the regular button-and-screen user-interface
software.
The point to this idea would be to (a) lighten the requirements list for the button-and-screen
user interface, which needs to be completed in a tight time frame; and (b) allow
an arbitrarily powerful, extendable, and upgradable UI through the WWW interface. The user
would hook his PC to the RED one (using Wi-Fi or USB or whatever), and starting viewing
and controlling camera internal features and wonderfulness. You know, "rendering
obsolescence obsolete" and all that.
The button-and-screen user-interface could be shipped with version 1.0 of RED-one,
and then the WWW UI could be in a future firmware upgrade.
David
EDITED LATER: The 3d item on my list ("software to serve web pages") is
probably *not* already include in the RED-one parts list. What I mean is that
maybe it is available from the OS vendor or a 3rd party that sells software
for that OS. If there is an OS (see the 1st item).
I may have this wrong, but I vaguely remember hearing that even
low end consumer cameras run an RTOS like VxWorks from Wind River.
Last edited: