I think this request is the opposite of the forthcoming DMX feature for control of lighting fixtures by Liberation.
I would like to be able to control Liberation from a lighting desk, in a similar way to how video servers such as MediaMaster can be controlled as a DMX fixture. Liberation would attach to a block of channels (likely on Artnet, or perhaps via some of the open interfaces) and interpret the values there to select clips, adjust parameters and so forth. This could work similar to MIDI mapping, but for ease of fixture definition it would be nice if the allocation was fixed. Desk developers would likely add the fixture to their standard libraries on request.
The value of this would be to synchronise a laser show with a lighting show, either to make single operator busking much easier, or to timecode a show. I often run lights, video and lasers single handed and this requires some level of interoperability (since I’m not an octopus). I’ve done this with other software using an OSC trigger box (typically Streamdeck) - but having everything mapped into Artnet would be a better general solution.
This would also enable timeline programming before Liberation has an internal implementation (even if this is planned).
I think the priority would be low for users who are primarily laser operators with a little bit of lighting (the existing DMX feature request covers that). For a lighting operator wanting to add lasers it would be awesome. That’s not to detract from the APC40 busking workflow which is brilliant, and would likely still be used in hybrid way.
I have to say that this would be a game changer in the use of liberation, This would allow the software to be used in professional touring rather than busking. Production and lighting designers would start to jump at using this feature.
Massively could use the Artnet-in features to control Liberation <3
A lot of our big shows require it as the timecoding happens in LX land.
(this spot reserved for sending epic appreciation for tackling this beautiful piece of software)
So, I had exactly this problem a while ago. And I coded a solution. See attachment. Just need to install the setup.exe. The .xml-File is the device definition for DMX Control.
I’ve been using DMX Control ( DMXControl – Startseite ) for years and built everything around it. It’s a free Software, feel free to give it a try.
I noticed, that the existing MIDI implementation of Liberation although not customizeable is already quite powerful. So I coded a small program that would receive DMX values via ArtNet from any ArtNet sender. I made a “virtual” Laser Device Definition which assigns Features to these DMX channels e.g. channel 1 and 2 encode with clip should run, channel 3 is master dimmer, channels 4… color and so on. Just as you would expect from a DMX controlable Laser. These DMX values get translated to the corresponding MIDI messages and sent via a virtual MIDI cable (loopMIDI | Tobias Erichsen) to Liberation. In Liberation you just need to activate MIDI control and select this virtual MIDI cable as input for that. Works like a charm for me. Upon feedback I could update/expand this workaround until an “official” solution is available. Also right now it is in german…
Qiuck Guide:
First Row: ArtNet Settings. If you use default port you don’t need to change anything.
Second Row: MIDI Device to interact with Liberation. The click “Verbinden” (Connect)
Third Row: Set DMX-Address and see the channels below to know the functions. Clip1 and Clip2 are used to select the running clip. Both of these at 0 stop all clips. Start by increasing Clip1 while Clip2 is at 0. The clips are startet/stopped in ascending order. After the 255th clip increase Clip2 to 1 and it will continue. So you can address 255*255 -1 clips. As of now only one clip at a time can run. The previous one is stopped, the new one started. I had no good idee yet how to do multiple clips at once or start/stop indivudually. ColorMode goes through the color effects on the bottom row of Liberation. And all the other channels address the effects in Liberation. You should be able to just test it and see what changes.
Would love to throw in the suggestion to also have osc as a protocol, especially because we wouldn’t be constrained by only 127 midi or 256 dmx values (2 channels - 16 bit would be an option though).
