You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Web MIDI API changed once again, and as a result Flocking's MIDI support is not working in Chrome 43. This appears to be due to the fact that input ports need to be explicitly opened prior to being used, despite the Web MIDI spec clearly stating that attaching a MIDIMessageEvent listener should automatically open the port.
* 0.1.x:
Makes the Flocking website more responsive. Thanks to @abledaccess for the fixes.
Updates Node.js MIDI support to better reflect new port semantics.
Fixesgh-108: Explicitly opens MIDI ports prior to using them.
* master:
Updates release version to 0.1.2.
Fixesgh-107: Adds support for receiving clicks from multiple elements.
Fixesgh-109: Adds flock.enviro.start() method; deprecates play().
Makes the Flocking website more responsive. Thanks to @abledaccess for the fixes.
Updates Node.js MIDI support to better reflect new port semantics.
Fixesgh-108: Explicitly opens MIDI ports prior to using them.
Conflicts:
demos/audio-file-web-worker/html/audio-file-web-worker.html
dist/flocking-all.js
dist/flocking-all.min.js
dist/flocking-no-jquery.js
dist/flocking-no-jquery.min.js
docs/getting-started.md
docs/nodejs.md
flocking/flocking-core.js
The Web MIDI API changed once again, and as a result Flocking's MIDI support is not working in Chrome 43. This appears to be due to the fact that input ports need to be explicitly opened prior to being used, despite the Web MIDI spec clearly stating that attaching a MIDIMessageEvent listener should automatically open the port.
http://www.w3.org/TR/webmidi/#methods-1
The text was updated successfully, but these errors were encountered: