OSC message via channels display window

[pace514]

Hi Claude !!!

Obviously, you can select a channel by clicking on it. But would it be possible to send an OSC message by clicking on that same window ?

I guess i'm dreaming in color... Would be awesome though...

Have a nice day !

[admin]

You can do this with the latest builds of LXBeams and LXConsole.

When editing the display configuration in LXBeams, draw a channel text field. You can double-click it to directly enter the label text eg. "test osc".

With the channel text field selected, in the Inspector's info table enter something like the following for the "channel" property:

Code: Select all

osc:127.0.0.1:53000~/cue/1/start

If you use the Setup window OSC Out tab, you could create a named destination:

qlab = 127.0.0.1 port 53000

Then the channel text field's property could be:

Code: Select all

osc:qlab~/cue/1/start

[pace514]

Hi Claude !!!

I tried making it works for good moment without success.

I did this little video. Maybe you can spot a mistake somewhere...

https://www.dropbox.com/s/9e7dielkopc9b ... 1.mp4?dl=0

Thank you again !

Pascal

[admin]

In QLab's settings, general pane, do you have the checkbox Use Passcode checked? That will prevent LXConsole's OSC from being accepted.

In order to verify that LXConsole can/is sending OSC to QLab, try creating a new cue. Then in "Cues" display mode, use the Inspector's Cue Options tab to add an OSC action to the cue. Use the same IPAddress:Port and OSC message as you are in the test. Then use the GO button to play your test cue and see if QLab responds. That should tell you if it is a configuration issue or if something specific to the display configuration method is the problem.

Also verify that your LXConsole version is Version 6.3.0 (17516.1) and your LXBeams version is Version 6.3.0 (18917.1).

[admin]

https://youtu.be/lqKfHNHx4sU

[pace514]

Hi Claude !!!

First, LXConsole version is: Version 6.3.0 (17514.1)
LXBeam version is: Version 6.2.2 (18520.1) Could not find version 6.3.0 (18917.1).
Could it be an issue ?

https://www.dropbox.com/s/seapqtruxuj2o ... b.mp4?dl=0

À+

Pascal

[admin]

Your dropbox shows that you have the default OSC Out target set to QLab. You also have enabled "echo command line and cue fade info". This is meant to work with remotes using TouchOSC or Lemur. But that is why the first message captured is setting the text of a field named "next_cue" when the go button is clicked. There are a whole slew of messages sent while a cue is running to update TouchOSC or Lemur's status fields.

If you have QLab set as the overall OSC Out target (and you obviously do from the video) then you do not need to specify a target in either the action command or the cue action. You should be able to just enter "osc:/cue/1/start" for the channel property of your test field in LXBeams and then send the display configuration to LXConsole.

Yes, it is important to have the latest build of both LXBeams and LXConsole and you'll get that on the LXBeams/LXSeries Pro download page.

[admin]

And, just an observation, when you added a cue action in your video, you didn't click edit after selecting the OSC action type from the popup menu.

What you did was paste the command text for the channel display "osc:127.0.0.1:53000~/cue/1/start".

Clicking edit allows the separation of the address:port (or target) and the OSC address pattern "/cue/1/start".

The "osc:" prefix for the channel text field's property tells LXConsole that this is not text to be interpreted on the command line. The "osc:" prefix should not be used as part of a cue action.

The way the channel text fields work in a display configuration is that if the channel property is not the same as the channel text (which is the way the majority of the channel display works) then the property is added to the command line. In this way you can make clickable text on the display that selects a series of channels. For example, the channel text field could display "Odd" and its channel property could be "1&3&5&7&9". In LXConsole's main display, clicking "Odd" would add 1&3&5&7&9 to the command line, selecting those channels if the command line was previously empty. The only exception to this is the recently added ability to send an osc message using a similar method of clicking on text. The way that LXConsole determines NOT to add the channel property to the command line is when the property starts with "osc:". In that case, the osc: portion is ignored and the rest is interpreted as an OSC action.

[pace514]

Hello again !!!

So as you'll see in this video, i emptied the OSC action command and the cue action and put the complete address in the channel property. Now instead of starting cue 1 in Qlab, the address appears in the command line.

https://www.dropbox.com/s/oueutpskvzagj ... 3.mp4?dl=0


Also, is there really a LXBeam Version 6.3.0 (18917.1). Lated build on the LXBeams/LXSeries Pro download page is:


June 24th, 2022

6.2.2 (18523.1) additional RGBL RGBIL LED support. Option key with Add Layer button duplicates current layer.

[admin]

It looks very likely you have a space in front of the "osc:" in the channel property when you edit it in LXBeams. " osc:" will not get special treatment and will be entered on the command line as shown in your last video.

Both download sites have 6.3.1 installer when you click the latest build link under more downloads.

The site you are going to should be:

Code: Select all

https://www.macluxpro.com/cgi/lxseries10_download.cgi?...

followed by the registered email, etc.

-or-

Code: Select all

https://www.claudeheintzdesign.com/cgi-bin/lxseries10_download.cgi?...

followed by the registered email, etc.