magnusson
Joined 14 years ago
Karma
123
Submissions
26
Member since
Oct 18
Recent submissions
Comment · 10 years ago
Comment · 11 years ago
I implemented local caching for all the API calls, so it shouldn't be exceeding the rate limit as much now, plus load times should generally be quicker.
Comment · 11 years ago
FYI for anyone still coming in, this has been up and down all day due to the fact that Uber's API is rate limited to 1000 requests/hour. I contacted support and asked for an increase but they haven't gotten back to me yet. So if you want to see it and it's not working, check back on the next hour. Sorry about that and thanks for looking!
Comment · 11 years ago
Yes! Tis truly an exciting time to be playing synthesizers on the web!
Comment · 11 years ago
Hm, yeah, that would be a cool thing to publish separately. The MIDI mapping code is pretty much isolated to these two objects [1] [2], but I'd have to do a little thinking about how people would want to use it, and separating it from Backbone would take some work.
[1] https://github.com/stevengoldberg/juno106/blob/master/js/vie...
[2] https://github.com/stevengoldberg/juno106/blob/master/js/mod...
Comment · 11 years ago
Very cool, thanks for sharing!
Comment · 11 years ago
Well, the real 106 doesn't have an arpeggiator either (without mods anyway) -- only the 6/60 do. I don't think it'd be too hard to implement one though, so I may do that soon.
Comment · 11 years ago
If you have links to other websynths with similar "MIDI learn" functionality, I'd love to see them!
Comment · 11 years ago
Ha, thank you Paul! Glad to know it's probably not my fault ;)
Comment · 11 years ago
There are lots of websynths that respond to MIDI note messages, and I've seen some that respond to CCs as well -- e.g. the midi-synth [1] by Chris Wilson (editor of the WebAudio and WebMIDI specs) -- but in that case, the CC messages are hardcoded to the UI. (It also doesn't support 14-bit messages.)
In 106.js, every UI control is arbitrarily assignable to any MIDI CC message, so you can map it to your device however you like. That's a feature I'm used to ("MIDI learn") from desktop DAWs, but haven't seen in any other websynths yet.
You won't be able to see the UI for this feature at all unless you've got a MIDI controller plugged in, though.
Comment · 11 years ago
In Firefox the envelope release is broken, and overall performance seems worse compared to Chrome, for reasons I haven't really bothered to investigate deeply. It mostly works in Safari, but Safari does something different with garbage collection of audio nodes, so the note-stealing behavior doesn't work right.
Basically, use Chrome for now if you want it to play nice. WebMIDI is only supported in Chrome anyhow.
Also, 100% agreed on TAL U-NO-LX, it's one of my favorite plug-ins and the price is great!
Comment · 11 years ago
Re the 0-127 range, you may be familiar with this, but many devices are capable of sending 14-bit MIDI messages by combining 2 different MIDI CCs, allowing for much finer control. 106.js supports both 7 and 14-bit messages.
I've been using redux-form in large production app, btw, and have mostly found it nice, but am looking forward to migrating to the new version.