orzer

sorry i am sure i am overlooking something basic, for i am really inexperienced with this.

I am trying to create a Touch OSC interface for Ableton live, which turns out to work quite well. On one page of my template, i try accessing the ML 185 device with OSC messages. I arranged a few labels (=text boxes) for the template, so i can read parameter values of my faders. Everything is set up fine, when i fire messages manually, they display as desired. However, when i mess with the faders live, the output kind of "glitches", it displays the starting value as well as the current position changing in a very fast pace, making it barely readable and, what is worse, never ending on the actual value, but displaying the starting point. I tried adding a qlim as well as a speedlim object, but here it behaves especially weird: For two values or so it works nicely, and then freezes completely, not putting out anything until i restart max or delete and recreate the speedlim object.

I do not have any idea if this is a common error/mistake, or if i left out any important detail. I will happily provide the code if helpful, although it is very messy...

sorry i am sure i am overlooking something basic, for i am really inexperienced with this.
I am trying to create a Touch OSC interface for Ableton live, which turns out to work quite well. On one page of my template, i try accessing the ML 185 device with OSC messages. I arranged a few labels (=text boxes) for the template, so i can read parameter values of my faders. Everything is set up fine, when i fire messages manually, they display as desired. However, when i mess with the faders live, the output kind of "glitches", it displays the starting value as well as the current position changing in a very fast pace, making it barely readable and, what is worse, never ending on the actual value, but displaying the starting point. I tried adding a qlim as well as a speedlim object, but here it behaves especially weird: For two values or so it works nicely, and then freezes completely, not putting out anything until i restart max or delete and recreate the speedlim object.

I do not have any idea if this is a common error/mistake, or if i left out any important detail. I will happily provide the code if helpful, although it is very messy...


udpsend-osc-messages-freezing-max

Sounds like you've got a feedback loop. You're sending OSC messages to Max which is sending them right back to your device. Generally use a gate to stop messages being received to be sent back out.

yes sounds like feedback, try and only use a [set $1] message to update a slider in your own UI from external data.

He, sorry for the late response, but i somehow thought this thread still wasn't authorized...

Thank you very much for your replies. The thing is, i am not actually updating the sliders from my daw to avoid feedback problems. I am only updating "unrelated" text boxes.

However, i tried to edit my patch to try your suggestions anyway. Now i am getting even stranger behavior: My udprecive object doesn't seem to do anything now when i connect it to a print-object. When i close Max, everything works as programmed though, and i don't even get the jittery thing i described above anymore. I could just leave it like that i guess, but expanding the patch will be difficult like that.

edit: After tidying up and splitting into several devices everything seems to run normal. Thanks again for the help, will try to solve another patch i made which i think has a feedback issue.

Thank you very much for your replies. The thing is, i am not actually updating the sliders from my daw to avoid feedback problems. I am only updating "unrelated" text boxes.
However, i tried to edit my patch to try your suggestions anyway. Now i am getting even stranger behavior: My udprecive object doesn't seem to do anything now when i connect it to a print-object. When i close Max, everything works as programmed though, and i don't even get the jittery thing i described above anymore. I could just leave it like that i guess, but expanding the patch will be difficult like that.

edit: After tidying up and splitting into several devices everything seems to run normal. Thanks again for the help, will try to solve another patch i made which i think has a feedback issue.


When udpreceive is blocked in the edit mode it maybe to do with the TCP port being already taken. Try temporarily adding 1 to the port number while you're developing.

When udpreceive is blocked in the edit mode it maybe to do with the TCP port being already taken.  Try temporarily adding 1 to the port number while you're developing.


Ok, i'll try it next time it occurs. Thanks!

udpsend OSC messages freezing max