Ontime meets open stage control - WIP

[Greenman]

installation de ontime.io

https://www.getontime.no/

Settings

OSC Settings in ontime

ontime listen on Port 8888 > So Osc will send on this port OSC messages.
Osc target Port : 9999 > Osc will receive on this port OSC messages

Osc server configuration

The "target" in ontime settings is Open Stage Control input : 127.0.0.1:9999 (Osc is on the same host 127.0.0.1 as ontime)

osc-port : 9999
send : 127.0.0.1:8888

Launch the Osc server

another launch, another port number

Question : I don't know why the *\ontime\update* is sent FROM (not to) a randomized port.

let's make a button Start Next

We find some infos :

OSC and WebSocket APIs

Important : every osc message sent to ontime must start with /ontime/ and then the "command"
i.e. /ontime/start-next to start-next

It works

A suivre

ps : session json file
ontimeMeetsOsc-01.json (6.4 KB)

[jean-emmanuel]

Question : I don't know why the \ontime\update is sent to a randomized port.

It's not sent to a randomized port, it is sent from a random port. In my opinion it's a bad yet harmless practice. It's usually very easy for a software to instead send from its receiving port, with the benefit of indicating where other softwares should reply.

[Open-Stage-Composer]

Thanks for sharing the project, time and effort!
Having all the information from the other long post here, is a great resource.

Thank you!

[Greenman]

Happy this can help ! Feel free to share your session json files and your tips.

In example i can not find why the start button does not work. Bref wip