Hi there,
Just found QLC+ and looks super promising! I saw in this old thread there is no OSC passthrough:
viewtopic.php?p=54505
I would love it if it were possible to have some RGB string lights attached to a universe and send an OSC message in the format
/rgb r1 g1 b1 r2 g2 b2 ....
My use case is writing realtime apps that will animate many pixels at once. Rather then sending artnet or similar each frame I was hoping to pipe it through something like QLC+, which supports so many formats and provides such great tools for setting up and testing the light set up.
Some other solutions cater for spout/syphon support for this kind of thing but I am after a more widely supported solution that can ideally scale to receiving data from across the network or multiple apps.
This project will ideally be in dart so at present it seems my best bet is to implement the easiest supported protocol I can (artnet) and then if needed I would have the option to use QLC+ passthrough. However, OSC would be much simpler and mean more consistent implementations across different dev environments that usually support it.
If any other ways to achieve this using QLC+ or other tools please do let me know!
nay.
OSC passthrough
-
GGGss
- Posts: 3052
- Joined: Mon Sep 12, 2016 7:15 pm
- Location: Belgium
- Real Name: Fredje Gallon
Welcome to the community,
Now, wait a minute. A passthrough is where QLC+ interprets input and sends it back out. It can also merge input with locally created values.
Why would you need a passthrough in your case? You didn't specify a device behind QLC+ waiting for instructions.
A typical scenario would be something like this:
OSC in -> QLC+ scene / function / ... -> Artnet out (this is where QLC+ takes care of the 'look'; you only instruct via OSC to call this look.)
OR
OSC in -> QLC+ bound sliders to every channel possible -> output. (A huge workload stands before you, adding many sliders and binding them to numerous inputs.)
If you want to control channels directly, I'd go the Artnet or sACN way. Now you can use passthrough and have the inputs directly influence the output. But hey... you are already outputting Artnet / sACN from your environment. Why do you need QLC+ for now? You can go directly from your environment to the output device.
Or do we have a DMX interface hanging somewhere in the line?
Now, wait a minute. A passthrough is where QLC+ interprets input and sends it back out. It can also merge input with locally created values.
Why would you need a passthrough in your case? You didn't specify a device behind QLC+ waiting for instructions.
A typical scenario would be something like this:
OSC in -> QLC+ scene / function / ... -> Artnet out (this is where QLC+ takes care of the 'look'; you only instruct via OSC to call this look.)
OR
OSC in -> QLC+ bound sliders to every channel possible -> output. (A huge workload stands before you, adding many sliders and binding them to numerous inputs.)
If you want to control channels directly, I'd go the Artnet or sACN way. Now you can use passthrough and have the inputs directly influence the output. But hey... you are already outputting Artnet / sACN from your environment. Why do you need QLC+ for now? You can go directly from your environment to the output device.
Or do we have a DMX interface hanging somewhere in the line?
All electric machines work on smoke... when the smoke escapes... they don't work anymore
-
nay
- Posts: 2
- Joined: Tue Jul 09, 2024 7:30 am
- Real Name: rene christ
Thanks for the thorough response. The hardware lighting controller is not yet defined but I am looking for a solution that can be reused between projects that might be built differently and with different hardware.
In this case I will implement Artnet at my end and if the hardware doesn’t accept it I could use the existing pass through to convert. OSC is better supported in the different dev environments we typically work with but hopefully won’t need to implement another artnet solution from scratch next time.
Thanks again.
In this case I will implement Artnet at my end and if the hardware doesn’t accept it I could use the existing pass through to convert. OSC is better supported in the different dev environments we typically work with but hopefully won’t need to implement another artnet solution from scratch next time.
Thanks again.