# OSC trigger help

**URL:** <https://casparcgforum.org/t/osc-trigger-help/7081>\
**Category:** General\
**Tags:** client\
**Created:** [January 14, 2025, 4:02pm UTC](https://casparcgforum.org/t/osc-trigger-help/7081 "2025-01-14T16:02:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Petter\_TV12](https://casparcgforum.org/letter_avatar_proxy/v4/letter/p/dc4da7/32.png) [@Petter\_TV12](https://casparcgforum.org/u/Petter_TV12)\
**Post date:** [January 14, 2025, 4:02pm UTC](https://casparcgforum.org/t/osc-trigger-help/7081/1 "2025-01-14T16:02:47Z")

</div>

Trying to trigger templates in Caspar client from Companion. Tried following tutorial linked in a different post on here, but no dice. Regardless of what IP or port I try to use (localhost or LAN) and where Companion is located, it doesn’t respond to anything. UID is set, all ports and IP is open on the firewall, and everything is set up in the Client settings as instructed in the other post. What could be the issue?

---

<div class="post-metadata">

**Author:** ![andyw](https://casparcgforum.org/letter_avatar_proxy/v4/letter/a/f05b48/32.png) [@andyw](https://casparcgforum.org/u/andyw)\
**Post date:** [January 16, 2025, 12:08pm UTC](https://casparcgforum.org/t/osc-trigger-help/7081/2 "2025-01-16T12:08:09Z")

</div>

I’m assuming you are using client V2.2 or V2.3. I also assume you have set your client OSC preferences in a similar way to screen grab shown below.

 ![Client_OSC_setup](https://casparcgforum.org/uploads/default/original/2X/2/297c7917b0e96461e3578eb88d369074e7e78003.png)

The client uses the OSC monitor port number to listen to status data from the server, driving the audio meter displays and the clip progress bars. This requires ther OSC output port in the server to be same number as the client monitor port.

The enable OSC control tickbox must be active when you want the client triggered by an OSC message. The listen port number must match the port number you set for an instance of generic OSC output from companion. The web socket enable and port number are needed when using a web page to send OSC traffic.

When you have enabled an instance of the generic osc output driver in companion you can allocate a button to use that instance. The message from Companion must include an address of the format: `/control/myTriggerLabel/play` and carry an **integer** parameter with the value **1**. The target UID for an item in the rundown is **myTriggerLabel**.

If you add an OSC Output to your client configuration you can also send OSC messages from the client. These can be directed at itself by setting the destination address as `127.0.0.1` and the port number matching the enable osc control port number. You can add an OSC output item to the rundown, selecting the destination from a dropdown list. Set the output type to integer and set a value of 1.

If you need a list of allowed control names (play, stop etc) I list these in my “Introduction to CasparCG Graphics System” document available [here](https://github.com/amwtech/CasparCG_Documentation) on GitHub. The description of OSC in Caspar starts around page 117, with the command verbs listed on page 120. There is also a description of how to set up StreamDeck/Companion to send messages to the CasparCG client on page 89.