The OSC API behaves almost identically when using both UDP and TCP. When sending message to Go Button from QLab, set the Go Button UDP Reply Port to 53000 to be able to view Go Button reply messages in the QLab Workspace Status > Logs window. For example, sending the string /cue/1/start as text to Go Button on UDP port 53535 will have the same result as sending an actual OSC message /cue/1/start to the current TCP/UDP Listening Port (e.g. Go Button also listens for plain text on UDP port 53535 and attempts to interpret it as OSC.
When a client talks to Go Button via TCP, messages are framed using the double end SLIP protocol ( RFC 1055) as required by the OSC 1.1 specification. Replies to OSC messages received via UDP are sent on the port specified in the Sidebar > OSC Control Settings > Network > UDP Reply Port. When a client talks to Go Button via UDP, each OSC message corresponds to one UDP datagram. The default listening port for TCP and UDP is 53100. Go Button listens for incoming OSC messages and sends replies on the ports specified in the Sidebar > OSC Control Settings > Network section. The Go Button OSC API can be used over both UDP and TCP transport layers.
OSC messages are sorted more or less alphabetically in each section, which is to say they’re alphabetically sorted, but messages which are closely related to each other are sometimes grouped together even if they are not alphabetically adjacent if that makes it easier to understand their relationship. What follows here is a complete dictionary of Go Button’s OSC implementation.
#QLAB OSC HEARTBEAT SOFTWARE#
Go Button has an extensive API (application program interface) for OSC which allows you to control Go Button from any device or software which can broadcast OSC messages.
0 kommentar(er)
