-
Notifications
You must be signed in to change notification settings - Fork 3
WebMIDI integration #25
Comments
The problem is that, as you mentioned in this issue: WebAudio/web-midi-api#45 New OSs make users jump through hoops to open a virtual MIDI port. It's a usability disaster. So I found this which opens virtual ports: https://github.com/justinlatimer/node-midi But it has no synths, obviously. I'm trying to put the puzzle pieces together here, can you help? node-midi seems unable to create a real virtual output port! Does yours? |
https://github.com/notator/residentSf2Synth contains the code for a synth that should work for you. All you have to do is include the code for the synth on your website [1], load it with the soundfont of choice, and then send it MIDI messages. You'll have to construct those by reading the .mid file of course. The Resident Sf2 Synth works fine [2], but its by no means perfect. See the issues in its repo. Think of it like this: Your app is the host. The synth itself implements the API for Web MIDI output devices, so you don't need the browser's implementation of the Web MIDI API, and you don't need to call [1] for an example of how to do that, see |
thanks! |
Please let me know here if you get it working. Thanks. |
@notator absolutely, although, we may go the Timidity++ route. |
We're working on a way to build web app which takes a
.mid
file and basically just "plays" it in a variety of soundfonts.This repo makes use of
new AudioContext()
but notnavigator.requestMidiAccess
.Is there a way your "synth host" can be hooked up to, say, a midi file reader like this? https://github.com/nfroidure/MIDIPlayer
The text was updated successfully, but these errors were encountered: