4 ms·
That's usually caused by cheap controller firmware flooding the connection with continuous Active Sensing signals (0xFE bytes every 300ms) or noisy clock jitter
by halfradaition 3mo ago
That's usually caused by cheap controller firmware flooding the connection with continuous Active Sensing signals (0xFE bytes every 300ms) or noisy clock jitter.
- im3w1l 3mo agoThat's one way to look at it, but imo firefox shouldnt crash no matter how malformed the data is.
- tgv 3mo agoAlso, the sensing command is one byte per 300ms. That's irritating when you have to deal with it personally in real time, but for a modern computer, that's peanuts.
- halfradaition 3mo agoFirefox shouldn't crash indeed. The crash was usually due to a memory leak in the browser's Web MIDI implementation when handling constant stream disconnects/reconnects.