Introduction From v2.0.4 onwards, CasparCG Server adds support for the Open Sound Control (OSC) protocol which sends real-time data and events from CasparCG Server over UDP to a client. In CasparCG Server, the OSC implementation provides one way support only, CasparCG Server provides a client interface, sending status information to an OSC server but does not listen for OSC datagrams from remote clients.

Navis Media provides most simple CasparCG sport clients in the market. Set up graphics, connect client to server and show the world who's the best! Sep 28, 2017 - Improving CasparCG Client to show Live Comments from Flash Template that using XML data from web application called LiveComments.

Connection When a client establishes a connection to the AMCP port configured for the server, an OSC client is started by CasparCG Server against the AMCP client's IP, using a default UDP port configurable in casparcg.config (see below), this OSC client will expire when the AMCP connection that initiated it ends. Persistent OSC clients can be set-up by adding them to the list of persistent clients in CasparCG config (as below). Clients receive events by connecting to the OSC client interface provided by CasparCG Server, and then issuing a RegisterMethod command to subscribe to different properties and actions made available by the CasparCG Server.

Looking at the source code for the Caspar Monitor example client, in particular Form1.cs would be a good place to start in understanding CasparCG Server and OSC. Configuration The following is an example of the configuration entries which relate to the OSC implementation, as described above, persistent OSC clients can be added to the list of predefined clients by adding a element, in the example below, an OSC client is defined for an OSC server on localhost port 5253. OSC clients must defined by ip address not hostname. 6250 127.0.0.1 5253 OSC Messages The OSC protocol uses a fairly simple message structure containing an address pattern and various arguments corresponding to each pattern, the protocol also includes other detail as described on the Wikipedia entry. The below is a list of address patterns and details of what response subscribing to this will trigger, this list is currently a work in progress and does not represent all of the addresses available, the example client by Andy Mace at the bottom of this page will show you what your CasparCG Server is doing live.

Like Show likes. Share Show shared copies. Kazahskie shrifti dlya word 2007 free.

It is important to note that OSC sends messages for things that are active only, if CasparCG Server is not doing anything you will only see a small number of lines. Number ranges such as [0-9] should be substituted for the appropriate channel, layer or output port you are trying to monitor. Cara hack password wifi menggunakan wireshark for mac. More than one digit is acceptable in all of these cases but not specified for brevity. Output and Channel setting Messages Output messages contain information about CasparCG Server Consumers, this largely contains information about which Consumers are active, alongside this are other messages such has format and profiler messages which contain more information about what the channel is doing. Address Example Arguments Description /channel/[0-9]/ format PAL The of the channel profiler/time 0.041 0.04 The amount of time that CasparCG Server is spending rendering the frame, two arguments are sent in this message, what it is and what it should be as shown in the example. Output/port/ [0-9]/type screen A message like this will exists for each of the outputs in use, with the default CasparCG config file in use this will result in two rows; one of type screen, and one of type system-audio.

Current types are, system-audio,, and output/port/[0-9]/frame 200 88836854 The number of frames that have been created by the consumer on this port, the example indicates that 200 frames have been written to disk and that a maximum of 88836854 can be written. Stage Messages Stage messages contain properties related to CasparCG Server layers and the producers that are contained within them. General Stage messages The following messages do not directly relate to a producer. Address Example Arguments Description /channel/[0-9]/stage/layer/[0-9]/ time 101.24 Seconds the layer has been active frame 2531 Time in frames that the layer has been active type transition background/type empty profiler/time 0.39 0.4 Actual Expected time on frame paused True/False Whether the layer is paused or not FFMPEG Producer The messages produced by the FFmpeg Producer are documented on. Flash Producer The messages below may be produced when an object utilising the is in use on the stage. Address Example Arguments Description /channel/[0-9]/stage/layer/[0-9]/host/ path template_file.ft width 1920 height 1080 fps 50 /channel/[0-9]/stage/layer/[0-9]/ buffer Mixer Messages The majority of information from CasparCG's compositing module is not yet made available via OSC (an issue is open for this), the only information available currently is audio related as listed below. Address Example Arguments Description /channel/[0-9]/mixer/audio/ nb_channels 2 Number of audio channels in use on this CasparCG channel [0-9]/dBFS -20 Audio level in dBFS Example Clients A couple of members of the CasparCG community have constructed simple OSC example clients to demonstrate its use, these are available from the links below.