We do not plan a set of protocols for Video server developers to adopt, rather we are planning on adding both hardware, as a video wing, and software to the lighting console to make control easier. We will then add a software layer to adapt to each video server supplier's mode of operation and interface to try and achieve a consistent working environment.

We have had a number of suggestions and requests for features, and the purpose of this is to involve as many Video server users as possible in defining a versatile product.

On the hardware side a video wing may have a number of extra playback masters as well as an area dedicated to improving the programming / playback of video content.
One example could be to add flying faders or encoders that can be assigned a selected number of parameters (with offset and scaling) that are active when a cue stack is activated, giving manual control or busking during play back. This would not involve the programmer(s), they would remain free for other use. The selected parameters would be assigned in the programmer during programming for use when the cue or cue stack is run.
Another might be to add a set of layer select key switches, to speed up programming.

The system we currently demonstrate uses both UDP and TCP sessions, but as you say sticking to UDP makes coding a lot simpler.