Resolume Timecode Monitor
View the time left for a playing clip on multiple devices.
 |
 |
This screenshot is from firefox on linux, but you can even view this on your phone. |
This is the server end of things, doesn't need to be run on the same device as Resolume |
How to use
- Download the latest release
- Open the app and verify that all the information in there is set correctly.
- Click Start Server
- Open your web browser to the location specified by the application.
- Start playing a clip in Resolume.
- Profit.
Note: The precision should be within a few hundred milliseconds (usually 50ms), if it feels off double check that the clip length
(under Advanced Settings
on the client) is correct. If it isn't, just refresh the page.
How to set the Path
field
Clip to use |
Example path |
Selected Clip |
/composition/selectedclip |
Specific Clip |
/composition/layers/1/clips/1 |
Selected Layer |
/composition/selectedlayer |
Specific Layer |
/composition/layers/1 |
Note: using a layer will cause the layer's name to be shown on the client instead of the clip name
(I'm not sure if there is a way to fix that).
Motivation
When using Resolume for events where longer clips were being played, I found it annoying that the only way to find out
the remaining time was to ask the guy in front of the laptop. So I decided to fix that.
How it works
Resolume outputs the position of the clip head through OSC, by calculating how much time it took between the one message
and the previous one, it's possible to calculate how long the clip is, and therefore how much time is left.
Due to certain inconsistencies in the way this information is outputted, it's not as simple as it sounds.
For the exact algorithm, check main.js
(specifically, procPos()
).
Anyways, because we're running in a browser, we can't actually interact with OSC (as it works over the network),
so this application also acts a proxy, translating the UDP packets to websocket.
There is also a bit of processing done here to reduce the load on the device (it's around 300 messages a second, so the less the better).
Known Issues
- Uses around 60-70mb of RAM. Sorry, can't do much about that, at least it's better than an electron app.
- Restarting Resolume while the server is running will cause it to crash. Will fix eventually.
Building
Because this is based on fyne it requires the use of cgo, so make sure you have a C compiler installed on your system.
Just clone the repo and run go build github.com/chabad360/resolume-timecode
.