-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add MIDI support for Chrome #14
Comments
This has been fleshed out significantly: http://gibber.mat.ucsb.edu/?path=charlie/MIDI_demo Unless there are complaints this is probably the API I'll include in Gibber. |
I have also tested with midi within chrome, and I find it very interesting. I am able to interact from gibber with hardware synths... it would be awesome to easily target a seq to a midi outport....if someone en light me a little on this matter, or where to look to copy another implementation, i would happily create a pull request for this |
Hi Diego, Please checkout gibberwocky.cc/midi... it's basically a MIDI-specific implementation of Gibber with some extra features. Also: https://github.com/gibber-cc/gibberwocky.midi Let me know how it goes! - Charlie |
Excellent work!although I'd love to use it within gibber to take advantange
of all the goodness.
Thank you!
|
Yes, it'd be nice to be able use gibber sounds and MIDI at the same time (or graphics + MIDI). Unfortunately the way sequencing works in Gibber the timing for MIDI is really unreliable (gibberwocky is really good though). It's going to take some work to reconcile the different scheduling approaches. Ideally, you'd be able to sequence Gibber sounds / MIDI / Max messages / Ableton messages etc. all from the same interface and the same clock. That would be really fun! |
That would be awesome! count on me to help in that direction!
|
Add MIDI support for Chrome that takes advantage, when possible, of Gibber's continuous mapping abstractions. MIDI support seems fairly simple... as a test see:
http://gibber.mat.ucsb.edu/?path=charlie/simple_midi
The text was updated successfully, but these errors were encountered: