Skip to content
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

Open
charlieroberts opened this issue Jul 7, 2014 · 6 comments
Open

add MIDI support for Chrome #14

charlieroberts opened this issue Jul 7, 2014 · 6 comments
Assignees

Comments

@charlieroberts
Copy link
Collaborator

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

@charlieroberts
Copy link
Collaborator Author

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.

@diegodorado
Copy link

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

@charlieroberts
Copy link
Collaborator Author

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

@diegodorado
Copy link

diegodorado commented Jun 13, 2017 via email

@charlieroberts
Copy link
Collaborator Author

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!

@diegodorado
Copy link

diegodorado commented Jun 16, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants