Q Light Controller+

Hello,

As of 4.9.0 TouchOSC is no longer working.

I opened QLC+ blank project went to input output

I adjusted touchOSC for my tablet and nothing it doesn't receive or transmit.

This is windows 7 x64 bit

I rebooted Windows and it resolved the issue.

In the installer It may be a good Idea for windows to add a reboot reminder.

I have also been having issues with TouchOSC after upgrading to 4.9.0

I have a project which makes heavy use of TouchOSC (I have replaced my Behringer LC2412 with a customised TouchOSC template on an iPad). After upgrading to 4.9.0 I have certain OSC controls that don't work, and some that work but don't receive feedback.

From my testing today I have observed :
1) 90% or more of the OSC buttons work fine, with feedback
2) the OSC buttons which don't work are not detected by the Input Profile Editor Channel Wizard
3) I created a new 'test' button on the OSC template, and this was detected by the wizard, but when I went to the Virtual Console to assign it to a button it was not detected.
4) Restarting QLC+ allowed the test OSC control to be AutoDetected in VC and assigned to a VC button, but no feed back is sent to the iPad when using that button.
5) I know the QLC+ functions are running correctly, and in fact if I temporarily assign the VC button to a working OSC button - then the two way communication works fine (ie button press & feedback) - but it won't work when I revert back to the problematic OSC button

The TouchOSC profile file has been stable for a while and thoroughly tested previously, and used in production.

I can't identify anything special about the OSC buttons that don't work. They certainly weren't the last to be added to the OSC template. In fact, other buttons which were added later in the development of the OSC template work fine. All buttons work fine at version 4.8.5, and the TouchOSC / QLC+ configuration has been used live at stage performances.

I'm sorry I can't be more specific or helpful in narrowing down the symptoms , but am willing to provide further information if that will help, and to run further tests as requested.

OS is Mint Linux 17.

I could run tests on Win 7 if that helps, but Linux is my real target OS. I am also very close to having a production ready, headless Raspberry Pi 2 implementation running too.

Cheers,
Nick

Hi,

OSC support was rrwritten from scratch, in order to get rid of an external library.
Can you post your profile, ideally also workspace and touchosc configfile and tell us which buttons do not work?

@Louis: a reboot is not needed, it has to work out of the box, especially with TouchOSC. If there are issues in the plugin, they need to be resolved

@Nick: I have a purchased version of TouchOSC, so if you share the template and indicate the controls that don't work, I can test them out.
As Jano said, the plugin has been completely rewritten, so now we have full control of the OSC protocol, but we probably missed something that was working before.

Thanks for the prompt response guys. I have attached the project file, the input template and a screenshot of the main TouchOSC screen. I will attach the TouchOSC config in a subsequent post (can't seem to add any more to this one).

One of the problematic controls is called "/Main/TapLED"

Since my original post I have noticed that in the XML file, the channel number for this is 60889 but in QLC+ it shows as 60890 !! I edited the channel number in QLC+ and saved it, and then checked the XML file, and again, the numbers were slightly different (ie by 1). Methinks this might be getting closer to the source of the problem - but not sure why just on a few channels.

I will run a few spot checks comparing the QLC+ channel number to the XML number and see if I can learn more.

Cheers,
Nick

Here are another screen shot and the TouchOSC file (I had to add the extension ".txt" in order to upload it)

Cheers,

Nick

OK - as far as I can see - all of the channel numbers in the XML file are one less than what shows in QLC+ so I'm assuming that this is expected behaviour and not as significant as I first thought.

N

@Nick, I managed to load your template in my TouchOSC installation.
The object /Main/TapPush seems to be wroking correctly.
Am I missing something ?
You mentioned a /Main/TapLED, where do I find it ?

Thanks

[EDIT] I found /Main/TapLEDSwitch and that works as expected too

/Main/TapLED is a TouchOSC LED located above and to the right of the 'Tap' button on the Main page. It is defined as the input channel for VC button "TapLight OSC".

"TapLight OSC"/"Tap Light Dummy"/"Tap Light OSC1" buttons are turned ON/OFF in time with speed dial "Music Beat" by virtue of sharing the same Function (chaser "TapLight Dummy") . The "/Main/TapLED" pulses on the iPad to indicate the current temp of "Music Beat".

I hope that makes sense. I'm sorry that that part of the project is a bit convoluted.

Regards,
Nick

I am no expert of TouchOSC layouts, but I just downloaded the TouchOSC editor and opened your layout.
Apparently /Main/TapLED is not a button, so it cannot be pushed. Is this correct ?
QLC+ cannot feedback data to a channel that haven't been used before (manually). This is the same behaviour we had in 4.8.5

Hi Massimo,

Yes, the /Main/TapLED is a TouchOSC LED not a button. This is a technique I have used a few times. I create a TouchOSC button and register,assign etc it in QLC+, and then once the project is working I recreate the TouchOSC object as an LED.

This all works fine, and the project in question works fine at 4.8.5.

As you can see in the input profile /Main/TapLED is registered OK.

The specific problem I am having is that' with 4.9.0 that object is no longer receiving feedback, and even if I create a new button to replace /Main/TapLED, it still does not work. Sometimes I can not register it in the input profile, and sometimes I can register it, but not auto assign it to a VC button. There are other objects affected in the same way too.

If I assign an existing TouchOSC object eg ScanOff to the same QLC+ Button, I see it behaving as expected ie receiving feedback OK, and pulsing as the chaser runs in time with the speed dial.

Hope this all makes sense. If you load the project under 4.8.5 you will see it working as intended. There are other TouchOSC LED objects that continue to work fine at 4.9.0 (eg the Drum Beat LED) so fundamentally the functionality still works - just not for all objects.

I realise that this project uses a large number of OSC objects as well as nearly 20 loop back channels. Could this be contributing to the problem ?

Thanks for your help,
N

Nick, I finally found and fixed what was causing issues on some channels.
It's fixed now on GIT, so if you build from sources, please check it out and let me know if everything works properly now.

By the way, the project you attached has wrong mapping of /Main/TapLED in the Virtual Console. It should be 60890 and not 60891

Thanks Massimo,

I have never build QLC+ (or anything else for that matter !) from source from GIT. It may take me a while.

I'll let you know how I go.

N

Ok, ive experienced similar problems and probably got some hints.

made some packet capture with wireshark and noticed that the outgoing packets from qlc looks different and dont gets recognized by my touchosc, hope you can get something useful out of these two pics.


[img][/img]

[img][/img]


here is how the packages sent from touchosc looks like:

[img][/img]

lasch43 wrote:Ok, ive experienced similar problems and probably got some hints.
made some packet capture with wireshark and noticed that the outgoing packets from qlc looks different and dont gets recognized by my touchosc, hope you can get something useful out of these two pics.

Did you read that I have fixed the issue on GIT ? Have you tested the GIT version ?

I am having problems compiling the latest Git version - in order to test the TouchOSC fix. I am getting errors during compilation - relating to ItemHeight & ItemWidth being uninitialised (see attached log).

Anyone able to help please?

Thanks,
Nick

Hi,

You can ignore the faulty commit: Or remove the release option could work too.

Fixed.
I'm wondering why Travis didn't spot those...

Because this warning is activated by -O2, and travis does not compile release versions.