Closed rikner closed 9 years ago
I also discovered this problem on Windows. Maybe it's an issue with Chrome. Since I'm really not sure yet, where the problem is, I will close this issue.
I got the same error while using the virtual piano "Midi Keys" at line 1236 : info = instance.MidiInInfo(name);
If i use a "real" midikeyboard everything works fine.
Sascha, what is the virtual piano "Midi Keys"? Can you please give a link? Would like to test...
Hi,
here is the link:
http://www.manyetas.com/creed/midikeys.html http://www.manyetas.com/creed/midikeys.html
i am using these tool for some testing purposes.
Greetings
Sascha
Am 20.05.2015 um 14:35 schrieb Sema notifications@github.com:
Sascha, what is the virtual piano "Midi Keys"? Can you please give a link? Would like to test...
— Reply to this email directly or view it on GitHub https://github.com/cwilso/WebMIDIAPIShim/issues/59#issuecomment-103866405.
I just tested the update from Jan 15, 2015 with my web app and the Jazz plugin 1.4 on Mac OSX Yosemite.
Before the update, requestMidiAccess() based on the shim and the Jazz plugin worked without problems. When activating the chrome flag for web midi, the native implementation was used. I just had to differentiate between the input-iterator (native) and the input-array (shim) in my code. So everything was fine.
Now with the update, the native web midi still works fine with my code, but if turn native web midi off and try to run requestMidiAccess() with the shim, the jazz-plugin crashes immediately with following error:
I can restart the plugin and reload the page, but the next time I try to do requestMidiAccess() it fails again.
This happened to me in all three browsers (Chrome, Firefox, Safari). I re-installed the Jazz plugin but it didn't solve the problem. So is this some kind if compatibility problem with the OSX version of the Jazz plugin?