How do you keep Web MIDI from crashing a 1983 synthesizer?

Discussion (8 Comments)Read Original on HackerNews

_def•about 1 hour ago

tangent/feedback about the product: replacing abandoned desktop apps with a webapp with unknown future does not exactly excite me. Bundle this as a desktop app that works offline-first and you'll pique more interest.

nl•22 minutes ago

Strong disagree!

Zero install is a huge feature both to reduce friction and to save local storage. I don't want to install yet another synth I'll use twice a year.

gbanfalvi•8 minutes ago

You can offer standalone exes without installers.

halfradaition•27 minutes ago

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

sargstuff•2 days ago

Nice retro-demo/motivation for "what's the point of protocols/abstraction layers"[0].

Use case argument for an add-on programmable logic array / micro controller board as security interface / non-standard to standard protocol translation.

----------------------------------------------------------------------------------

[0] : https://www.terryewell.com/m116/Docs/historyMIDI.pdf

halfradaition•about 22 hours ago

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

Macha•about 3 hours ago

I had the opposite problem where using my (recent-ish) cheap midi keyboard with WebMidi was crashing Firefox.

halfradaition•about 3 hours 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.

How do you keep Web MIDI from crashing a 1983 synthesizer?

⚡ Community Insights

Discussion (8 Comments)Read Original on HackerNews