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.
[dead]
How do you keep Web MIDI from crashing a 1983 synthesizer?
41–49 of 49 posts
Re: How do you keep Web MIDI from crashing a 1983 synthesizer?
#42US$ 20/month for a SysEx librarian backup? Or US$ 599 for a "lifetime" license of a solution that mostly depends on this company existing to keep the precious backups? That'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 s…
Knob Monster runs on a serverless architecture, the monthly operating costs are near zero, meaning we can (and will) keep the servers alive indefinitely without commercial pressure.
Re: How do you keep Web MIDI from crashing a 1983 synthesizer?
#43[deleted]
Re: How do you keep Web MIDI from crashing a 1983 synthesizer?
#44[deleted]
Re: How do you keep Web MIDI from crashing a 1983 synthesizer?
#45Hear you all loud and clear. The pricing critique was a massive blind spot on my end.
* New Pricing: A single $39 one-time payment for lifetime access (called knob.monster+).
Re: How do you keep Web MIDI from crashing a 1983 synthesizer?
#46Earlier quoted context omitted.
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.
A long forgotten feature of desktop OS, incredible how knowledge goes lost within a lifetime.
By zero install I mean I don't want an executable on my computer. I want it transient - available when I use it, but removed when I don't.
Re: How do you keep Web MIDI from crashing a 1983 synthesizer?
#47Earlier quoted context omitted.
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.
You can offer standalone exes without installers.
By zero install I mean I don't want an executable on my computer. I want it transient - available when I use it, but removed when I don't.
Re: How do you keep Web MIDI from crashing a 1983 synthesizer?
#48Earlier quoted context omitted.
A long forgotten feature of desktop OS, incredible how knowledge goes lost within a lifetime.
By zero install I mean I don't want an executable on my computer. I want it transient - available when I use it, but removed when I don't.
Easy, place it on a memory mapped volume, or shared drive mapped on request.
There are other means, as mentioned a forgotten art.
Re: How do you keep Web MIDI from crashing a 1983 synthesizer?
#49The Web MIDI API[0] used by the author has a built-in precise scheduler, that has higher precision and works better than the unreliable setTimeout approach used by OP when coupled with the Performance API[1]. Pass a timestamp as the second argument to midiOutput.send(data, timestamp), calculated with performance.now. Something like midiOutput.send(data, performance.now() + offset) 0: https://developer.mozilla.org/en-…
Brilliant suggestion. I'll test scheduling directly on the Web MIDI API thread to keep JS main thread timers out of the equation.
Glad it helped! A little credit on the post would go a long way :)