Hi,

I have a Raspberry Pi connected to a lot of buttons, encoders, and a display.
Initially, I planned to communicate using OSC messages, but I’m running into a bottleneck very quickly.

For example, I have 16 buttons for a step sequencer, and I need to send an OSC message for each step to briefly turn a button’s light on, and then another message a few milliseconds later to turn it off again, so I can show the current step position. Basically a running light through the steps. That alone seems to overload OSC, depending on the tempo of my sequencer.

I could probably optimise this better, but I’m a bit shocked at how quickly I can overload OSC messages. There’s much more I still need to send, for example my encoders would also send many messages within milliseconds, and there are multiple encoders running at once.

I just read about using stdin and stdout for communication. I don't have any experience with it though. Would that work better in my case, or is it still better to stick with OSC and try to optimise it as much as possible?
Or are there any other/better ideas?

@impression You are running this on an RPI so have a look at this thread... https://scsynth.org/t/limit-to-maximum-number-of-osc-messages-that-can-be-received-in-short-time/8641/6
The sysctl command will probably help.
David.

Hey David,

Thanks a lot. Funny enough, I actually switched to SuperCollider recently, and I'm having those issues actually mainly in SuperCollider.

But for some reason I can't get access to the SuperCollider forum, I've been waiting for the administrator’s approval for days.

But I'm glad to hear that it seem a general problem with the UDP messages, I will try if changing the buffer can fix it.

Thanks again!