It's an issue we've discussed before, but would love to re-ignite the conversation on. In our testing, we find that Isadora will "drop" OSC packets from being received if we transmit them at a cadence more frequent than 100ms. This occurs in patches with extremely low LOAD, with no video processing, and with framerate and general service task set to their maximum options. This is an issue because while certain faders, sensors, etc. may be OK to interact with in a lossy way, ZoomOSC/ISO are sending discrete and unique data packets. For example, less than 100ms of delay when receiving our ../list output causes entire zoom participants to be dropped from the corresponding Isadora database.
Could we continue the conversation on figuring out how to buffer and play out these OSC packets when needed, so that we can increase the speed and reliability of the connection between the ZoomOSC API and Isadora? While small audiences are OK to transmit with the 100ms delay we offer as an option in ZoomOSC, if you have a large database of participants, it can take several minutes for Isadora to build its internal database of participant data.
Thanks!