ThomSteinhoff
Member
Well, like most of you, I have been dreaming of features I would like to see on my Red One. I didn't make it in time for the contest, but I don’t need a contest to have me think of things I’d like to see in my future camera. So, here's my idea:
If the camera could be an on-set web server, either wireless or wired, where a script supervisor could use “Red Code Remote” software, running on a laptop, to post scene information to the camera (Via HTTP Post) which would then be added to the next shot as metadata, that would eventually be handed over to a NLE, pre-logging all of the shots. This onset pre-logging would save tremendous amounts of time in post.
Once the shot has been tagged, users of the remote software should be able to update the shots still on the attached hard drive with more details that may come up after the shot is done (director notes, quality, etc).
Ideally, this “Red Code Web” server would also stream an MP4 video stream in an IP broadcast to whoever is attached to the “Red Net”. This would allow for N number of participants to record on their own laptop/tablet computers an on-set, NLE view, of the footage without video cables.
The remote shot logging software should be able to store locally DV quality footage if necessary for on-set playback to check continuity or performances, without having to go to the camera. Down the line, software that included the ability to store pre-vis shots and replace them with real footage (that is connected via the metadata to the actual footage) would be an amazing addition to the workflow.
So, the script supervisor logs and tags, and everyone else getting the feed (director, producers) get a fully tagged version that they can record onto their own playback system so they can replay, or refer back to prior shots without slowing everyone else down .
Of course, there is the obvious desire to remote manage and control the camera (to allow an additional set of eyes on the monitors, remote set of hands on the dials or remote triggering) so, please include those features in with this as well.
In Summary: On Camera web server, maybe with it’s own DHCP/equiv server and only accept traffic from locally, camera assigned, IP addresses (to avoid some idiot hooking his camera to the internet allowing for the first RED Virus) an HTTPPost page to post XML requests the camera and streaming to an IP broadcast channel, a UDP broadcast of triggered events (camera start, camera stop, etc) Eventually, a Red “SDK” could be made public to allow 3rd parties to create cool set management applications.
Anybody else think this is a good idea?
If the camera could be an on-set web server, either wireless or wired, where a script supervisor could use “Red Code Remote” software, running on a laptop, to post scene information to the camera (Via HTTP Post) which would then be added to the next shot as metadata, that would eventually be handed over to a NLE, pre-logging all of the shots. This onset pre-logging would save tremendous amounts of time in post.
Once the shot has been tagged, users of the remote software should be able to update the shots still on the attached hard drive with more details that may come up after the shot is done (director notes, quality, etc).
Ideally, this “Red Code Web” server would also stream an MP4 video stream in an IP broadcast to whoever is attached to the “Red Net”. This would allow for N number of participants to record on their own laptop/tablet computers an on-set, NLE view, of the footage without video cables.
The remote shot logging software should be able to store locally DV quality footage if necessary for on-set playback to check continuity or performances, without having to go to the camera. Down the line, software that included the ability to store pre-vis shots and replace them with real footage (that is connected via the metadata to the actual footage) would be an amazing addition to the workflow.
So, the script supervisor logs and tags, and everyone else getting the feed (director, producers) get a fully tagged version that they can record onto their own playback system so they can replay, or refer back to prior shots without slowing everyone else down .
Of course, there is the obvious desire to remote manage and control the camera (to allow an additional set of eyes on the monitors, remote set of hands on the dials or remote triggering) so, please include those features in with this as well.
In Summary: On Camera web server, maybe with it’s own DHCP/equiv server and only accept traffic from locally, camera assigned, IP addresses (to avoid some idiot hooking his camera to the internet allowing for the first RED Virus) an HTTPPost page to post XML requests the camera and streaming to an IP broadcast channel, a UDP broadcast of triggered events (camera start, camera stop, etc) Eventually, a Red “SDK” could be made public to allow 3rd parties to create cool set management applications.
Anybody else think this is a good idea?
Last edited:
I kid I kid.