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
{{ message }}
This repository has been archived by the owner on May 16, 2023. It is now read-only.
Greetings! First, my gratitude for this great library. I tried several libraries for web MIDI and this is by far the most straightforward and usable that I've seen.
My setup seems to work but it's producing some warnings that I thought were worth reporting. I have two MIDI inputs that I'm listening to: a VMPK keyboard and a KORG-SP500 that hooks to my laptop with a MIDI-USB adapter.
Both of the inputs play sound in my browser, but when the KORG is connected I get these illegal message warnings in very quick succession. I'd be happy to drill in and gather more information for you, but I'm not sure what I'm looking for.
Thank you again for the great lib and for taking time to read through this issue.
The text was updated successfully, but these errors were encountered:
This appears to be an error originating from the midimessage dependency. Based on the midimessage source it seems that this message can be safely ignored.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Greetings! First, my gratitude for this great library. I tried several libraries for web MIDI and this is by far the most straightforward and usable that I've seen.
My setup seems to work but it's producing some warnings that I thought were worth reporting. I have two MIDI inputs that I'm listening to: a VMPK keyboard and a KORG-SP500 that hooks to my laptop with a MIDI-USB adapter.
Both of the inputs play sound in my browser, but when the KORG is connected I get these illegal message warnings in very quick succession. I'd be happy to drill in and gather more information for you, but I'm not sure what I'm looking for.
Thank you again for the great lib and for taking time to read through this issue.
The text was updated successfully, but these errors were encountered: