The latest version of Google’s Chrome browser, released earlier this week, has added support for hardware MIDI – meaning that you can now use your MIDI controllers to play web-based music software.
In Chrome 43, you can use MIDI hardware to create music, without installing any specialized software. The Web MIDI API lets websites communicate with connected MIDI devices.
In the video demo, via Paul Kinlan, a hardware controller is used to play a web-based virtual analog synthesizer. If you’re a Chrome user and have updated to version 43, you can try out Chris Wilson’s web-based software synth at the Web Audio Demos site or Steve Goldberg’s web Juno 106.
Check out 106.js, my new MIDI-enabled browser based Juno-106:
http://resistorsings.com/106/
Thanks for the tip – I updated the post.
This is very cool. Enjoyed that a lot! Wished I was at home with my studio to really hear it on good speakers!
nice!
works on my mac. midi keyboard needs to be plugged in BEFORE starting chrome.
If you are looking for a great sounding browser synth with MIDI, try: http://www.websynths.com
You can even live-code your synthesizers and play them in the browser. Check: http://modlfo.github.io/vult/demo.html
https://builtwith.angularjs.org/projects/hya.io/thumb.png
Take a look!
A complete DAW with MIDI on Chrome, totally developed in HTML5, CSS3 and Javascript:
http://app.hya.io/
Could you map buttons to open and close tabs though?
Yeah, you could map your MIDI controller to do anything you can do with JavaScript.
Chromebook could be useful for light music composing on the go 😀
I wonder if this is the first sign of an era of cloud based music creation environments.
Those would be available through a subscription business model, or via a pay per use basis…
all version of chrome?
article says,, Chrome 43…
I don’t understand this. Why is Google making bloatware out of Chrome? Shouldn’t this be better left as a plugin?
Don’t get me wrong… I’m a huge fan of new software for the studio and music-making in general… but if there was any question that Chrome was becoming bloatware, this answers it…