udp osc choking in max :/

    Feb 10 2014 | 1:34 am
    Im sending some data to a touchscreen with several XY pads. This seems to work with 1 XY pad, but if I add a 2nd XY pad Max starts to choke. Im wondering if there are any strategies to stop this choking? Am I expecting too much to get Max to drive several XY pads?
    I notice the X/Y data is in float format e.g. 0.3456 . Should I try to limit this to 0.34 ?
    Ive tried using speedlim and qlim, but all these seem to result in a very choppy performance on the touchscreen (same as choking).

    • Feb 10 2014 | 1:54 am
      ok so using [round] I have started to get somewhere near where I need to be, but it is still choking in max. Im starting to think that one stream of udp is really quite limited, if your trying to run several streams of data over OSC :/
      Its not only that max starts to choke, it happens so bad that I cannot even open max to edit it :<
    • Feb 10 2014 | 2:04 am
      Are you receiving the data from each pad on seperate UDP ports?
    • Feb 10 2014 | 2:57 am
      no, its all coming from the same udp stream/port. Should I be breaking it up into different ports? Im not sure how I could have separate ports for different xypads in lemur, or touchosc for instance, because they just use one udp port and its the same port for the whole app.
      its quite strange that an XY pad takes so much data that it chokes max up completely and it can only handle 2 or so, at the same time.
      Maybe I should break up the 4 XYpads I have into 4 different pages, and drive each XYpad that is on screen at any time? Seems like the only way. Bit disappointed that I have to create so many workarounds tho for something that seems so simple... :/
      Its worth mentioning that on one touchscreen app Im using, max even struggle with 1 xypad. Is there something wrong with my wifi connection maybe?
    • Feb 10 2014 | 8:15 am
      >Ive tried using speedlim and qlim, but all these seem to result in a very choppy performance on the touchscreen
      ...*on* the touchscreen? You mean your tablet starts acting up?
      Either way you should not be having problems. I regularly run big performance setups on tablets, and having several Multiballs in Lemur is par for the course.
      Show your patch and we can try to find your bottleneck. Oh, and are you connecting via ad-hoc or via a router somewhere? That does matter.
    • Feb 10 2014 | 12:56 pm
      Thanks wetterberg, Its good to know that lemur/touchosc should be able to handle these things easily. I realise now that I was using snapshot a few times instead of sending audio-rate. This seems to be what was causing the lock ups.