halfradaition

Firefox 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.

dezgeg is correct, MIDI has no hardware flow control pins. The synth's serial receiver chokes because the 8-bit CPU takes too long to write the SysEx buffer to SRAM.

It's fascinating how easy it is to overwhelm older hardware stacks with broadcast/flooding traffic that modern systems wouldn't notice!

Haha, sometimes one or two keyboards quickly turns into one or two bedrooms anyway! Appreciate the feedback on the copy.

I wrote the entire parser by hand to read Yamaha DX7 SysEx bytes, no AI generation here! Thanks for sharing SoundPalette, looks like a great reference

Absolutely. Your data belongs to you, we fully support standard .syx exporting at all times. Pricing is definitely getting a rework for solo producers.

Hear you loud and clear. The pricing was originally framed for commercial studios.

Brilliant suggestion. I'll test scheduling directly on the Web MIDI API thread to keep JS main thread timers out of the equation.

Fair point. We went web-first to bypass driver installation hell, but a local Tauri app for offline-first use is on the roadmap.

That's usually caused by cheap controller firmware flooding the connection with continuous Active Sensing signals (0xFE bytes every 300ms) or noisy clock jitter.

We just throttle the Web MIDI stream in JS with 100ms pauses between packets so the 8-bit CPU doesn't choke.

basically the icloud for vintage synthetizers