Thank you very much.
Qt 5.5.1 is scheduled to be released in September and should contain the fix for this problem.
I will produce a TEST version with Qt 5.5.1 and notify you here.
I am looking for a good osc/midi controller for my phone to control qlc+ with. Awaiting your update. TouchOSC is the only one i see that looks well done and popular, but not sure if i want to invest in it yet as I dont know if it will work. Let us know when you can.
It sounds like your looking for an alternative to TouchOSC? I was the same way about buying TouchOSC. I tried 3 or 4 OSC apps before purchasing TouchOSC. In my experience its definitely the easiest to customize, integrate with QLC+, and its stable. Its not free but if you want an OSC app for your phone I highly recommend it.
OSX 10.10.5 QLC+ 4.9.1
Surface Pro4 Windows 10
Raspberry Pi B OLA 0.95
Raspberry Pi 2B QLC+ Swisson XMt-350
Chauvet RDM2Go
Enttec Pro Mk2
ultraDMX Micro
FTDI USB-RS485-WE-1800-BT XLR Korg nanoKONTROL2
Korg nanoPAD2
Haven't had time to ompile a different version of Qlc for my last gig. But on my way back I got an idea of which may be the problem. My Touch osc is set up to send ping and accelerometer messages. This causes lots of OSC traffic. My guess now is that the Qt UDP implementation (or qlc+) probably chokes somewhere (filled buffer or similar)
Haven't tried it yet without accelorometer and ping messages yet though.
Haven't had time to ompile a different version of Qlc for my last gig. But on my way back I got an idea of which may be the problem. My Touch osc is set up to send ping and accelerometer messages. This causes lots of OSC traffic. My guess now is that the Qt UDP implementation (or qlc+) probably chokes somewhere (filled buffer or similar)
Haven't tried it yet without accelorometer and ping messages yet though.
regards teackele
According to the Qt bug report on the UDP socket implementation, that can actually be the cause. Lot of traffic disturbs the socket.
I am eagerly waiting for Qt 5.5.1 to be released. Should happen any day now.
Back to the original post subject... I'm new to QLC and OSC ... I, till now, handled most of the things I wanted using both excellent pieces of software (Thanks to the creators !) ... except I now have the same issue... QLC fails to react to OSC input after a while ...
I read this post, and indeed, the switch between 127.0.0.1 works ... but in the heat of the action, I don't want to stress on this ...
Doing nothing special... I attached some screenshots of the setup.
Just playing around and then for now obvious reason, the TouchOCS (still gives output - blinking green led) is not read anymore by QLC...
It is 'what ought to be' random, I cannot think about a fixture or scene or whatever that causes the halt.
As suggested in this post, switching to and back from 127.0.0.1 reconnects the TouchOCS
I'm running on Windows 7 64 - SP1
TouchOSC is running on my Ipad V2
Enttec DMX USB Pro MK2
Could it still be an "overload" of data ? ... I play quit a bit with the TouchOSC ... with the sliders ... going from one fixture to another ... etc...
TouchOSC is configured as follows :
- no doubletap / no flip / no Ping / no Accelerometer / no TouchMessages
- MidiBridge disabled
- CoreMidi disabled
V 1.9.4
For what it's worth, if other 'dumb' people like me would stumble on this post ... with the latest beta version provide in this post, it works like a charm on Windows...
...