Izzy unexpectedly close without a crash report while receiving/sending OSC

Sanza

Hi all !

I'm working on a project that require to receive a lot of OSC values (around 200).
I'm doing some math to it and resend it to an another computer with Ableton live via ethernet cable.

Or sometimes, Isadora just suddently stop the program (even when i'm not programing) and when i opened it back it doesn't show any crash report.

I have reseted the Isadora preferences but no change for now.

I'm using Macbook M1 Pro 2021 on MacOS Monterey 12.0.1 and Isadora 3.1.1

Let me know if you may have an idea of what is happening..

Thanks !

DusX

@sanza

Have you tried adjusting the Max Packets in the Isadora Preferences, Midi/Net panel?

At what speed are these values coming in/out?

Would you be able to combine values? That may reduce the number of packets received, which might help.

Sanza

hi @dusx

I tried to put the Max Packets at the maximum (9999) and Isadora quit like before.
For the past hour I put this at 250 and it didn't quit (yet).

I'm receiving OSC at 4210/sec (around 160Hz), I'm not sure how I can see the speed of my out values to Live.

I might be able to "ignore" some values coming in that I don't use in my Isadora program. Would it help or it doesn't change anything ?

thanks

mark

@sanza said:

I'm receiving OSC at 4210/sec (around 160Hz), I'm not sure how I can see the speed of my out values to Live.

Hi there, it's Mark, creator of Isadora here.

First of all, please add your configuration to your signature line as described in this post. We don't know if you're on Mac or Windows, what version of the operating system you're using, and what version of Isadora you're using. These help us to give you better answers when you ask questions.

That said...

So you're receiving 200 OSC packets at 160 Hz, is that right?

What is in each OSC packet? A floating point or integer number? Or?

What is the source of these packets -- is it something we can also use so we can make a test on our end?

In any case, if you're receiving 200 packets per second at 160 Hz, that means you're receiving 32000 packets per second. If Isadora has to manipulate each of those packets, it could get behind and – eventually – that means the buffer will overflow which could be a source of the crash. (It should fail gracefully in this case by simply dropping the packets but I can imagine situations where it might not do so.) It would be good to see your patch so we can analyze it and see if there are an inefficiencies that could be removed. If you're not willing to the patch here, then open a ticket and send it to us privately.

Best Wishes,
Mark