Custom OSC
Published 31 Jul 2026
Open Platforms in TipLinkThis page assumes you already know what OSC is and have an app that can send it. If you just want VRChat avatar parameters, use VRChat instead, which is set up for that out of the box.
OSC (Open Sound Control) is a simple messaging format that a lot of creative and VR software speaks. TipLink can listen for OSC messages from any of it, and turn each matching message into an alert trigger.
Typical sources: face-tracking software, hardware controllers, lighting desks, audio tools, custom scripts, and games other than VRChat.
Set-up Instructions
-
Open TipLink and go to the Platforms page.
-
Click Custom OSC. It is under the Advanced group.
-
Fill in the fields:
Field What it is Default Account Name A label so you can tell this apart from other accounts. Only used inside TipLink. - Advertised Name The name other apps on your network see when they discover TipLink. TipLink Receive Port The port TipLink listens on. Point your OSC app at this same port. 9100 Message Filters Only messages sent to these addresses create alerts. *is a wildcard. Separate several with commas./avatar/parameters/* -
Click Create Account.
Connecting
On the Home or Platforms page, click Connect next to your Custom OSC account.
TipLink starts listening on the port you chose.
Message Filters
This is the field that matters most. TipLink only creates events for messages whose address matches one of your filters.
| Filter | Matches |
|---|---|
/avatar/parameters/* | Anything under /avatar/parameters/ |
/myapp/button1 | That one exact address |
/lights/* | Anything under /lights/ |
/myapp/*, /lights/* | Both of the above |
A very broad filter such as /* captures everything, and busy OSC sources send hundreds of messages a second. Every one of those becomes an event. Always filter down to just the addresses you need.
Setting Up the Sending App
In whichever app is sending, set the OSC output to:
- Host:
127.0.0.1if the app is on the same PC, or your PC's local IP address if it is not. - Port: whatever you set as the Receive Port in TipLink,
9100by default.
Some apps discover TipLink automatically on the network. Those show it by the Advertised Name you set.
Events You Can Use
| Event | When it fires |
|---|---|
| OSC Message Received | A message arrives at an address matching your filters. |
You can filter further inside the alert, on the address and on the value the message carried, so one connection can drive many different alerts.
Account Settings
Click the person-and-gear icon on your account. Reconnect after changing anything.
| Setting | What it does |
|---|---|
| Account Name | Your label for this account. |
| Advertised Name | The name shown to other apps discovering TipLink. |
| Receive Port | The port TipLink listens on. |
| Message Filters | Which addresses create alerts. |
| Auto Connect on Startup | Connect automatically when TipLink starts. |
Common Uses
A hardware button that fires an alert
Point your controller software at TipLink's receive port, filter on that button's address, and hang any action off it.
Face tracking driving a reaction
Filter on the tracking parameter you care about, and add a value condition so it only fires past a threshold.
Another tool telling TipLink something happened
Anything that can send an OSC message can now start a TipLink alert. Useful for gluing together software that has no other integration.
Sending OSC Out
This page is about receiving. To send OSC from an alert, use the VRChat: Send Custom OSC Message action. Despite the name, it can target any OSC address and port, not just VRChat.
Troubleshooting
No events arrive
Work through these in order: the account is connected, the sending app points at the right port, the address matches one of your filters, and no firewall is blocking the port.
Too many events
Your filter is too broad. Narrow it to the specific addresses you need.
The port is already in use
Something else is on it. Pick a different Receive Port and update the sending app to match. Avoid 9000 and 9001, which VRChat uses.
Messages arrive from the wrong app
Two apps are sending to the same port. Give each TipLink account its own port, or make the filters more specific.
Related
- VRChat - purpose-built for avatar parameters.
- VRChat: Send Custom OSC Message - sending OSC out from an alert.
- Settings - the global OSC options.