OtoMotion Manual

Version 1.4 (2026-10-01) / Applies to: OtoMotion 1.x, Ross XPression 12.5

1. What OtoMotion is

The official name is DBT OtoMotion.

OtoMotion measures the loudness of a line-level audio input to broadcast standards (ITU-R BS.1770-4 / EBU R128 / ARIB TR-B32) and sends the values to XPression DataLinq up to 60 times per second. Design the numbers and bars in XPression and you have a loudness meter on the venue screen. At the same time, a monitoring screen opens in a browser on the measuring PC, so the audio mixer can watch the values there.

What it can do

• Measure up to 8 stereo groups at the same time (for example, "Main" and "Venue PA")
• Calculate Momentary / Short-term / Integrated / LRA / True Peak to the standards
• Send each group's values and bar lengths (0–1) to XPression DataLinq. No calculation is needed on the XPression side
• Save and recall settings per venue as presets
• A "Set as reference" button that automatically sets the input trim from a test tone
• Japanese / English interface

2. Terms

3. Installation

Windows

1. Before extracting, right-click the downloaded zip → Properties, tick Unblock under Security at the bottom and press OK. This stops the Windows warnings for files from the internet (if you already extracted it, delete the extracted folder, unblock the zip and extract it again)
2. Right-click the downloaded zip → Extract All, then put the OtoMotion folder inside it (containing OtoMotion.exe and the start .bat file) anywhere on the PC (for example C:\OtoMotion). The app does not start from inside the zip
3. Double-click OtoMotion を起動する.bat (the file name is Japanese for "Start OtoMotion"). After about 10 seconds the monitoring screen opens in an app-style Edge window
4. On first launch the license screen appears. Save the license.json attached to our email to the Desktop or Downloads, and it appears in the list: press Load next to it (see section 17, License)
5. If you skipped the first step (Unblock), Windows asks first: "The publisher could not be verified" → Run; "Windows protected your PC" → More info → Run anyway
6. Settings, logs and presets are saved in %APPDATA%\OtoMotion (C:\Users\<user name>\AppData\Roaming\OtoMotion). Your settings stay even if you move the distribution folder

Mac

1. Open the zip we send you and put OtoMotion.app anywhere you like, such as Applications (Apple Silicon only. It does not run on Intel Macs. Requires macOS 14 or later)
2. Double-click to start. If Chrome is installed, the monitoring screen opens in an app-style window; otherwise it opens in the default browser
3. On first launch, macOS asks for permission several times in a row: access to the Desktop, Downloads, removable volumes (USB), and the microphone. Click "OK" / "Allow" every time. If you click "Don't Allow", a license saved on the Desktop or in Downloads won't appear as a candidate, or there will be no sound (fix it later: System Settings › Privacy & Security › Files and Folders / Microphone, turn OtoMotion on, then restart OtoMotion)
4. On first launch the license screen appears. Save the license.json attached to our email to the Desktop or Downloads, and it appears in the list: press Load next to it (see section 17, License)
5. When you choose a device and click Apply and save (or, once a device is set, when the app starts), macOS asks for microphone access: Allow it. Right after the very first start (no device chosen yet) you are not asked. If you deny it, the meters stay silent (−∞) and no error is shown. To change it later: System Settings → Privacy & Security → Microphone. On macOS 27 the prompt reads “Allow "OtoMotion" to access the microphone?”. After replacing the app with a new version, the monitor does not open until you answer this prompt (if nothing opens, check whether the prompt is hidden behind other windows)
6. A .app downloaded or received via AirDrop may say it can't be opened the first time. If so, go to System Settings → Privacy & Security → "Open Anyway". Or, in Terminal, run xattr -dr com.apple.quarantine OtoMotion.app
7. Settings, logs and presets are in ~/Library/Application Support/OtoMotion

Tested on: MacBook Pro (Apple M1, 8 GB) with macOS 26.5.2 (2026-09-27). Chrome opens the monitor with a profile dedicated to OtoMotion (~/Library/Application Support/OtoMotion/browser), so your usual Chrome settings and extensions are left alone.

Getting audio at the venue (recommended)

In stadiums and arenas, we recommend a small audio interface dedicated to OtoMotion, fed with two channels from the audio team (the venue's main mix, or a mix of the crowd mics).

Why a dedicated interface: it is never fought over by other software (XPression, streaming software and so on). It is also easy to ask the audio team for "two channels for OtoMotion", and changes to other equipment during the show do not affect it.

How to ask: "Could we have the venue's main mix (or the crowd-mic mix) as two line-level channels? A send whose level does not change during the show (a matrix or a fixed aux send) would be ideal." If the level moves during the show, the hype number moves with it.

4. Reading the screen

The monitoring screen is switched with the four tabs in the header: TOP (the screen shown at startup), Live (what you watch during the show), Settings (section 6) and Presets (section 8). At startup (whenever the screen is opened in a new window) the TOP tab opens. If you reload the same window, you stay on the tab you had open. Switching tabs does not stop measuring or sending, and values you are editing in the Settings tab are kept.

4.1 TOP

This is the first screen you see after starting the app. The waves in the background, the bars along the bottom and the pictures inside the cards move with the incoming audio (the level of group 1 and the BPM).

• Three cards (Loudness meter / Audio-reactive graphics / BPM sync): what you can do with OtoMotion. Start here → on any card simply moves to the Live tab; it does not change any settings.
• Status strip: from the left, Input (device name and sample rate; green = audio is arriving, red = no signal, yellow = test signal), XPression (green = connected, destination and rate per second; red = not connected), Groups (the number of groups and how many of them are band-limited) and Preset (the preset you last loaded or saved; Change opens the Presets tab). The › at the right of each item opens the matching settings page (Input and Groups: "Device and groups"; XPression: "Send to XPression"; Preset: the Presets tab).
• Footer: How to use opens this manual. The DekoBokoTech website link only works when the PC is online.

Keep the Live tab open during the show (the background is only drawn while TOP is shown, so the Live tab carries no extra load).

4.2 Header

A red banner below the header is a warning (for example "Cannot open input device" or "No input for group(s) 5, 6, 7, 8 (this device has 4 ch; …)"). The banner is always one line; long text is cut off with "…" (hover over the banner to see all of it). See Troubleshooting. While a test signal is playing, a yellow banner "Test signal is playing" appears below it. Both banners are visible on every tab.

4.3 Live tab: group cards

Each group has one card, laid out in two columns (a single group fills the full width).

A group with no input is shown faded (for example when its L ch / R ch are above the device's channel count; the red banner below the header lists the group numbers).

With 5 or more groups, the cards switch to a compact layout (thinner bars, slightly smaller numbers). On a 1280×800 screen, 8 groups fit without scrolling. On a smaller screen, only the card area scrolls; the right rail (Start, Stop, BPM) always stays in view.

4.4 Live tab: right rail

On the right of the screen, from the top: Integrated measurement, BPM, and Venue presets.

Below it, the BPM card shows the tempo and beat, with TAP, Sync and so on. See section 16.

The Venue presets card shows the name of the preset you last loaded (or saved), or "—" if there is none yet. Open presets takes you to the Presets tab (section 8). To exit the app, press Quit in the row of tabs at the top of the screen (right of Help). It works from any tab.

5. First-time setup (5 minutes)

1. Connect the audio interface to the PC and start OtoMotion
2. Open the Settings tab in the header and choose Device on the rail on the left. Choose the audio interface under Device (for example Komplete Audio 2 (2ch))
3. Set the Number of groups. For a single stereo feed, 1. To measure Main and Venue PA separately, 2
4. In the groups table, enter each group's Name, L ch and R ch (which audio interface inputs to use). By default Group 1 is 1/2, Group 2 is 3/4, and so on
5. Press Apply and save at the bottom of the screen. The header changes to "Input: (device name)", and in the Live tab the bars move when audio is present
6. Send a test tone from the desk (for example 1 kHz at −20 dBFS) and press Set as reference on the group's card in the Live tab. M / S become −24.0 and sit on the white vertical line (the target) (a trim is applied automatically to match the desk's reference)
7. Once XPression has been prepared (section 9), the header shows "XPression: connected"
8. Save these settings under a name in the Presets tab; next time, just load the preset

6. All settings

Open the Settings tab in the header and the rail on the left lists seven items. Choose an item to show its page on the right (the page you last opened is shown again next time).

Items marked "On save" are applied and saved only when you press Apply and save at the bottom of the screen (nothing changes until then). When you change a value, the save button turns yellow and reads "Unsaved changes — Apply and save", "● Unsaved changes" appears to its right, and a yellow dot appears on the "Settings" tab in the header. Values you are editing are kept even if you move to another tab. Revert puts the saved values back (6.8). No restart is needed after saving, and the app starts with these settings next time.

The Test signal page, the three fields on the BPM page, Light mode on the Display and language page, and the time signature and Auto follow on the Live tab's BPM card take effect and are saved as soon as you change them. Changing them does not mark the settings as unsaved.

6.1 Device and groups

Choose the device and the number of groups on the upper card, and set up each group in the groups table on the lower card (Figure 9). The table columns are # (group number), Name, L ch, R ch, Trim dB, Band (for Custom, Low / High Hz fields appear to its right) and Set as reference. The table's Set as reference works the same as the button on the Live tab's card. It can't be pressed on rows you added by raising the number of groups until you save ("Save the settings first").

6.2 Test signal

So that you can check the band filters, BPM detection and the XPression scene even without a desk or cables, OtoMotion can play a signal it generates itself in place of the audio interface. While it is on, every group measures the same stereo signal (the groups' L ch / R ch settings are ignored and treated as 1/2, so no "channel 3/4 not available" warning appears; Trim dB and Band still apply). Nothing is played through the speakers.

This page takes effect and is saved as soon as you change it (no need to press Apply and save, and pressing it does not change the test signal). While it is on, the input status in the header turns yellow and reads, for example, "Input: Test signal (sine 997 Hz)", and a yellow "Test signal is playing" banner appears just below the header. The banner is visible on every tab: Live, Settings and Presets.

6.3 Target and true peak

6.4 Bar motion

OtoMotion normalises bar lengths to 0–1 before sending them to XPression. The range and motion set here apply identically to the monitoring screen and to the XPression bars.

6.5 BPM

The three fields are Detect from group, beat length ms and beat_hit decay ms. Each takes effect and is saved as soon as you choose (or enter) it, and does not mark the settings as unsaved. See 16.3 for what they mean. The BPM itself, the time signature and Auto follow are on the Live tab's BPM card.

6.6 Send to XPression

The JSON sent to XPression is always nested (a tree): under root there is a folder per group (g1–g8), one for the beat (beat) and one for the MIDI slots (midi), e.g. g1 › mbar, beat › bpm, midi › s1. The values and their meaning are unchanged; only the key placement is a tree. There are 181 keys in total (chapter 11). This tree has been verified in XPression 12.5's Browse DataLinq (2026-09-26; the midi branch is checked in the hardware test of chapter 18).

6.7 Display and language

6.8 Apply and save / Revert (save bar)

The save bar at the bottom of the Settings tab has two buttons.

• Apply and save: applies the "On save" items (Device and groups, Target and true peak, Bar motion, Send to XPression, Display and language) to the app and saves them to state.json. Pressing Enter in a field does the same. If you close the screen without pressing it, your changes are discarded
• Revert: discards unsaved changes and puts the saved values back (the screen language stays as it is)

7. All buttons

Start, Stop and Reset are in "Integrated measurement" on the Live tab's right rail; Quit is in the row of tabs at the top of the screen (right of Help).

Each setting is explained in "6. All settings" of this manual. The Help button in the header opens this manual in a panel inside the app, and the "Open in a new window" link at the top of that panel opens it as an ordinary page in a separate tab.

8. Venue presets

Use the Presets tab in the header (or Open presets on the Live tab's right rail).

A preset is a snapshot of everything in the Settings tab (device, groups, target, bars, target IP …), except light mode, which is a per-PC setting.

1. Get the settings right in the Settings tab and press Apply and save
2. In the Presets tab, type the venue name into "Preset name" (for example XYZ Arena show) and press Save preset
3. Next time, pick it from the list and press Load. Loading takes effect and is saved at once. If a device with the same name is found, measurement starts right away
4. To remove a preset you no longer need, pick it from the list and press Delete

The name of the preset you last loaded (or saved) is shown in "Venue presets" on the Live tab's right rail (Figure 8), so you can see which venue's settings are in use (the name is remembered by this browser; a deleted preset is removed from the display).

9. Preparing XPression

You only need to do this once per XPression machine.

9.1 Add a source in DataLinq Server

1. Start XPression DataLinq Server (Start menu → XPression → XPression DataLinq Server)
2. Add New → choose XML/JSON TCP DataLinq Source → OK
3. Configure the next screen as follows

Press OK to add the source. Give it an obvious name such as "OtoMotion".

9.2 Connect XPression to DataLinq Server

1. In XPression, open Project → DataLinq Manager and click Add
2. Enter localhost as Host Address (when DataLinq Server is on the same PC as XPression) and 8888 as Port (DataLinq Server's default), then OK
3. If the source you created in 9.1 appears under Available DataLinq Sources, you're done

9.3 Check that values are arriving

Once OtoMotion is running and shows "XPression: connected", open a text object's Data Source → DataLinq → Browse in XPression to see the tree of folders g1–g8 and beat under root. Open g1 and pick name to see "メイン" (or "Main" in English mode); open g2 and pick m to see "-∞", and so on.

10. Building the scene

OtoMotion does all the calculation before sending, so on the XPression side you only need to "display the value" and "use it as a bar length".

10.1 Show a value in a text object

1. Place a text object, choose DataLinq on the Data Source tab of the Object Inspector, and click Set
2. In Set DataLinq Properties, turn Enabled on, choose the OtoMotion source under DataLinq, and click Browse...
3. In Select DataLinq Field, expand the g1 folder, pick m, and click OK. Column becomes g1 (the folder) and Row becomes m (the key). You can also type them in (for a beat value, Column beat and Row bpm, and so on). For the common keys directly under root (elapsed, status, and so on), leave Column empty and put the key name in Row
4. Always turn Live Update on (the value does not update without it)

Frequently used keys: g1 › m (Momentary), g1 › s (Short-term), g1 › i (Integrated), g1 › lra, g1 › tp (True Peak), g1 › tpmax, g1 › diff_i (difference from target, in the form +0.6), elapsed (measurement time; a common key, so it sits directly under root). They arrive as strings with one decimal place, so they can be displayed as they are.

10.2 Drive a bar (script)

Bar length arrives as g1 › mbar (0–1). Receive it in a text object (it can be hidden) and use a script to put it into a quad's scaleX. Write the script in the OnSetText event of that text object's Script Editor (it runs every time a value arrives).

' Script on the text object that receives g1 › mbar
dim bar as xpBaseObject
dim v as Double
Scene.GetObjectByName("Bar1", bar)
v = text / 1                 ' convert the string to a number
bar.scaleX = v               ' use 0–1 directly as the horizontal scale
bar.Visible = (v > 0)        ' hide at 0 (so no thin sliver remains)

• Set the quad's origin (Pivot) to its left edge and make its width the length of a full bar. Then scaleX = 1 is full and 0.5 is half
• For the peak bar use g1 › pkbar, or g1 › pk_l / g1 › pk_r for separate L / R. The peak hold position is g1 › pkhold (0–1 on the same range, so set a thin quad's positionX to "maximum bar width × value")
• For a target line, place it at a fixed position: the target −24 divided by the bar range (default −60 to 0) = 0.6. If you change the bar range, move it accordingly

10.3 Showing and hiding groups

gN › on is 1 if the group is enabled and 0 if unused. Use it to toggle Visible on group 2's group (its full set of text and bars), and the same scene works whether the venue has one group or two.

' Script on the text object that receives g2 › on
dim grp as xpBaseObject
Scene.GetObjectByName("Group2", grp)
grp.Visible = (text / 1 > 0)

10.4 TP Over warning

While g1 › tpover is 1 (for 3 seconds after the overshoot), show a red indicator. As above, just feed it into Visible.

10.5 Building per-band bars

Use the same input in several groups and give each group a different band to get bars that move separately for "overall", "bass" and "highs".

1. Set Number of groups to 3
2. Give all three groups the same L ch / R ch (for example 1 / 2)
3. Set names and bands: Group 1 = "Overall", Full range; Group 2 = "Bass", Low; Group 3 = "Highs", High. Then press Apply and save
4. In XPression, feed g1 › mbar, g2 › mbar and g3 › mbar into their own bars (same script as in 10.2). The bass bar jumps with the kick and bass; the highs bar with cymbals and crowd noise

• Filtering lowers the level itself, so the low and high bars tend to be shorter than the full-range bar. Narrow Loudness min / max (the bar range) or raise that group's Trim dB to balance the look (the trim also affects the numbers)
• For snappier movement lower Smoothing ms (e.g. 30); for a longer tail raise Fall time ms (e.g. 500). Bar settings are shared by all groups
• Always judge broadcast loudness (−24) with the full-range group (Group 1 in this example). Groups whose gN › band is not full are for visual effects only

Checking with the test signal's kick: even without sound from the desk, you can check how the per-band bars move with the 6.2 Test signal. After setting up the three groups above, set the test signal Type to Kick (for BPM detection), the Level to −12 dBFS, and turn on "Use test signal" (the test signal feeds the same sound to every group, so L ch / R ch don't matter). If the "Overall" and "Bass" bars jump with each kick while the "Highs" bar hardly moves, the bands are split correctly. Then switch the Type to Sweep: as the tone rises from low to high, the "Bass" bar and then the "Highs" bar extends. You can watch the XPression scene with the same signal. Always turn it off again when you are done.

10.6 Other useful keys

10.7 Sample scene (a complete kit)

A sample that combines a loudness meter, band-limited bars and beat dots. The background, guide, textures and scripts are bundled, so you can build the same scene in XPression.

The quickest way: open the project

1. Save OtoMotion_sample_scene.xpp (an XPression package) on the XPression PC
2. Double-click the saved .xpp. XPression (12.5 or later) starts and walks you through unpacking the package; follow its prompts. The background image is inside the package; the text uses Arial, which comes with Windows
3. In Project → DataLinq Manager, check that the server (default localhost, port 8888) and the DataLinq DataLinq1 point to the OtoMotion source you created in 9.1. If DataLinq Server runs on another PC, change the Host Address
4. Set OtoMotion to 4 groups with bands Low / Mid / High (see "5. OtoMotion settings" below) and press Start on the monitor

To build it yourself or to see how it works, follow the steps and scripts below.

Bundled files (open them from here)

• OtoMotion_sample_scene.xpp — the XPression 12.5 package (open it as above)
• otomotion_scene_bg.png — background (1920×1080) with frames, bar tracks, the scale and the target line (−24)
• otomotion_scene_guide.png — the same image with each frame's name and center coordinates (a placement guide)
• otomotion_scene_preview.png — what the finished scene looks like
• textures/ — bar gradients (bar_M / bar_S / bar_PK / bar_BAND / tpover) and a glowing dot (dot_on, transparent)
• otomotion_scene_scripts.txt — every binding and script below, for copying

The idea: display text and "drivers"

Values appear in a text object just by binding it. Bars and dots (quads) cannot receive DataLinq, so place a hidden text object (a driver) that receives the value and moves the quad from its OnSetText script (the same mechanism as 10.2). Hide drivers with Alpha 0 (turning Visible off may stop updates).

1. Display text (bind only)

2. Drivers and the quads they move

Make horizontal bars as wide as their track and vertical bars as tall as theirs, so a value of 1 fills the track and 0.5 fills half.

3. Scripts (OnSetText of each driver)

Horizontal bar (g1_mbar; for the others change "M" to "S", "PK_L" or "PK_R"):

dim bar as xpBaseObject
dim v as Double
Scene.GetObjectByName("M", bar)
v = text / 1
bar.scaleX = v
bar.Visible = (v > 0)

Vertical bar (g2_mbar): the same, with "M" changed to "LOW" ("MID" for g3, "HIGH" for g4) and scaleX changed to scaleY.

TP OVER (g1_tpover):

dim box as xpBaseObject
Scene.GetObjectByName("TP OVER", box)
box.Visible = (text = "1")

Beat dots (beat_count). Only the current beat's dot is shown; the dark rings drawn in the background show for the others:

dim d1 as xpBaseObject
dim d2 as xpBaseObject
dim d3 as xpBaseObject
dim d4 as xpBaseObject
Scene.GetObjectByName("dot_1", d1)
Scene.GetObjectByName("dot_2", d2)
Scene.GetObjectByName("dot_3", d3)
Scene.GetObjectByName("dot_4", d4)
d1.Visible = (text = "1")
d2.Visible = (text = "2")
d3.Visible = (text = "3")
d4.Visible = (text = "4")

4. Colors (to match the OtoMotion screen)

M #F24028, S #FF8A70, PK #FFD23F, LOW / MID / HIGH #B04DFF, TP OVER #D9202A, beat dots #F24028. For gradients, use the bundled textures as material textures (they shrink with the bar, matching the preview).

5. OtoMotion settings

Set the number of groups to 4, give groups 2–4 the same input channels (L ch / R ch) as group 1, and set their bands to Low, Mid and High (6.1). With one mono mic, set every group to L1 / R1 so PK L and PK R move together. Integrated, LRA, TP MAX and the difference from target appear after you press Start on the monitor.

If something does not move

• Check the Row spelling: Row is OtoMotion's key name, not the object name (e.g. mbar). One wrong letter means no value arrives and the script never runs. When a quad stays in its original shape, suspect this first
• Temporarily set the driver's Alpha to 100 and see whether the number changes. If not, the binding (Column / Row, Live Update) is wrong; if it does, the script is
• Write the script in OnSetText and confirm "Compiled successfully." in Messages
• The name in GetObjectByName must match the quad's name exactly (case and spaces)
• A bar grows from the center or shrinks the wrong way → the quad's pivot is not at the left edge (bottom edge for vertical bars)
• If you changed the gain after starting a measurement, press Reset → Start to measure again (earlier values stay in Integrated and TP MAX)

10.8 CROWD POWER (crowd meter for venues)

The sample package OtoMotion_sample_scene.xpp (XPression 12.5) now includes, alongside the existing loudness sample scene, four "CROWD POWER" scenes for a venue's big screen.

• A: vertical gauge — 24 segments stack up from the bottom, with the tier word switching through GOOD 40 / GREAT 60 / AMAZING 80 / MAX!! 95. A dotted line marks BEST
• B: dial — a needle points at one of 30 ticks. The tier word appears under the dial
• Side-by-side — A on the left, B on the right, in one scene
• C: LED equalizer wall — 24 bars (8 LOW in blue, 8 MID in purple, 8 HIGH in red) with a big number in the centre

How the crowd-power value works

Crowd power is group 1's bar value (g1 › mbar) × 100. It rises with a bigger cheer.

• BEST: keeps the highest value seen so far; it stays on screen even after the crowd quiets down
• NEW RECORD!: shown for 3 seconds when the crowd drops at least 20 below the current record and then beats a record of 60 or more (so it only fires when a fresh cheer clearly tops the previous one, after a lull)
• The screen flashes at 95 and above
• Pressing Reset in OtoMotion sets BEST back to 0

OtoMotion settings: Bar motion

On the Settings tab → Bar motion (6.4), set these values for a venue crowd:

Tuning: aim for about 20–30 when the crowd is quiet, and about 85–95 for the biggest cheer. If it sticks at 100, raise the max (e.g. −3 → 0). If it never gets high, lower the max. Leave group 1's Trim dB at 0 unless it's clearly off.

Scene C needs 4 groups

Scene C moves band-colour-coded bars, so it uses 4 groups (Settings tab → Device and groups).

Crowd noise has little high-frequency energy, so the HIGH bars often read lower than the others. If one colour is clearly shorter than the rest, raise that group's Trim dB (try around +6 dB for HIGH).

DataLinq bindings

In all four scenes, the driver text objects are bound to the DataLinq source named "OtoMotion" that you set up in section 9 (an XML/JSON TCP source, TCP Server, port 7327). Name your DataLinq Server source OtoMotion, or, if it's named differently, re-select your source in each driver's DataLinq properties. The main drivers are drv_level (g1 › mbar) and drv_elapsed (elapsed); scene C also has drv_low (g2 › mbar), drv_mid (g3 › mbar) and drv_high (g4 › mbar).

Font

The numbers use the free font Teko (Bold and SemiBold, SIL Open Font License 1.1). Install Teko-Bold.ttf and Teko-SemiBold.ttf on the XPression PC before opening the scenes (licence: OFL_Teko.txt). The background images already contain the title and labels, so no other font is needed.

Hidden text objects and scripts

The hidden text objects var_best, var_rec, var_frame, var_armed and var_elapsed hold the record and timers. Don't delete them, and keep them empty (nothing needs to be typed into them). The scripts are also provided as text files: crowd_power_scripts.txt (for A / B / side-by-side) and crowd_power_c_scripts.txt (for C, including the three band scripts). The XPression scripts are VB.NET and find objects by name (seg_01…, tick_01…, bar_01…, needle, best_marker_b, tierA_*, tierB_*, flash, new_record, num_a / num_b / num_c, best_a / best_b / best_c_num, and so on).

11. JSON key reference (181 keys)

OtoMotion always sends the same 181 keys (for all 8 groups regardless of the number of groups, and all 16 MIDI slots even when nothing is assigned). So XPression bindings don't break when you change venue. Types are fixed: "display values are strings; bars and flags are numbers". The JSON is always nested (a tree): under root there is a folder per group, one for the beat and one for the MIDI slots, as shown below.

root
├ seq, time, status, running, elapsed, target          (common keys; names unchanged)
├ g1 … g8   each: on, name, m, s, i, lra, tp, tpmax, diff_i, diff_s, mbar, sbar, pkbar, pkhold, pk_l, pk_r, tpover, band
├ beat      : bpm, beats_per_bar, beat, beat_phase, beat_tri, beat_sine, beat_hit, beat_square, beat_count, downbeat, bar_phase, half_phase, double_phase, bpm_detected, bpm_confidence
└ midi      : s1 … s16   (raw values from a MIDI controller; added 2026-09-30; chapter 18)

Common (6, directly under root)

To bind one in XPression, leave Column empty and put the key name in Row (for example, Row elapsed).

Per group (g1–g8 folders, 18 keys × 8; N is 1–8)

Beat (beat folder, 15 keys)

All numbers. Beat values are calculated from the PC clock each time a message is sent, so they keep running without sound. In the final message on quit, beat › bpm and beat › beats_per_bar are the set values and the rest are 0.

MIDI slots (midi folder, 16 keys)

Values of MIDI controller knobs and buttons, sent to XPression as they are, independent of the measurement (chapter 18). Unassigned slots, the final frame at shutdown, and PCs where the MIDI library cannot be loaded send 0.

12. Show-day workflow

Preparation (day before to show day)

1. Confirm that DataLinq Server has been set up (section 9)
2. Start OtoMotion → load the venue preset in the Presets tab (for a new venue, set it up as in section 5 and save)
3. With the desk's test tone, press Set as reference → confirm M / S sit at −24.0 (the target)
4. Confirm the header shows "Input: (device name)", "XPression: connected" and "Send: actual 60"
5. Put the XPression scene into preview and confirm the bars and values move. Also confirm they show −∞ with silence
6. Confirm there is no yellow banner (test signal) below the header and no yellow dot (unsaved changes) on the "Settings" tab, and leave the Live tab showing

On air

1. At the top of the programme, press Reset → Start (if "Start measuring at launch" is on, just Reset)
2. Run the show while watching Integrated and its difference from the target (the small figure to the right of Integrated). If TP Over appears often, check the desk limiter
3. To exclude commercials or breaks, press Stop, then Start to resume

Strike

1. Take the meter scene out of XPression
2. Press Quit in OtoMotion (it sends one final message with bars at 0 before exiting)

13. Sending to another PC

1. Find the XPression PC's IP address (ipconfig in Command Prompt)
2. On the XPression PC, allow inbound TCP 7327 in Windows Firewall (in the prompt that appears the first time DataLinq Server starts, tick both "Private networks" and "Public networks" and allow; venue networks are often treated as public by Windows, and allowing private only is not enough)
3. In OtoMotion's Settings tab → "Send to XPression", enter that IP in "Target IP" and press Apply and save
4. When the header shows "XPression: connected", you're done. If it doesn't, check ping, then the port, then the firewall

14. Troubleshooting

15. Measurement specifications

16. BPM (moving to the beat)

To make visuals on the venue screen move with the beat of the music, OtoMotion also sends the BPM (tempo) and the beat position to XPression. The beat position is calculated from the PC clock, so it keeps running at a steady tempo even with no sound and even when the device isn't open. There are three ways to set the BPM.

• Type it in: enter a number and press Set (for songs whose BPM you know from the set list)
• TAP: press TAP in time with the beat (or the T key)
• Automatic detection: press Adopt to use the value estimated from the audio, or turn on "Auto follow" to adopt it automatically

16.1 Reading the BPM card

It is on the Live tab's right rail, just below "Integrated measurement". The dropdown to the right of the large number is the time signature.

16.2 Buttons and keys

16.3 Settings

These items take effect and are saved as soon as you change them (no need to press Apply and save, and they do not mark the settings as unsaved). Time signature and Auto follow are on the Live tab's BPM card; Detect from group, beat length and beat_hit decay are on the "BPM" page of the Settings tab (6.5). Auto follow can be switched on and off live during a show.

Only time signature, detection group, beat length and beat_hit decay are stored in venue presets. The BPM and auto follow are not (loading a preset keeps the current tempo and auto-follow state).

16.4 How detection works, and its limits

From the chosen group's audio, OtoMotion picks out the moments where the sound suddenly gets louder, weighting the low end (20–150 Hz: kick and bass) most, and estimates the BPM from how those moments repeat over the last 6 seconds. The estimate is updated every 0.5 seconds.

• It takes 4–8 seconds to lock: right after launch, after changing the group, or after the device is reopened, it shows "Detected —" until 6 seconds of audio have been collected. After a song changes, it also takes a few seconds to settle on the new tempo
• It goes wrong during talk, crowd noise, or songs with a weak beat: auto follow does nothing while the confidence is below 0.5, so during MC it keeps running at the previous tempo
• It can mistake half or double the tempo: for example, a 70 BPM song with strong off-beat hi-hats can come out as 140. Because values near the previous estimate are preferred, it rarely jumps to double mid-song, but if it starts at double, fix it with ÷2 / ×2 or use TAP
• It does not detect the time signature (which beat is the top of the bar). To line up the top of the bar, press Sync on beat 1
• MIDI / OSC clock and sync with external devices are not supported

Checking with the test signal's kick: even without a music source, you can see detection work with the 6.2 Test signal. Set the Type to Kick (for BPM detection), Kick BPM to, say, 128, the Level to −23 dBFS or higher (−12 dBFS is safest), and turn on "Use test signal". The test signal feeds the same sound to every group, so any detection group works. Within 6–8 seconds you'll see something like "Detected 127.7 · conf 0.8"; press Adopt or turn on Auto follow and check that the BPM matches (detection can be about 0.1 BPM off). If you change Kick BPM, the input is reopened and detection follows the new tempo a few seconds later. Slow tempos such as 60–90 BPM rarely reach a confidence of 0.5, so try 100–180. Always turn it off again when you are done.

16.5 Using it in XPression

All beat keys are numbers and are sent 60 times per second ("Beat (beat folder, 15 keys)" in chapter 11). Receive a key in a text object (it can be hidden) and drive other objects from its script, in the same way as 10.2.

Blink on every beat (beat › beat → Visible)

' Script of the text object receiving beat › beat
dim lamp as xpBaseObject
Scene.GetObjectByName("BeatLamp", lamp)
lamp.Visible = (text / 1 > 0)      ' shown only for the "beat length" after each beat

Spin with the beat (beat › beat_phase → rotation)

' Script of the text object receiving beat › beat_phase (0→1, repeating every beat)
dim star as xpBaseObject
Scene.GetObjectByName("Star", star)
star.rotationZ = (text / 1) * 360  ' one turn per beat (use beat › bar_phase for one turn per bar)

Pulse on the beat (beat › beat_hit → scale)

' Script of the text object receiving beat › beat_hit (1 on the beat, falling toward 0)
dim logo as xpBaseObject
dim v as Double
Scene.GetObjectByName("Logo", logo)
v = 1 + 0.2 * (text / 1)           ' 1.2× on the beat, back to normal size
logo.scaleX = v
logo.scaleY = v

Change colour on each beat (beat › beat_count → colour)

' Script of the text object receiving beat › beat_count (1 to beats per bar)
' Stack objects Color1–Color4 in different colours and show only the one for the current beat
dim obj as xpBaseObject
dim n as Integer
dim i as Integer
n = text / 1
for i = 1 to 4
  Scene.GetObjectByName("Color" & i, obj)
  obj.Visible = (i = n)
next

17. License

OtoMotion runs on a term license. Without a valid license file (license.json), the app still launches but only the license screen appears; it neither measures nor sends to XPression. Licensing does not tie the app to one PC and does not need an internet connection. A loaded license file is kept in the same folder as the settings (%APPDATA%\OtoMotion; on the Mac, ~/Library/Application Support/OtoMotion) and survives replacing the app.

17.1 Loading a license

1. Save the emailed attachment license.json (license.txt also works) to the Desktop or Downloads
2. Start OtoMotion. If there is no license, the license screen appears, listing any files found with their location, addressee and expiry
3. Press Load next to the one you want. Once loaded, the app moves on to the TOP screen
4. If the file is not found in the list, press Search again (after saving the file again), or use Choose a file to load to pick it directly

17.2 Expiry and renewal

Starting 30 days before expiry, a yellow "License: N days left" appears in the header (click it to open Settings › License). The license works through the end of its last day; starting the app on or after the next day shows the license screen. Once running, the app does not stop even if the license expires while it's open.

1. Save the renewal file (the emailed attachment license.json) to the Desktop
2. Open the Settings tab › License and press Load next to it (if the app started with an expired license, do the same thing on the license screen shown first)
3. Once "Remaining" shows the new value, you're done. No restart is needed

Settings › License shows the addressee, license ID, plan (term or perpetual), period and days left. Quote the license ID when contacting support.

17.3 Restoring the previous license

If you load the wrong file by mistake, Restore the previous license in Settings › License goes back one generation (only the file loaded just before the current one is kept). You can't restore to one older than the license currently in use.

17.4 Troubleshooting

18. Operate with MIDI · OSC (MIDI controller)

With a USB MIDI controller (knobs, faders, buttons) you can move OtoMotion's parameters, press its buttons and drive XPression graphics directly during the show. No specific model is required: as in Resolume, anything can be assigned with MIDI Learn. Assignments are saved in midi.json (in the same folder as the settings) and are not part of venue presets. OSC apps (TouchOSC, Companion, Vertex and others) use the same mechanism (chapter 19).

18.1 Assigning

Open Settings tab › MIDI · OSC to see the list of parameters you can assign (18.2). To assign one from its row:

1. Press Assign on the row you want. It turns yellow, the button reads "Move a control", and a blue banner appears at the top of the screen
2. Move a knob or press a button on the controller. The assignment is made and saved at once; the row shows a green "Assigned", a label such as CC 21 · ch1 and the device name
3. Done: that knob or button now moves the parameter. Below the label, Remove removes assignments one at a time

Buttons on the Live screen (Start, Stop, TAP, …) and the settings fields can also be assigned: press MIDI in the header, then click the item (assignable items light up blue; clicking one does not perform its normal action — pressing the button, editing the field). Tabs and the settings list on the left still switch normally. Pressing Esc cancels only the current wait if one is running, or leaves the mode if nothing is waiting. One knob may be assigned to several parameters (one fader for the trim of groups 1 and 2, for example).

Once a wait starts, a blue "MIDI assignment" banner appears at the top (it stays visible on any tab). Its current step is one of these three:

③ normally shows the control and the parameter name, as in the example above. It stays on the plain heading "③ Assigned" only when that information is missing. The right side of the banner shows Esc to cancel. Only when the wait was started from the header's MIDI mode (assigning a Live screen button or a settings field) does it read Esc to cancel / Esc again to leave, and a second Esc leaves the mode entirely.

Once a row has an assignment, its Assign button disappears. To switch it to a different knob or button, press Remove first, then assign again. Clicking a row opens an editor below it (a knob's Min / Max and Invert, and the Mode of a switch target — 18.5), but only for rows that already have an assignment. Switching the list's "Assigned only" filter on the top left shows just the rows that have an assignment (it is remembered even after reopening the page).

18.2 Parameters you can assign

The list is ordered: Level → Bars → Target & TP → BPM & beat → Measurement & presets → Test signal → Values sent to XPression. There is one group row per group in use, and one preset row per saved preset.

Parameter names never include a unit. The small text under a name shows "Button" for a button, "Switch" for a switch, the slot's behaviour (0–1, 0 / 1, and so on) for a value sent to XPression, or the range and unit for a knob. For a knob, that range is the mapping's own Min–Max when exactly one mapping exists, otherwise the default range (for example, trim defaults to −20 to +20 dB). In the value column, a + appears on dB-type values (trim, bar/peak maximum, TP limit) when they are positive (e.g. +3.1 dB). Target loudness and the test signal level can only ever be zero or negative, so they never show a plus sign.

Rows that cannot be used (a group not in use, a preset that no longer exists, frequency or kick BPM with a type that does not use them) are greyed out with the reason, but the assignment is kept — you can still remove it with Remove. The input device, channels, number of groups, the XPression address, language and license cannot be controlled by MIDI (changing them interrupts the audio or the connection).

18.3 Last signal

The bar at the top of Settings › MIDI · OSC shows the last message received, e.g. "device knob CC 16 (ch1) value 92 → Bar maximum (loudness): −1.2 dB" (it fades after 3 seconds). When one knob or button is assigned to several parameters, the first one is followed by "(+1 more)" and so on for the rest. A message that is not assigned shows "not assigned to anything yet"; when the value was not applied, the reason is shown (locked, group not in use, preset missing, not used with the current type, used for the assignment). The row of the parameter that moved lights up yellow for 1.5 seconds.

Releasing a button (a note off, for example) does not overwrite this line (except s1–s16 assigned as Momentary) — the moment it was pressed stays shown. An s1–s16 slot assigned as Momentary is the exception: releasing it updates the line to show a value of 0.

18.4 Values set by MIDI (live only)

Trim, bar ranges and the like moved by MIDI are not saved. The fields on the Settings tab keep showing the saved values, and a badge such as MIDI −12.0 appears next to the field (choices such as the band or the test signal type show text, e.g. "MIDI Low"). The "Current value" column of the list is shown in yellow too. Click the badge, or use the row buttons, to choose:

MIDI values are also cleared when a venue preset is loaded and when OtoMotion restarts (back to the saved values). Apply and save does not clear them (fixing the target address during a show does not undo what you set with the knobs). If you edit and save a field that has a badge, the saved value changes but the MIDI value stays in effect (press Clear to use the field's value).

18.5 Switches, the test signal and the band

Band, time signature, auto follow, detection group, start at launch, and the test signal's on/off and type are "switches". An assignment has one of two modes (change it in the row editor).

• The test signal's type, level, frequency and kick BPM and a group's band change without a gap in the audio during the show (they take effect from the next block; the input is not reopened). The frequency knob is logarithmic (the middle is about 630 Hz)
• Frequency only applies when the type is sine, kick BPM only when it is kick. While the current type does not match, the row is greyed out and turning the knob does nothing (a value set earlier is kept and applies again once the type matches)
• The test signal's on/off switches the input (audio interface ⇔ test signal), so it is saved like the checkbox. The device audio stops the moment it is turned on. The switch can take a few seconds (especially on Mac). At the next launch it is always off, as before

18.6 Values sent to XPression (midi › s1–s16)

Sixteen values that send MIDI values to XPression as they are, independent of the measurement. A knob gives 0–1 (the range can be narrowed within 0–1 and inverted); a button gives 0 or 1 (1 while held in Momentary mode). They have no names (their use in XPression differs from project to project). In XPression, bind them through DataLinq with Column = midi and Row = s1–s16, like any other key (chapter 10). The current values are shown as bars at the end of the list on Settings › MIDI · OSC.

18.7 Connected devices

The bottom of Settings › MIDI · OSC lists the MIDI inputs found. A device seen for the first time is set to Listen. Untick devices you don't use; their messages are then ignored (and stay off next time). The dot lights up when a message arrives.

18.8 Notes

• A 7-bit CC gives BPM steps of about 1 over 60–180; assign a pitch bend wheel for finer control
• To receive MIDI from a DAW on the same PC you need a virtual MIDI cable (Windows: loopMIDI, Mac: the IAC driver). Following MIDI clock for BPM comes in the next version
• On Mac, USB and IAC MIDI need no permission dialog. Bluetooth MIDI is not supported
• On a PC where the MIDI library cannot be loaded, Settings › MIDI · OSC shows the reason. Everything else works, and midi › s1–s16 are sent as 0. OSC receiving and assigning still work, and the MIDI button can still be pressed (clicking an item then waits for OSC; 19.8)
• Without a license (locked), MIDI has no effect on anything. The MIDI button and Settings › MIDI · OSC are also hidden. Assignments are kept, and they work again once a valid license is loaded

19. OSC (send and receive)

OSC (Open Sound Control) is the UDP message format that video, lighting and control apps exchange over a LAN. OtoMotion can send (the same values it sends to XPression, to Resolume, TouchDesigner, lighting consoles, Ross Vertex and others) and receive (be controlled from TouchOSC, Bitfocus Companion, Vertex and others). Settings live in osc.json (same folder as the settings) and are not part of venue presets. It is a separate output from XPression; neither affects the other.

19.1 Sending: add a destination

1. In Settings › Send OSC, press + Add destination (up to 16)
2. Enter the IP (IPv4 digits only; host names are not accepted) and port (Resolume's default is 7000). Click the heading to rename it (empty shows IP:port)
3. Choose per second (1–60, default 30). 15–30 is recommended for an iPad (TouchOSC) on Wi-Fi
4. Tick Send to the left of the name to start sending. Every change is saved at once. A newly added destination has "Send everything" on by default, so if you only want "Added addresses" (for example sending to a lighting console), untick it

Each destination can use "Send everything" (fixed names, everything; 19.2) and "Added addresses" (any value to any address and range; 19.3). Broadcast (a special IP that reaches every device on one subnet at once, e.g. 192.168.1.255 reaches everything on 192.168.1.*) also works. On a PC with several interfaces (wired, Wi-Fi, virtual adapters) 255.255.255.255 only leaves one of them, so use the subnet broadcast. If two OtoMotion PCs send to the same device, give each a different address prefix (/otomotion_a, /otomotion_b).

19.2 Addresses and values of "Send everything"

Addresses follow the XPression tree (chapter 11): under the prefix (default /otomotion) come groups g1–g8, the beat beat, the MIDI slots midi, and the common keys (time, status, running, elapsed, target). seq is not sent (180 addresses). Values that go to XPression as text (M, S, I, LRA, TP) go over OSC as numbers.

Values are sent on change (a difference under about one-millionth counts as unchanged), and in addition every key is re-sent gradually over one second, so a receiver started later has everything within about a second. Unused groups send only /gN/on (0); when you reduce the number of groups, that group's values (bars 0, levels −120, empty text) are sent once. One value per message (OtoMotion does not use "bundles", OSC's way of grouping several messages into one packet). On exit, only destinations that have both Send and Send everything on, with a host set, receive once: /otomotion/status "offline", running 0, the 6 bars at 0, M, S and TP at −120, tpover 0, the 4 beat keys at 0 and the 16 slots at 0 (gN/on, BPM, I, LRA, TP max, name, band, target and added addresses are not sent; nothing at all is sent while locked).

The bottom of the page lists every address "Send everything" sends, each with a Copy button, for wiring up XPression or another app.

19.3 Added addresses: any value to any address

Add rows to the table in the destination card (up to 64). Choose the value (numeric keys only, shown with the source range, e.g. "Main › M bar (0–1)"), the address (anything starting with /), the range (min and max, e.g. 0–1, 0–100, 0–255; min > max reverses the direction; min and max cannot be equal — both fields turn red and nothing is saved), the type and when to send. Values outside the source range are clamped before mapping.

Examples: for the opacity of a Resolume layer, value "Main › M bar", address /composition/layers/1/video/opacity, range 0–1, Float, on change. For an Eos submaster, /eos/sub/1, range 0–1, Float (for UDP on Eos enable String RX/TX in Setup › Show › Show Control and UDP Strings & OSC in the ECU; ports 8000/8001 or 4703–4727 are recommended). For a grandMA3 fader, /gma3/Page1/Fader201, range 0–100, integer. For a Companion variable, point the destination at Companion's IP:12321 and use /custom-variable/bpm/value (use "Number as text" to show it on a button; Float also works, but OSC floats are 32-bit, so 0.3561 shows up as 0.3560999929904938). Vertex registers addresses in an OSC Receiver Device and reads decimal values (turn off "Send everything" for Vertex; see 19.9).

When: "On change" (default) sends only when the mapped value differs from the last one sent, with no one-second re-send (so OtoMotion does not fight a fader the operator moved on the console). A receiver started later therefore gets nothing until the value changes (e.g. g1/on, BPM). "Every time" sends at the destination's rate. "Trigger" is 19.4. Do not point a destination at your own receiver (this PC's IP:8831); the values would come back to you.

Entering a value of the wrong shape turns that field red and nothing is saved; a line below names the destination, row and column, e.g. "The request was malformed (Added address row 2 › Address)". A destination's own fields (IP, port and so on) turn red the same way.

19.4 Trigger (fire a clip on the beat)

Sends only at the moment the chosen value rises from below 0.5 to 0.5 or more (beat, downbeat, tpover and so on). The edge is checked 60 times a second regardless of the destination's rate, so a rate of 10 or less does not miss beats.

The Trigger shape column only exists when the type is Float or Integer, and there are two choices:

Fixed text and No value are not trigger shapes — they are type choices (19.3), and a row using either shows "—" in the Trigger shape column. Both behave the same way: at the rising edge, OtoMotion sends that one message (the fixed text, or a message with no argument) and nothing afterwards — no 0 follows — which suits a "press and release" receiver such as Eos's /eos/key/go_0.

19.5 Destination status

While locked, the screen shows only the license page: OSC does not send, and received messages are not applied (only the fixed /otomotion/clear/… addresses still work while locked; see 19.7). Settings and assignments are kept, and everything works again once a license is loaded (the same as 18.8).

On a Mac (macOS 15 and later), sending to the LAN needs the "Local Network" permission. Allow it in the dialog shown the first time; if denied, the status reads "Cannot send (nothing is listening there)　Allow OtoMotion in System Settings › Privacy & Security › Local Network".

19.6 Receiving: port and IP

In Settings › MIDI · OSC, tick Receive in the "Receive OSC" card. The default port is 8831 (it cannot be the monitor page's port; if the monitor page uses 8831, the first default becomes 8832). In the app, enter "This PC's IP" and the port (when several IPs are listed, pick the one on the same network as the device; a virtual adapter's IP may appear).

• On Windows, the first time you turn it on a firewall dialog appears. Tick both "Private networks" and "Public networks" and choose Allow. Venue networks are often treated as public by Windows; if only private is allowed, nothing arrives from an iPad or another PC (Companion on the same PC still gets through, so this is easy to miss). If you cancel, packets are silently dropped from then on. If nothing arrives, check the current network type (private or public) in Settings › Network & internet, and tick both boxes for OtoMotion in Windows Security › Firewall & network protection › Allow an app through firewall
• Accept only from (comma-separated IPv4) drops everything from other senders. Recommended during a show (OSC has no authentication). Add 127.0.0.1 for Companion on the same PC
• Do not point Resolume's or TouchDesigner's OSC output at this port (thousands of messages per second delay MIDI too; anything beyond 2048 queued messages is dropped and counted)
• "Last sender" shows the IP and seconds ago; use it to check whether anything arrives
• When any of them is non-zero, a count appears next to the status, e.g. "filtered 2 · dropped at limit 0 · malformed 1". Filtered is how many were rejected by "Accept only from", dropped at limit is how many were discarded past the 2048-message queue, and malformed is how many packets could not be read as an OSC message at all

While locked, the screen shows only the license page: OSC does not send, and received messages are not applied (only the fixed /otomotion/clear/… addresses still work while locked; see 19.7). Settings and assignments are kept, and everything works again once a license is loaded (the same as 18.8).

Only the first argument is used. Numbers, text and button presses from ordinary apps are read as expected (uncommon types are ignored). A "bundle" (several OSC messages sent together as one packet) is unpacked, and each message inside it is handled on its own. Addresses must match exactly, including case (patterns such as /otomotion/bpm/* are not expanded).

19.7 Fixed addresses (work without assigning)

While receiving is on, every row in Settings › MIDI · OSC shows its address (Copy copies it). Enter that address in the app and it works without assigning.

Buttons count one press for no argument or a number of 0.5 or more (the 0 a TouchOSC button sends on release does nothing). 1 / 0 means on for 0.5 or more, off below (not a toggle). Numbers outside the range do nothing and "Last signal" shows the reason, e.g. "Out of range (30–300)". Sending text instead of a number, or a value that cannot be read as a number at all (such as a malformed decimal value), also shows "wrong argument type". Integer addresses accept decimal values such as 4.0. Text must match exactly (Low is not accepted). The effect is the same as moving the parameter by a MIDI assignment, including "Last signal" and the highlighted row.

19.8 Assigning (the same [Assign] as MIDI)

To use an app control of your own choosing (TouchOSC's /1/fader1 and so on) instead of a fixed address, assign it as in 18.1: press Assign on the row, move the control in the app, and the first address that arrives is assigned; the row gets a purple badge "OSC /1/fader1".

• The edit panel (click the row) gains an Input range (default 0–1; set it to 0–100 for senders like Vertex; the default stays 0–1 even if the Learn value was outside it; min and max cannot be equal — both fields turn red and nothing is saved) and a Source (any source / only this IP)
• Numbers are continuous (faders), no argument means "pressed", and numbers crossing 0.5 act as buttons. Text is used as a choice name only on band, test-signal type and time-signature rows
• A sender that streams continuously (TouchDesigner's OSC Out, Resolume feedback) will be the first address to arrive while waiting. Stop it or restrict "Accept only from"
• /otomotion/… addresses are never assigned (they act as fixed addresses and the wait continues)

19.9 Examples

These combinations were checked with OtoMotion and the other app running on the same Windows 11 PC (October 2026; the app version is in brackets in each heading). If the apps run on different PCs, replace 127.0.0.1 with the IP of the other app's PC (when OtoMotion sends) or of the OtoMotion PC (when the other app sends).

Resolume (Arena 7.28): drive a layer's opacity with the level

1. Resolume: in Arena › Preferences › OSC, turn on OSC Input and set Incoming Port to 7000
2. OtoMotion: in Settings › Send OSC, add destination 127.0.0.1, port 7000, and tick Send
3. Add one row under Added addresses: value "(group name) › M bar", address /composition/layers/1/video/opacity, range 0–1, type Float, send On change

Layer 1's Opacity follows the sound. To find a Resolume address, choose Shortcuts › Edit OSC and click the parameter; the address appears in the Shortcuts panel at the bottom right. Resolume's own Learn (remember the incoming address) is unreliable while "Send everything" streams 180 addresses, so sending straight to Resolume's address from OtoMotion, as above, is the recommended way. Preferences › OSC › Monitor shows the addresses and values that arrive.

Resolume: trigger a clip on the beat

Add one more row to the same destination: value "Beat › Beat", address /composition/layers/2/clips/1/connect, range 0–1, type Integer, send Trigger, trigger shape "1 then 0". The first clip of Layer 2 restarts on every beat (19.4). Check first that the BPM matches the music (chapter 16).

TouchDesigner: receive the values as channels

1. OtoMotion: add destination 127.0.0.1, port 7000, and tick Send everything and Send. If you also need the text values, add a second destination on port 7001
2. TouchDesigner: add an OSC In CHOP with Network Port 7000
3. For the text values, add an OSC In DAT with Network Port 7001

The OSC In CHOP lists the numeric values (otomotion/g1/mbar, otomotion/beat/beat_phase and so on) as channels; pick what you need with a Select CHOP (Strip Name Prefix removes /otomotion). The text values (time, status, elapsed, group names, bands) are silently dropped by the OSC In CHOP (they do not become 0 or an error), so read them with the OSC In DAT. One port can be received by only one operator, so give the CHOP and the DAT different ports.

Bitfocus Companion (v5.0.7): show the BPM on a button

1. Companion: in Settings › Protocols, turn on OSC Listener (port 12321). In Variables › Custom Variables, create a variable bpm
2. OtoMotion: add destination 127.0.0.1, port 12321, untick Send everything and tick Send
3. Add one row under Added addresses: value "Beat › BPM", address /custom-variable/bpm/value, range 30–300, type Number as text, send On change

The BPM goes into the Companion variable $(custom:bpm), which you can use in button text. If the range stays at the default 0–1, the BPM range 30–300 is scaled to 0–1 (to send the BPM as it is, set the range to the original 30–300). Float also works, but OSC floats are 32-bit and show extra digits.

Bitfocus Companion (v5.0.7): control OtoMotion from buttons

1. OtoMotion: in Settings › MIDI · OSC › Receive OSC, tick Receive (port 8831). If you use "Accept only from", include 127.0.0.1
2. Companion: in Connections, add Generic: OSC with Target Hostname or IP 127.0.0.1, Target Port 8831, Protocol UDP
3. Add actions like these to a button's Press actions

To check what arrived, look at "Last signal" at the top of Settings › MIDI · OSC (for example OSC 127.0.0.1 /otomotion/bpm/bpb 3 → Time signature: 3/4) and "Last sender" under Receive OSC. All addresses are listed in 19.7.

Ross Vertex (Trial 2026.02.23): drive a clip's opacity with the level

1. Vertex: check that System1 under Project Explorer › Systems is connected (while it shows Disconnected, OSC devices neither receive nor send; connect it before use)
2. Vertex: in Library › Devices, search for "OSC" and add an OSC Receiver Device. In the Inspector set IP Port to 8000 and enter /vertex/opacity as the Address of Values › Osc Address 1
3. OtoMotion: add a destination with the Vertex PC's IP and port 8000, untick Send everything and tick Send
4. OtoMotion: add one row under Added addresses: value "(group name) › M bar", address /vertex/opacity, range 0–1, type Float, send On change. When values arrive, they show in Received Value of Osc Address 1 in Vertex
5. Vertex: right-click the clip on the timeline › Pin to new Inspector › Clip to open an Inspector for that clip (it may open at the edge of the screen)
6. Drag Opacity from that clip Inspector onto the Source field (the checkered field) of Osc Address 1 of the device

The clip's opacity now follows the sound. Note:

• Turn off "Send everything" for Vertex. Streaming everything (180 addresses, over 1,000 messages per second) to Vertex makes its receiver stop within a few seconds (Reset Connection brings it back, but it stops again). Send only the values you use, as added addresses
• One OSC Receiver Device holds 16 addresses (Osc Address 1–16). Add more devices for more
• What goes into Source is the property you want to drive (such as the clip's Opacity). Dropping the image file from Content only offers file information. While the blue pin (lock) of the Inspector is on, selecting the clip does not switch the Inspector to it
• The M bar (0.4 s) suits visuals; the S bar is a 3-second average and looks slow. If the movement is small, widen the range of the added address in OtoMotion, for example 0–2 (Vertex's Opacity tops out at 1). Small flicker settles with the clip's Opacity Damping at about 0.1–0.2
• Quiet sound keeps the bars at 0: below the range in Settings › Bars (default −35 to −3 LUFS) the bar is 0. Feed a proper level from the venue desk

Ross Vertex (Trial 2026.02.23): switch OtoMotion from Vertex

1. OtoMotion: in Settings › MIDI · OSC, tick Receive (port 8831)
2. Vertex: in Library › Devices, add an OSC Sender Device. In the Inspector enter the OtoMotion PC's IP as IP Address and 8831 as IP Port. Turn Use Message Prefix off (when on, text is added before the address and OtoMotion rejects it)
3. In Project Explorer, right-click the Sender › Add Float Property, then enter /otomotion/set/g1/band as Address and 2 as Value

Group 1's band in OtoMotion switches to Low (1 = full range, 2 = low, 3 = mid, 4 = high). Vertex cannot send text, so use the numeric addresses for band, test signal type and presets (19.7). Put the value on the timeline or in a cue, and OtoMotion's measurement changes together with Vertex's show cues.

Other apps: setup guide

• TouchOSC: Connections › OSC, Host = this PC's IP, Send Port = 8831. To get values back, set a Receive Port and add "iPad IP:that port" as a destination in OtoMotion. Faders default to a decimal range of 0–1; buttons send 1 on press and 0 on release
• Lighting consoles: see the examples in 19.3 (an Eos submaster, a grandMA3 fader) and triggers in 19.4

19.10 What to expect during a show, and notes

• When measuring stops, running is 0 while M, S, bars and the beat keep flowing and I and LRA stop (as with XPression). Test-signal values are sent as they are
• XPression and OSC are independent. If XPression disconnects, OSC keeps going (and vice versa)
• osc.json is not part of venue presets. Values set through set/ are live overrides and are cleared when a preset is loaded (as with MIDI)
• Around a save or at shutdown, a rare "Could not save" or "Shutting down" message can appear; wait a moment and try again
• IPv6, host names, TCP, sending bundles and OSCQuery are not supported

OtoMotion — dekobokotech.com