ChamSys, Arkaos and Capture, three of the fastest growing software developers in the lighting and media server markets today, have developed an open network protocol called CITP/MSEX. Companies like Martin, ETC and Green Hippo are beginning to join the parade by implementing the protocol into some of their latest products including Maxedia, Congo and Hippotizer. The importance of the CITP protocol is that it allows transmission of video data via ArtNet. Along with layers for DMX, information for selections of fixtures, reports and patching (PINF, SDMX, FPTC, FSEL, FINF, and OMEX), CITP also transmits a layer for live streaming video from a media server (MSEX) over Ethernet. Having this protocol means that applications can now share video in real time, allowing thumbnails of video content as well as streaming video to be displayed either on a lighting console or in a visualizer.
What Is It?
To quote the CITP standards posted on the workgroup Web site, www.citp-protocol.org, “CITP is an open protocol for integration of lighting controllers, media servers and visualizers on a higher-than-control level. It makes it possible to browse a media server with thumbnail previews of content as well as effects, to use the correct effect-specific parameter names while programming and to preview output from a controller or visualizer. It also allows bi-directional DMX, device selection and patch transfer to and from visualizers.”
Just How MSEXy is it?
The Media Server Extensions layer is the part of the suite of protocols that is used for communication between a controller and a media server. It allows information for specified elements to be passed from the media server to the console and/or visualizer. There are currently eight element categories included in the data stream and if you’ve ever used a media server then they should sound familiar to you. They include media (images and video); effects; cues; crossfades; masks; blend presets; effects presets; and image presets.
MSEX 1.0 is based on the adopted media server standard of using one DMX512 channel to control the media library and one to control the media file. In this configuration, MSEX 1.0 can transmit information for up to 256 libraries, with each containing up to 256 items or clips.
Even though currently most media servers are not designed around two DMX512 channels to control library and file elements, MSEX 1.1 expands the data that can be transmitted between devices to three library levels with a maximum of 256 discrete elements each and has been implemented in several new products, including: ChamSys MagicQ and Martin Maxxyz consoles; Arkaos Media Master and Martin Maxedia media servers; and the Capture visualizer.
Advantage CITP: Consoles
There are several advantages to be gained by using CITP protocol in lighting consoles. When you control video devices, CITP/MSEX allows you to see streaming real-time video of the content on the lighting console.
Why is this important? One implication is that media servers may no longer need to be at FOH while programming and/or playing back a show. That’s because the output of the media server can be sent to the console where it can be displayed on its monitor. All of the content in the media server library is also visible on the console, virtually eliminating the need for the media server to be near the console for feedback purposes as well. This will save a tremendous amount of time while programming with a media server because a visual representation of each clip can be used to call up a look instead of using a wheel to dial a DMX number. If the console has a touchscreen you can simply find the thumbnail of the file you’re looking for and select it directly.
Advantage CITP: Visualizers
Using the CITP communication protocol with a visualizer would allow it to receive streaming video from a media server (like Arkaos) and apply it to any object, essentially treating the video as if it were a material. This means your previz of the show can now include streaming video while you are programming your cues for a more realistic rendering of the stage. Currently Capture is the only visualizer with CITP implementation, but others will probably not be far behind.
Your Mileage May Vary
How CITP is implemented between manufacturers is important, but having a de facto standard is a big step forward. Maxxyz and Arkaos have both implemented MSEX1.1 but Maxxyz has not implemented streaming video. This means you will not see live previews on the Maxxyz, but you will be able to view thumbnails sent from the Arkaos. Maxxyz has also not implemented the SDMX layer, which is the part of the protocol that sends DMX, so in addition to using CITP you have to use ArtNet or another DMX-to-Ethernet protocol to control the Arkaos. And that requires you to configure the IP address in the ArtNet window of the Arkaos software as well as the IP in the operating system.
In today’s technology-driven market, smaller innovative partnerships are increasingly responsible for the introduction of relatively affordable products. Powerful and flexible lighting and video control solutions are becoming more readily available thanks to these combined efforts. We are beginning to see reactions from other console manufacturers, and some are now planning to begin implementing CITP. As they do, CITP may become the de facto standard and it may even be the impetus for the industry to adopt it as a formal standard, much the same way DMX512-A is the standard lighting control protocol.
