Controlling Light Dashboard via OSC

[Sven Eriksson]

Hi!

Does anybody know if there is a way to control the Light Dashboard in QLab 4 via OSC. In the QLab OSC Dictionary ( http://figure53.com/docs/qlab/v4/scripting/osc-dictionary-v4/ ) there are commands for doing stuff to the dashboard but I haven't gotten it to work (maybe because I hardly know what I'm doing OR maybe because it isn't possible).

In my trials I've been using OSCulator, QLab and TouchOSC.

Best Regards Sven

[Sven Eriksson]

Ha! Nevermind! I managed to do it! My problem was that I didn't convert the OSC input to integers before passing it on to QLab. 

// Sven

[Scott McGlynn]

Sven,

After much assistance from Sam Kusnetz at Figure 53 I was able to get a setup working using OSCulator, Qlab, and TouchOSC. When I'm home tonight I'll send you my workspace and OSCulator template.

The broad strokes are:

1. Create a light cue in your workspace. Without this placeholder you can't communicate with the dashboard as far as I know. It need not have any commands but it must be a light cue.

2. Map OSCulator to send a command to that light cue in the standard Qlab light osc dictionary BUT reference the dashboard. For example, /dashboard/setLight myLight xx where 'setLight' is the name of your light cue and 'myLight' is the name of an instrument in the patch and xx is the value you are passing from TouchOSC through OSCulator

The biggest headache I had that Sam solved was the tricky specifics on how to set up variables in OSCulator. That process didn't quite match my approach from the standpoint of a programmer; some of it has been simplified from that mindset.

Utilizing the Workspace status window to see exactly what OSCulator is sending to Qlab is very helpful in troubleshooting. (workspace status --> logs --> OSC input)

One of the successes I had with this project was that I could control a moving head RGB wash with an iPad mapped as my stage...where ever I touched my finger to the iPad screen is where my light fixture hit the stage. This really simplified located my moving heads during tech. We didn't need it for this show, but it worked well enough that I could use it as a follow spot (which our venue cannot support in the usual way as there is no reasonable follow spot location that is human accessible)

Scott McGlynn

[Sven Eriksson]

Great! I was also going for simplifying moving head usage. Looking forward to seeing your solution and comparing it to mine :)

// Sven

[Conrad Stolze]

Scott -

Any chance I could get a copy of your OSCulator workspace? 

[Sven Eriksson]

Here are the files. It's the QLab, the OSCulator och TouchOSC files so you can see exactly what I've done. 

I made a custom layout in TouchOSC Editor for a moving head (Martin MAC 500) and since I'm using the moving head in 16-bit resolution (2 DMX channels for both pan and tilt) i send a number between 0 and 65535 directly from the XY-pad in the layout instead of letting OSCulator crunch the numbers.

// Sven

[Sven Eriksson]

So maybe you have missed it but I solved my problem ;) I posted a minute or so before your answer. So the files I sent are my solution :)

// Sven

Den lördag 29 april 2017 kl. 16:47:37 UTC+2 skrev Conrad Stolze:

[Conrad Stolze]

Thanks. Very helpful.

[Conrad Stolze]

Appreciate you sending the files, and I feel like I 'almost' have this working, but there seems to be something missing in every test I try.

When I use your OSCulator/TouchOSC files, the TouchOSC to OSCulator connection works (seeing button/fader activity), but for some reason I can't get OSCulator to connect to QLab - tried both localhost:53000 and {direct IP}:53000. Neither works, and if I use an OSC monitor on the output port, I also don't see any activity.

I then tried a similar direct approach with TB Midi Stuff, as it supposedly has the ability to send OSC arguments as integer only.  With it, I have a QLab connection, and can see the data in Qlab's Status window, but the arguments don't pass when the argument is set to integer. They 'do' pass when set to float, though I'm assuming QLab won't respond to Float arguments. I can, however, successfully send OSC to individual cues using TB to start, disarm, etc - so I know the TB>Qlab connection is valid.

I then tried Lemur, which I can script to send integer arguments - and I'm seeing what I believe to be properly formatted OSC values in the QLab status window - but not getting anything to respond in QLab. I've validated with an external OSC monitor that the argument is being passed as an integer value. 

Assuming 'mylight' is the fixture I'm trying to address, the OSC I've tried sending is:

/dashboard/setLight mylight.dim 100

I've also tried sending similar to a cue numbered '1'

/cue/1/setLight mylight.dim 100

Is there anything about the format of the OSC going to QLab that I'm missing for this?

[Sven Eriksson]

Hmm I hope someone else, better than me sees this because I really don't know what could be wrong...

Like you say, this: 

/dashboard/setLight mylight.dim 100

should rule out any integer issue because it is the correct syntax if your fixture is named "mylight" and "dim" is the parameter you set up in the definitions section for that fixture.

You don't have a conflict setting up the same port for TouchOSC -> OSCulator as OSCulator ->QLab?

Did you check the "Use OSC Controls" checkbox in the QLab settings?

Sorry for asking such basic questions but you never know... ;)

Another way to troubleshoot is to cut out the OSCulator part and try to see if you have contact with TouchOSC -> QLab by pressing one of the Capture buttons in the Preferences > OSC Control section after directing TouchOSC to 53000.

The last thing I could think of is if you have some kind of firewall set up that might be interfering.

That is all I could think of. Let me know if you get it to work :)

// Sven

[Sven Eriksson]

I did some screen dumps on all the settings I use when the the files are working on my computer with the ip adress of 192.168.1.3.

// Sven

[Conrad Stolze]

Thanks - appreciate the feedback.  The screen grabs were helpful in at least confirming my setup was pretty much the same as yours.

What I know:

• OSC is on in Qlab, as I'm getting some OSC apps to connect with it and data can be seen by QLab's status window
• I can connect to Qlab from everything directly except OSCillator - including TB Midi Stuff, TouchOSC and Lemur. i'm assuming this cancels out a network/firewall conflict (?)
• Unfortunately, TB and TouchOSC won't feed integer arguments, so they're out for now
  
• Lemur does send integer arguments, and is seen by QLab's OSC status logs - but nothing happens with either cues or the dashboard when sent.

I'm assuming I have something set up incorrectly with OSCillator > QLab, but that connection looks pretty straightforward - just like yours, set to localhost:53000. My preference would be to use something without OSCillator in the middle, but if I can get it working as you have, I can better see what it's sending that might be different from Lemur.

I'll keep digging. Missing something simple...

[Scott McGlynn]

Conrad,

Attached are my Qlab Workspace and OSCulator files that work. See if anything in there helps. 

Scott McGlynn

[Conrad Stolze]

Thanks, Scott - I'll take a look!

[Conrad Stolze]

I tried out your files, Scott, and as with Sven's, everything appears to be set up as it should - but I'm still not getting OSCulator to show any connection to QLab.  I mapped TouchOSC to your OSCulator mappings, and I'm seeing activity there, but the localhost connection isn't showing any activity in QLab's OSC Status window.

I can send OSC locally from QLab and have the Dashboard respond properly.

I can send the exact same OSC from Lemur and see it in Qlab's OSC Status window, formatted exactly as the local command, but nothing happens in the Qlab dashboard. I've even tried the OSC message both in and out of quotes - still no dice.

Appreciate you guys providing the files - they definitely help me understand what's going. I think I've got something else going on inside of Qlab that I need to figure out.

Thanks

[Conrad Stolze]

An OS update got OSCulator working for me.  The other apps apparently aren't sending as well formed OSC for Qlab to respond properly.

All is working well with TouchOSC and OSCulator now. Andy provided some additional information, as well.

  

Thanks again for your help. 

[nizer]

Why can't this all be done without using OSCulator? Can't QLab interpret the OSC messages sent from TouchOSC? or Lemur?

Thanks for any guidance.

[nizer]

One thing to note is Lemur OSC doesn't allow for SPACES in OSC commands, so it breaks the message.

On Thursday, May 4, 2017 at 3:30:17 PM UTC-4, Conrad Stolze wrote:

[Scott McGlynn]

Nizer,

I've set up a new work flow this year and I can now say that yes; it is theoretically possible without Osculator. You would need to set the OSC command in the TouchOSC template to match whatever you need Qlab to do (eg /cue/1/setLight mylight.dim x). Having said that though, I've gone to a completely different setup that is working much better for me:

I am still using a TouchOSC template but now using MIDI commands as those can be attached (in the Qlab light patch) to the default parameter of each instrument AND then automatically give feedback to the TouchOSC template. That means when you activate the dashboard or put the playhead on any light cue and then hit the levels tab, your TouchOSC template controls move to the positions of the commands/parameters reflected in Qlab. THAT was the big bonus I've been looking for. Now my virtual desk always reflects the positions, colors, and intensities of Qlab (either live in the dashboard or blind in a cue with the levels tab active).

However, note that I said you can attach MIDI only to the default parameter of an instrument. That meant I had no control of the other 15 - 30 parameters of my intelligent fixtures. My workaround was to define each parameter of each of my fixture types as its own light definition. That means I have a LOT of definitions but each one only has one parameter and therefore can be controlled and fedback to/from MIDI.

It works quite well as long as you don't flood the MIDI path. So, XY Pads are a no go; but a pan knob and a tilt slider work great together. The other drawback is you only have 128 steps of resolution. I'd really prefer to have OSC working both directions as it is much more robust in resolution, data volume, and flexibility. Right now, Qlab will only listen to one MIDI channel and I'm running out of command space (128 CCs, 128 Note ons, Program change and note off don't help me with sliders)

My dashboard is a [bigger] mess now but I don't care because I never need to use it except for the 'new scene with all' or 'update most recent cue' buttons. Everything else comes from my virtual desk in TouchOSC. I am actually looking forward to tech rehearsals this year.

[Mark Nizer/Neisser]

Awesome. What a great solution. I too wish for a OSC solution, but ur slider via midi and individual patch for each is genius. I have used LX Console as a OSC portal and run lights via midi from Qlab to have a similar solution, but I was trying to simplify. 

Mark Nizer/Neisser

📩 Ni...@active-media.com

📲 434-974-9699

💻 http://activemedia.org

💻 http://Nizer.com

--
Contact support anytime: sup...@figure53.com
Follow Figure 53 on Twitter: https://twitter.com/Figure53
User Group Code of Conduct: https://figure53.com/help/code-of-conduct/
---
You received this message because you are subscribed to a topic in the Google Groups "QLab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qlab/VKXugV3wJ-c/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/c90659fa-2196-4c9e-a78a-04446c2d02e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Sven Eriksson]

Oh, but it can! Here is my Lemur-file with one single fader connected to the value mac1.intensity in the dashboard.

// Sven

[nizer]

Isn't this all being done with MIDI? There is no OSC happening here. Correct?

Not sure why QLab doesn't react to OSC from TouchOSC formatted correctly. without using Osculator.

[nizer]

I don't think the below is correct?

I believe the example should be 

/dashboard/setLight myLight xx where 'setLight' is part of QLab OSC library and SHOULD NOT BE CHANGED and 'myLight' is the name of an instrument in the patch and xx is the value you are passing

[Sven Eriksson]

So my new solution is not what you where looking for? It is Lemur -> QLab without the use of OSCulator. 

// Sven

[nizer]

After two days of frustration I am reaching out for help. Maybe I am missing something basic.

If I make a OSC cue within QLab "/dashboard/setLight SlimPARProH.Red 2" and hit GO, I can make the red channel on my SlimPARProH go to 2%

If I make a OSC cue within QLab "/cue/4/start" and hit GO, I can make cue 4 start

If I send "/cue/4/start" from a TouchOSC button, I can make cue 4 start

If I send "/dashboard/setLight SlimPARProH.Red 2" from a TouchOSC button, Nothing Happens. TouchOSC seems OK with the spaces. I am not sure what the value OSC has when it only works for some stuff and not others. Running another program to interpret the OSC messages seems to defeat the whole purpose of QLab.

[Mark Nizer/Neisser]

It is, sort of. I was hoping to use OSC.

-------------------------------------------

Mark Nizer

[Christopher Ashworth]

Hi Mark,

Must be brief, but: try bringing up the workspace status window, go to the logs tab, and enable incoming OSC logs to see what messages are being received

(mobile)

[nizer]

Thank you so much.

Here is what I see.

OSC button in QLAB

2018-02-03 17:33:44 (1138.227): UDP 10.0.1.99:53001 sent OSC message: /dashboard/setLight "SlimPARProH.Red" 88

TouchOSC button ( I added quotes to the message in the touches window. The one comes from "value" 

2018-02-03 17:33:52 (1145.856): UDP 10.0.1.3:53001 sent OSC message: /dashboard/setLight "SlimPARProH.Red" 88 1

[micpool]

Sorry critical  typo in previous last word of post

I've been having a similar problem all day with the dashboard on a totally unrelated project, and had filed a support ticket.

I've now worked out what is going on

/dashboard/setLight is an OSC address that requires 2 arguments, a string followed by a number. 

When you put the string argument as part of the address in TouchOSC followed by the number the OSC input monitor in QLab status shows it as a valid OSC message with the correct arguments and it is identical to the message monitored from the same OSC sent from a qLab network cue.

If you monitor it in a different OSC monitor e.g OSCULAtOR, it doesn't register as anything. i.e No valid  OSC is received.

I'm not sure you can send an address with 2 arguments in TouchOSC.

Mic

Previous      Next

[Mark Nizer/Neisser]

Fascinating. We will prevail. 

Mark Nizer/Neisser

📩 Ni...@active-media.com

📲 434-974-9699

💻 http://activemedia.org

💻 http://Nizer.com

--

Contact support anytime: sup...@figure53.com
Follow Figure 53 on Twitter: https://twitter.com/Figure53
User Group Code of Conduct: https://figure53.com/help/code-of-conduct/
---
You received this message because you are subscribed to a topic in the Google Groups "QLab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qlab/VKXugV3wJ-c/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qlab+uns...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/2f7f8c94-1070-4c20-9ea1-6016930cddca%40googlegroups.com.

[Chet Miller]

TouchOSC is only capable of one argument at a time iirc. (From my time playing with it controlling d3. We normally suggest cues in an xx.yy.zz setup for a myriad of reasons I won't go into)

In touch, I can send only one set. Lemur will let me do two or more.

Also, I preach the gospel of Lemur whenever possible. It's a great piece of software that doesn't require a JRE. Worth the extra 20 imo.

[Mark Nizer/Neisser]

But lemur won’t let u do spaces in a OSC command. :-/

Mark Nizer/Neisser

📩 Ni...@active-media.com

📲 434-974-9699

💻 http://activemedia.org

💻 http://Nizer.com

--
Contact support anytime: sup...@figure53.com
Follow Figure 53 on Twitter: https://twitter.com/Figure53
User Group Code of Conduct: https://figure53.com/help/code-of-conduct/
---
You received this message because you are subscribed to a topic in the Google Groups "QLab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qlab/VKXugV3wJ-c/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qlab+uns...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/5a49a568-fba6-4e80-99f3-4c9eb54c6a83%40googlegroups.com.

[nizer]

So I couldn't sleep thinking about this:

I had a thought. If I just remove the last part of the message (in this case 88) and put that in the Value Range field the message should be correct.

It now shows this in the logs:

From QLab's OSC command: (Works)

2018-02-04 01:36:05 (1978.837): UDP 10.0.1.99:53001 sent OSC message: /dashboard/setLight "SlimPARProH.Red" 2

From TouchOSC on my iPad (Still didn't work)

2018-02-04 01:36:09 (1983.523): UDP 10.0.1.3:53001 sent OSC message: /dashboard/setLight "SlimPARProH.Red" 66

From TouchOSC on my iPad (with no quotes - also didn't work)

2018-02-04 01:36:09 (1983.523): UDP 10.0.1.3:53001 sent OSC message: /dashboard/setLight SlimPARProH.Red 66

From TouchOSC on my iPad (Works)

2018-02-04 01:37:43 (2077.530): UDP 10.0.1.3:53001 sent OSC message: /cue/4/start 1

2018-02-04 01:37:43 (2077.583): UDP 10.0.1.3:53001 sent OSC message: /cue/4/start 0

[micpool]

I'm not sure with all the troubles in the world that OSC is a reason to lose sleep but..

I assume it's still not working from TouchOSC; Here's why.

An OSC message consists of an OSC Address Pattern followed by an OSC Type Tag String followed by zero or more OSC Arguments.

So in an OSC monitor that shows the full structure a valid message looks like this

/dashboard/setLight ,si "1.intensity" 25

the si is the tag type showing the data types of the arguments, in our case 1 string and 1 number

The problem with the QLab OSC Monitor is it displays the valid OSC message and the invalid message, produced by putting your argument string before the type tag string, as identical messages.

Mic

[micpool]

On Sunday, February 4, 2018 at 1:54:39 AM UTC, nizer wrote:

But lemur won’t let u do spaces in a OSC command. :-/

Again you are confusing addresses and arguments. The mapping window in Lemur only allows the same as TouchOSC i.e an address with a single numeric argument. (with the advantage of defining what state change of the variable it is sent on thus avoiding double triggers) 

But it is very easy to get  Lemur to send anything you want (except an address with 0 arguments)

Highlight the button in the project pane

Click the script icon to add a script to the button

Here is an example script  that has a space

decl commandstring;

commandstring='/cue/2/name';

oscout(0,commandstring,'salad days');

This would show up in an OSC monitor as

/cue/2/name ,s "salad days"

OSC addresses never have spaces in them.

Mic

[Mark Nizer/Neisser]

Cool. I’ll try that. I assume this still won’t work for Qlab and my lighting desires. 

Mark Nizer/Neisser

📩 Ni...@active-media.com

📲 434-974-9699

💻 http://activemedia.org

💻 http://Nizer.com

--
Contact support anytime: sup...@figure53.com
Follow Figure 53 on Twitter: https://twitter.com/Figure53
User Group Code of Conduct: https://figure53.com/help/code-of-conduct/
---
You received this message because you are subscribed to a topic in the Google Groups "QLab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qlab/VKXugV3wJ-c/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qlab+uns...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/4325c118-58fa-4004-a3bc-8c35291de568%40googlegroups.com.

[micpool]

On Sunday, February 4, 2018 at 6:55:54 PM UTC, nizer wrote:

Cool. I’ll try that. I assume this still won’t work for Qlab and my lighting desires.

 

Why wouldn't it?

Multiple arguments in Lemur are programmed as an array so you want this in a script

decl commandstring;

commandstring='/dashboard/setLight';

oscout(0,commandstring, {'SlimPARProH.Red', 88});

For a Lemur  fader you would want this script for Fader1 (set script execution  to on expression x any)

decl commandstring, fadervalue;

commandstring='/dashboard/setLight';

fadervalue=round(Fader1.x*100);

oscout(0,commandstring, {'SlimPARProH.Red',fadervalue});

Mic

[micpool]

Actually for a fader you can reduce the fader rate considerably by creating an expression on the fader called integer

=round(Fader1.x*100)

and then using this as the script, attached to Fader1

decl commandstring, fadervalue;

commandstring='/dashboard/setLight';

fadervalue=Fader1.integer;

oscout(0,commandstring, {'SlimPARProH.Red',fadervalue});

Mic

[micpool]

On Sunday, February 4, 2018 at 9:55:13 PM UTC, micpool wrote:

Actually for a fader you can reduce the fader rate considerably by creating an expression on the fader called integer

=round(Fader1.x*100)

and then using this as the script, attached to Fader1

decl commandstring, fadervalue;

commandstring='/dashboard/setLight';

fadervalue=Fader1.integer;

oscout(0,commandstring, {'SlimPARProH.Red',fadervalue});

and set the execution to     on expression    integer      any 

[Mark Nizer/Neisser]

So excited. U r the DUDE!!!!

Mark Nizer/Neisser

📩 Ni...@active-media.com

📲 434-974-9699

💻 http://activemedia.org

💻 http://Nizer.com

--
Contact support anytime: sup...@figure53.com
Follow Figure 53 on Twitter: https://twitter.com/Figure53
User Group Code of Conduct: https://figure53.com/help/code-of-conduct/
---
You received this message because you are subscribed to a topic in the Google Groups "QLab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qlab/VKXugV3wJ-c/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qlab+uns...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/2fa941fe-50b4-4f9c-9ef9-98e45a515dfb%40googlegroups.com.

[nizer]

I got  this working. THANK YOU. A couple questions. 

How does the extra expression reduce the fader rate. Not sure what it is doing?

Can I then have the reverse feedback via OSC from QLab if I move the fader within the QLab Light Dashboard back to the iPad or am I stuck doing the midi thing and making individual "lights" for ever channel in my moving lights (i.e. PAN/TILT, Focus, etc)

Lastly, can I change the value on the slider for when i check the Value x box in Lemurs Properties tab.

[Christopher Ashworth]

The light dashboard does not currently provide feedback via OSC; only MIDI

(mobile)

[micpool]

On Monday, February 5, 2018 at 4:15:27 AM UTC, nizer wrote:

I got  this working. THANK YOU.

Great!

 

A couple questions. 

How does the extra expression reduce the fader rate. Not sure what it is doing?

Your script to send the fader level to the dashboard is set to execute on any change in the x value of the fader. This could  be loads of levels to go from 51 to 52 

If you execute the script on the integer expression changing there will only be 100 OSC messages from 1 to 100.

If you change the expression to (round(Fader1.x*200))/2 you will get 2000 values sent etc.

Can I then have the reverse feedback via OSC from QLab if I move the fader within the QLab Light Dashboard back to the iPad or am I stuck doing the midi thing and making individual "lights" for ever channel in my moving lights (i.e. PAN/TILT, Focus, etc)

 See Chris's reply.  There may be more you can do with light cues themselves  by getting the light command text.. But getting an external controller to track light levels within QLab does seem to be difficult, beyond the MIDI feedback provided. Possibly too difficult to be worth the bother, currently.

Lastly, can I change the value on the slider for when i check the Value x box in Lemurs Properties tab.

Yes, thats straightforward. the value can be any expression (not just the x value of the fader) so all you have to do is type integer and it will display the result of that expression i.e the rounded value of the fader 0-100.

Mic

[Mark Nizer/Neisser]

Could u add MIDI feedback on all patches on a lighting instrument to the wishlist? :-)

Mark Nizer/Neisser

📩 Ni...@active-media.com

📲 434-974-9699

💻 http://activemedia.org

💻 http://Nizer.com

--
Contact support anytime: sup...@figure53.com
Follow Figure 53 on Twitter: https://twitter.com/Figure53
User Group Code of Conduct: https://figure53.com/help/code-of-conduct/
---
You received this message because you are subscribed to a topic in the Google Groups "QLab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qlab/VKXugV3wJ-c/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qlab+uns...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/8431DEFB-3417-4F80-A8F9-0577D1D6A938%40figure53.com.

[Sam Kusnetz]

Hi Mark

I’m not sure what you mean by “feedback on all patches”, but if you’re asking for MIDI control of more than one parameter of each light, we’ve got it on the list.

Best

Sam 

—

Sam Kusnetz | Figure 53

s...@figure53.com

You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/459ABC06-33F1-4C97-A618-A4CABB8D521E%40gmail.com.

[Jsep]

Hi all,

bit late but i broke my head on this issue for a whole day and i finally got it. I'm using a constant CHOP and a CHOP execute dat together with a OSC out DAT, using the following script in the CHOP execute dat: Weirdly enough it only works when i send out to port 53535 instead of 5300, but it works great.

def onValueChange(channel, sampleIndex, val, prev):
    osc_base_address = "/dashboard/setLight"
    light_name = "LAROND"  # Replace "LAROND" with the corresponding light name
    osc_address = "{} {} {}".format(osc_base_address, light_name, val)
    osc_out = op('osc_out1')  # Replace 'osc_out1' with the actual name of your OSC Out DAT
    osc_out.send(osc_address, [])
    return

Weirdly enough it only works when i send out to port 53535 instead of 5300, but it works great.

hope this can be of help.