-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong instruments #3
Comments
This problem of all branches except |
Can you explain the problem w/ a bit more detail -- what are you doing and what instruments load instead? The branches work fine for me. Thanks! |
I modified The instruments and tempo are wrong. For example, instead of Have you tried |
I definitely know PASSPORT.MID (I'm old -- I remember when it was new) -- can you paste the midicube code you are using to load it and playback. It is also possible that there is a 1-based GM instrument encoding going on and each of the instruments is off by one? This is a problem in a lot of very old MIDI files which used 1-127 instead of 0-127. |
None of the instrument numbering/playing code has changed since MIDI.js -- that was not the reason for the fork, only to maintain the system. Note that none of MIDI.js or midicube (here) were optimized for midi-file playing - so there are lots of MIDI features (modulations, sysex, etc.) that don't work on MIDI.js -- one of the key features was just receive-MIDI note -> play MIDI note. |
That version of The modification is that it has |
When I tried
midicube
as well as https://github.com/gleitz/MIDI.js in December or earlier, they played wrong instruments for some (many?) MIDI files that have several instruments. Did recent commits fix this?This problem isn't present in the
abcjs
branch of the originalMIDI.js
.The text was updated successfully, but these errors were encountered: