Free tool
OSC Message Builder
Type an OSC address and add integer, float and string arguments. See the OSC 1.0 packet as hex, with the address, the type tags and each argument broken out, null padding included, and the length in bytes.
Runs entirely in your browser; nothing is sent or uploaded. The URL updates as you work, so a message can be shared as a link.
Message
Type the address, then add the arguments in the order the receiver expects them.
Addresses this site documents
Each example is an address that appears on the page linked beside it. Choose one to fill in the message.
- Layer 1 opacity. From OSC Setup Guide
- Trigger clip 3 on layer 1. From Resolume Arena/Avenue Setup
- Start cue 3. From OSC Setup Guide
- Press Go on an Eos console. From ETC Eos integration
- Energy value. From OSC Setup Guide
Encoded packet
- Packet length
- 32 bytes
- Type tags
- ,f
- Arguments
- 1
Hex
2F 6F 73 63 69 6C 6C 61 74 6F 72 2F 34 2F 66 72 65 71 75 65 6E 63 79 00 2C 66 00 00 43 DC 00 00
Byte breakdown
| Field | Value | Bytes | Padding |
|---|---|---|---|
| Address | /oscillator/4/frequency | 2F 6F 73 63 69 6C 6C 61 74 6F 72 2F 34 2F 66 72 65 71 75 65 6E 63 79 | 00 (1 byte) |
| Type tags | ,f | 2C 66 | 00 00 (2 bytes) |
| Argument 1 (float32) | 440 | 43 DC 00 00 | none |
CueSync sends OSC from its cues, to any address and argument list you define. With a free account you can run the demo show and tour the app in read-only mode. Download for Mac, free account.
The three argument types
The builder encodes the three types that cover most show-control messages. Each has a one-letter tag in the type tag string.
| Tag | Type | Encoding |
|---|---|---|
| i | int32 | 4 bytes, two's complement, big-endian |
| f | float32 | 4 bytes, IEEE 754, big-endian |
| s | string | ASCII bytes, a null, then nulls up to a multiple of 4 bytes |
OSC questions, answered
- What is in an OSC message?
- Three parts, one after another: an address pattern such as /layer/1/opacity, a type tag string that starts with a comma and has one letter for each argument, and the arguments themselves. Address and type tags are strings, and every part of the packet is a multiple of four bytes long.
- Why is there padding after the address?
- An OSC string is its characters followed by a null byte, then more nulls until the length is a multiple of four. An address of exactly four characters therefore still gets four null bytes after it, because the terminator has to fit. The breakdown shows the padding of each field separately.
- Which argument type should I use?
- The one the receiver expects. A receiver that wants a float will not always accept an integer with the same value, and the reverse. The type tag string in the packet says which was sent, so check it first when a message arrives and nothing happens.
- Are numbers big-endian?
- Yes. OSC 1.0 sends int32 and float32 with the most significant byte first. The integer 1000 is 00 00 03 E8, and the float 440.0 is 43 DC 00 00.
- Does this send the message?
- No. It builds the packet and shows the bytes, which is useful for checking what a sender produces, writing a test, or reading a capture. OSC normally travels in a UDP datagram, and the datagram holds exactly these bytes.
- What does the address start with?
- A slash. Each slash-separated part names a container or a method on the receiver, and the receiver decides which addresses exist. The builder checks the shape of the address, not whether any receiver will recognise it.