Q Light Controller+

I added a cue list widget in the virtual console window.
Then I added using auto detection external inputs (OSC messages) to the playback Play/Pause, Next Que and Previous Que triggers.

However, none of them seem to respond to these OSC messages.
The only property that works is the Faders property (but I don't need to change that now using OSC, it was just a test).

Also, I re'learned' the OSC messages in the Inputs/Outputs, Profile, Input mapping screen using the wizard, so I know the OSC messages arrive.
Also, when I use the autodetect option in the cue list, the OSC messages are recognized. But when I run the virtual console (green arrow in the top/right), still the cue list only recognize the Fader property.

The keyboard shortcuts to the Prev/Next Cue do work.

I only have on the virtual console, that cue list widget, nothing else (later I need more though).

Do you have any idea what I'm doing wrong? (I'm quite a newbie using QLC+).
Thanks in advance.

Btw, if there is an easy way to assign a button to go to the next step in a Chaser, then I would need cue lists which also would solve my issue.

Below are some screenshots

You have to go into produce mode... when OSC messages are sent, can you see the blue joystick wiggling in your input-outputs tab?

GGGss wrote: ↑Fri Jun 07, 2024 2:29 pm You have to go into produce mode... when OSC messages are sent, can you see the blue joystick wiggling in your input-outputs tab?

I am in produce mode (the screenshot was made in edit mode though).
And I SEE the joysticks wiggling in the Inputs/Outputs profile editor Input mapping screen.

produce mode ... OPERATE mode vs. DESIGN mode, please, once and for all time! what's so difficult about that, it has caused so much confusion already in the past

edogawa wrote: ↑Fri Jun 07, 2024 2:48 pm produce mode ... OPERATE mode vs. DESIGN mode, please, once and for all time! what's so difficult about that, it has caused so much confusion already in the past

Ok, I'm in operate mode.
However, it doesn't work in either mode (I expect it should work in Operate mode, but it doesn't).

Sorry, that was meant towards Fredje
I have no solution for your problem I'm afraid, it's weird that the Properties dialog recognizes the message but then the Cuelist doesn't react. I've worked a lot with MIDI controllers but I've only started to care about OSC, and used it in QLC+ only to try out the 30/60/90 channel templates floating around... bought TouchOSC Android yesterday but only tested it with Mixbus10's TTC-3 transport remote controller page so far.

edogawa wrote: ↑Fri Jun 07, 2024 3:19 pm Sorry, that was meant towards Fredje
I have no solution for your problem I'm afraid, it's weird that the Properties dialog recognizes the message but then the Cuelist doesn't react. I've worked a lot with MIDI controllers but I've only started to care about OSC, and used it in QLC+ only to try out the 30/60/90 channel templates floating around... bought TouchOSC Android yesterday but only tested it with Mixbus10's TTC-3 transport remote controller page so far.

Thanks for at least giving me some clues (and it is not a trivial issue).
I will then make a new post if it is possible to go to the next step in a chaser via a button.

Can you share your TouchOSC template?.

sbenejam wrote: ↑Sat Jun 08, 2024 5:04 am Can you share your TouchOSC template?.

I'm afraid not, as I'm not using TouchOSC .. I'm using GigPerformer.

edogawa wrote: ↑Fri Jun 07, 2024 2:48 pm produce mode ... OPERATE mode vs. DESIGN mode, please, once and for all time! what's so difficult about that, it has caused so much confusion already in the past

I know - my bad ... will tattoo that on my chest.