Original LXSeries Forum

Is there an existing Tousch OSC layout to control with faders the channel's level of LX console? In the layout provided with LX Console, there is faders for Sub only. I need faders for channels.
If there is no such layout, could someone explain me what values i have to enter in Touch OSC editor to create my own layout? I have basic knowledge of Touch OSC editor but i don't know what type of value i have to enter for each fader i create in order for them to control channels in LX Console.
Any help is very welcome.

Hi Spadrille,

I have tinkered and prodded, and created:

1. An IPad remote layout for LXConsole with
2. 30 "Flexichannels" faders - i.e., if you are using 30 channels in total, no matter what number you give them, you should be able to automatically assign/propagate the patching with my included script.

It is still a bit round-about, and not quite at a "published" level, but it worked well for me on two shows. Have a look and play around. I have just zipped my project folder, so there might be a few alternative versions which I did not persue in the end (I think the Vxa files).

Also included on the second page some faders for LED/intelligent light control of the selected channel.

Feedback welcome. It is a bit in a round-about way - you need to execute the script each time you evoke TouchOSC (as it transfers things like channel short name and number dynamically), and you need to import the MIDI and OSC patching files created by the script, because you currently cannot access/edit those patches via script hooks .

Here is the file: http://www.budgetfeatures.com/archive/L ... eFK_V1.zip

Hope that helps!

Hi Freddy,

First of all, thank you for your help. 30 channels would be perfect for me. I opened the zip files and, wow, that's a lot of files for someone who was just hoping for a simple Touch OSC layout. Could you help me finding my way around those files? It seems that some files are redundent. What are the difference between those? Also i'm not familiar with qtz file and scripts.
You also talk about channel "short name". What is a channel short name? Sorry about all the questions. Seems i have some things to learn.

Hi Spradrille,

I have written a bit of the documentation into the script file at the start, so looking into this one will probably help a little bit. I also omitted that I am using a software called OSCulator (the file is included), so that the numerical values of the faders are also displayed below (the OSC value sent from LXConsole is usable, but is as often betwen 0 and 1, and not the 0 to 100 percent one is used to read .). And I have used BOTH MIDI and OSC from LXConsole in order to ensure that

a) at all times, LXConsole reacts to the faders,
b) at all times, the faders reaact to LXConsole
c) the values are displayed below the faders.
d) the channel's short name (i.e. the first five letter of the channel's "USE" field ), the channel's channel number, and the channel's percentage are synched and displayed correctly to reflect "flexichannels"
e) the "caching" of the last command in grey when the command line is executed (otherwise it just gets blanked out as soon as a successful execution occurs)

However, I can see that the implementation is less than intuitive for someone who is not very familiar with scripts, quartz, and osculator, so feel free to chop and change my solution to make it simpler...

I would suggest you

a) read the comments at the start of the script file (PropagateChannelSetup_V1.scpt),
b) start by having your show open, executing the script (even without the TouchOSC template), and find and import the MIDI and OSC Actions from the generated files into your LXConsole
c) maybe modify the template with the TouchOSC Editor to loose the more complex features (i.e. Channel percentages, short names, channel numbers)?

Sorry that I can't really offer a quick and easy solution right now, I'm on holidays in Switzerland with only little gear on hand ... And as useful as I find the features I painstakingly implemented - they are often based on a bit of OSC routing and work-arounds, as it isn't trivial matters, and not all fully supported "Out-of-the-box" by LXConsole ...

Good luck!

A simple way of making a touch OSC slider control a channel in LXConsole is to use the OSC address "/lxchannel/nn" where nn is the channel number (don't include the quotes).

So, to make a slider that controls channel 12 in TouchOSC editor, add the slider. Then, uncheck the OSC: auto box. Enter /lxchannel/12 in the text field below the auto box. Leave the Value Range from 0 to 1.

I usually have the "Inverted" check box checked although the slider will control the channel without this.

Thanks. That's really the kind of straightforward way i was looking for. I tried and that works OK except for one thing. Touch OSC controls LX Console but not the other way around. When i make a change in LXConsole, it is not graphically reflected on TouchOSC. Is that a limit of that method or did i do something wrong?

The /lxchannel/ message tells LXConsole to set the level of a particular channel. LXConsole does not send out /lxchannel/ messages for every channel when a change happens. Which, because LXConsole has no idea what channels you are interested in, is what would be necessary for what you want to happen.

So, you need to tell LXConsole which messages to send when a channel changes. You do this by setting the OSC Out preference "Send chanel changes defined in actions"

Then, in the Setup window, OSC tab, you add your /lxchannel/nn messages to the list of actions. You can do this with the Detect button. With detect enabled, moving a slider in TouchOSC should make its message appear.

Then, you click the + button to add an action corresponding to the message.

The final step is to add a "nn@%p" command to the action (where nn is the channel in your message)

The effect of these steps is that when channel nn changes, LXConsole looks in the list of actions and finds it should send out the /lxchannel/ message and the slider moves in TouchOSC.

Look at the uploaded user example, 12dimmers. It can send fade signals back and forth between lxconsol and touchosc.

The latest build 3.3.4 (7210A) will eliminate the last step from the above. When you detect and add a /lxchannel/ message, it will now automatically fill in the appropriate nn@%p command.

That works perfectly. Thank you.