Earlier quoted context omitted.
That's usually caused by cheap controller firmware flooding the connection with continuous Active Sensing signals (0xFE bytes every 300ms) or noisy clock jitter.
That's one way to look at it, but imo firefox shouldnt crash no matter how malformed the data is.
How do you keep Web MIDI from crashing a 1983 synthesizer?
21–30 of 49 posts
Re: How do you keep Web MIDI from crashing a 1983 synthesizer?
#22tangent/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.
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.
Re: How do you keep Web MIDI from crashing a 1983 synthesizer?
#23Because the competition is free. There's a free DX7 plugin (https://asb2m10.github.io/dexed/) that includes a librarian, and there's a paid one (https://www.plogue.com/products/chipsynth-ops7.html; outstanding emulation) that also has a librarian (that I have personally used on a mac).
Re: How do you keep Web MIDI from crashing a 1983 synthesizer?
#24Re: How do you keep Web MIDI from crashing a 1983 synthesizer?
#25I have only messed with midi virtually so don't know much beyond the bit packing. But when you go to actual hardware and cables is there not a rigid speed it should be running at. 30Kbaud or something. That is, why is the interface running too fast and crashing the synth? the synth(no matter how old and limited) should handle the specified 30Kbaud stream all day long.
The reason this doesn't work is that USB adapters don't have those pins, and thus assume you can send it at 30kbaud - not respecting when the device says it must pause sending data.
By introducing a static flow rate below what the CPU can handle, it should theoretically keep the flow rate below the threshold that the CPU starts to choke at
Re: How do you keep Web MIDI from crashing a 1983 synthesizer?
#26tangent/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.
Yeah, and I'm certainly not paying $20 a month - indefinitely - for it.
Re: How do you keep Web MIDI from crashing a 1983 synthesizer?
#27That's more money than a fully fleshed out DAW like Ableton Live, Bitwig, Logic, etc.
> Every vintage synthesizer is a ticking time bomb. The soldered internal battery will die, erasing every custom patch you have ever made. Secure your irreplaceable sounds before your hardware turns silent.
The marketing copy is also really obnoxious to try to sell this solution. Yeah, induce fear to try to convince someone to pay a quite hefty amount of money for saving vintage synths patches.
I really don't understand the direction of this product, and I'm very much its audience/market...
Re: How do you keep Web MIDI from crashing a 1983 synthesizer?
#28I have only messed with midi virtually so don't know much beyond the bit packing. But when you go to actual hardware and cables is there not a rigid speed it should be running at. 30Kbaud or something. That is, why is the interface running too fast and crashing the synth? the synth(no matter how old and limited) should handle the specified 30Kbaud stream all day long.
Not necessarily. The RTS/CTS pins on the serial port are there for the device to tell the host "stop sending data, I need to process the data already sent" The reason this doesn't work is that USB adapters don't have those pins, and thus assume you can send it at 30kbaud - not respecting when the device says it must pause sending data. By introducing a static flow rate below what the CPU can handle, it should theoret…
Re: How do you keep Web MIDI from crashing a 1983 synthesizer?
#29Earlier quoted context omitted.
Not necessarily. The RTS/CTS pins on the serial port are there for the device to tell the host "stop sending data, I need to process the data already sent" The reason this doesn't work is that USB adapters don't have those pins, and thus assume you can send it at 30kbaud - not respecting when the device says it must pause sending data. By introducing a static flow rate below what the CPU can handle, it should theoret…
MIDI doesn't have RTS/CTS pins...
Re: How do you keep Web MIDI from crashing a 1983 synthesizer?
#30Earlier quoted context omitted.
Not necessarily. The RTS/CTS pins on the serial port are there for the device to tell the host "stop sending data, I need to process the data already sent" The reason this doesn't work is that USB adapters don't have those pins, and thus assume you can send it at 30kbaud - not respecting when the device says it must pause sending data. By introducing a static flow rate below what the CPU can handle, it should theoret…
MIDI doesn't have RTS/CTS pins...