Deprecated, please Chris Wilson’s WebMIDIAPI Shim
As developers started to use the midi-to-flash bridge i realized that the organization of code was not flexible enough. So i rearranged the code rather drastically. The code is now split up into two pieces: the midi bridge and the midi client. The midi bridge comprises 3 parts:
- a Java applet that receives the midi data from your system
- some JavaScript code that enables 2-way communication between Java and Flash
- a small Flash application that broadcasts the midi data to other Flash applications thru a LocalConnection
See the generated asdocs.
This is a sample of a midi bridge. You can set the bridge id and select the midi device that you want to connect to the midi bridge. These parameters can also be set as flashvars in the containing html file.
You can run multiple instances of a midi bridge at the same time, and you can connect each instance to different midi device.
Because a midi client receives midi data thru a LocalConnection it can be any type of Flash application: a swf running in a browser or in a standalone player, a projector or an AIR application.