QLC 4.9.1
Thinkpad t420
Hello!
I'm having serious trouble to keep OSC going.
I use Ableton Live 9 as sender. Sometime it did happen to work for hours but most of the time its a matter of second before it quit.
Using a OSC signal monitor i can see that the signal comming out of Ableton is steady.
Since im not an expert i was wondering if its a bug or im doing something wrong.
Help would be greatly appreciated
Thank you very much in Advance
Simon
Need Help! Trouble with OSC
-
mcallegari
- Posts: 4830
- Joined: Sun Apr 12, 2015 9:09 am
- Location: Italy
- Real Name: Massimo Callegari
- Contact:
-
mcallegari
- Posts: 4830
- Joined: Sun Apr 12, 2015 9:09 am
- Location: Italy
- Real Name: Massimo Callegari
- Contact:
4.10.0 has just been released.
You should try it cause it's supposed to solve the OSC issues (at least on OSX)
You should try it cause it's supposed to solve the OSC issues (at least on OSX)
-
mcallegari
- Posts: 4830
- Joined: Sun Apr 12, 2015 9:09 am
- Location: Italy
- Real Name: Massimo Callegari
- Contact:
OK, if 4.8.5 works and 4.9.x and 4.10.0 don't, then it has something to do with the new implementation of the OSC plugin.msicar wrote:win 7
4.10.0 Crash as soon as i send OSC signal.
4.8.5 is stable.. Loving it
Simon
I need to kindly ask you 2 things:
- I have a licensed Ableton Lite Live on OSX. Would you please give me the instructions to send OSC from it ? Even better, if you can send me a very simple Ableton project that I can use to reproduce the issue, it would be great
- if you have the chance, can you double check that with TouchOSC the OSC plugin is working ?
Thanks
-
msicar
- Posts: 7
- Joined: Sat Oct 17, 2015 11:31 pm
- Real Name: Simon Carignan
A custom Max for Live device is needed to get OSC going on Ableton. It wont be availlable on the lite version.
In Ableton, I set the proper Target IP and Target port on the sender.
Then i send an OSC adresse like: /qlc/chaser01
I catch it with in the input channel Wizzard
Then I use the adresse as external input in the general slider properties.
I have never used touchOSC... May be time to give it a try. Im away for few days ill get back to you soon
Let me know if you still want a simple Ableton Project, and where to send it.
Thank you very much, your work is greatly appreciated
Simon
In Ableton, I set the proper Target IP and Target port on the sender.
Then i send an OSC adresse like: /qlc/chaser01
I catch it with in the input channel Wizzard
Then I use the adresse as external input in the general slider properties.
I have never used touchOSC... May be time to give it a try. Im away for few days ill get back to you soon
Let me know if you still want a simple Ableton Project, and where to send it.
Thank you very much, your work is greatly appreciated
Simon
-
mcallegari
- Posts: 4830
- Joined: Sun Apr 12, 2015 9:09 am
- Location: Italy
- Real Name: Massimo Callegari
- Contact:
What about his: http://livecontrol.q3f.org/ableton-liveapi/liveosc/msicar wrote:A custom Max for Live device is needed to get OSC going on Ableton. It wont be availlable on the lite version.
Looks like it's free and doesn't need the whole Max framework.
-
msicar
- Posts: 7
- Joined: Sat Oct 17, 2015 11:31 pm
- Real Name: Simon Carignan
Don't know LiveControl but it look to me that it turn Ableton into a OSC receiver. To control it with Touch OSC
I use Ableton as a sender to control QLC+
All the time i was trying to get 4.9.0 to work i had the impression that QLC+ could not support all the data that it was receiving. Just an impression since my knowledge in OSC is limited.
hope it helps
Simon
I use Ableton as a sender to control QLC+
All the time i was trying to get 4.9.0 to work i had the impression that QLC+ could not support all the data that it was receiving. Just an impression since my knowledge in OSC is limited.
hope it helps
Simon
-
mcallegari
- Posts: 4830
- Joined: Sun Apr 12, 2015 9:09 am
- Location: Italy
- Real Name: Massimo Callegari
- Contact:
As far as I can tell, it can send data as well.4. LiveOSC accepts packets on port 9000 and sends data on port 9001
You mentioned a OSC monitor earlier. Is there any chance you can get a trace of the messages that Ableton sends ?
I am pretty sure it's a particular message that crashes the QLC+ plugin, but we need to find out which one it is.
Then solving the issue should be pretty easy.
-
msicar
- Posts: 7
- Joined: Sat Oct 17, 2015 11:31 pm
- Real Name: Simon Carignan
I can see in Ableton the message being sent, and how it come up in the OSC monitor.
Ableton:
/qlc/red 0.
show up in the monitor as:
[7770] /qlc/red/0.000 (float)
another example:
Ableton:
qlc/fader/red 0.510464
OCS monitor:
[7770] /qlc/fader/red/0.510 (float)
let me know if you need more infos
Simon
Ableton:
/qlc/red 0.
show up in the monitor as:
[7770] /qlc/red/0.000 (float)
another example:
Ableton:
qlc/fader/red 0.510464
OCS monitor:
[7770] /qlc/fader/red/0.510 (float)
let me know if you need more infos
Simon
-
mcallegari
- Posts: 4830
- Joined: Sun Apr 12, 2015 9:09 am
- Location: Italy
- Real Name: Massimo Callegari
- Contact:
Apparently they look good.
QLC+ accepts floats numbers and any OSC path.
There must be something happening sometimes, for example an integer value or a change of OSC path that cause instability.
Problem is to catch it...
Is your OSC monitor capable of saving a trace with all the OSC messages sent by Ableton (mayb while QLC+ is open) ?
Then you can stop the dump when QLC+ crashes and maybe we can find out what it was
QLC+ accepts floats numbers and any OSC path.
There must be something happening sometimes, for example an integer value or a change of OSC path that cause instability.
Problem is to catch it...
Is your OSC monitor capable of saving a trace with all the OSC messages sent by Ableton (mayb while QLC+ is open) ?
Then you can stop the dump when QLC+ crashes and maybe we can find out what it was