[BUG] UDP Socket Bottleneck / OSC Messages Not All Being Recognized

[justindube1987]

Make sure you're on the latest stable or beta build of both Companion and the module

• I have tested this on the latest stable or beta release

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Requesting a way to break up the OSC receive message at connection. The second half of the ~5,000 messages are being ignored and not updating the module variables.

Steps To Reproduce

1. Run the module
2. Check Logs and module variables
3. See that only the first half of variables get updated because the second half of the UDP OSC messages don't make it through (on my computer, at least)

Expected Behavior

All OSC messages for (channel/aux/main/mtx) strip names, sends, mutes, etc, should be received by the module.

Environment (please complete the following information)

- OS: Windows 10 Home
- Browser: Chrome 143.0.7499.170 (Official Build) (64-bit)
- Companion Version: v4.99.0+8573
- Module Version: 2.2.0
- WING Firmware Version: 3.1
- WING Model: Compact

Additional context

No response

[janikwitzig]

We could not send all commands at the same time. My suggestion is to collect all variable request and insert a short break after every N-th request. In total there will be ceil(varCount / N) such request bundles. After each bundle we can wait for some time (10-50ms?).