djipco / webmidi

Tame the Web MIDI API. Send and receive MIDI messages with ease. Control instruments with user-friendly functions (playNote, sendPitchBend, etc.). React to MIDI input with simple event listeners (noteon, pitchbend, controlchange, etc.).
Apache License 2.0
1.53k stars 115 forks source link

Work In Progress: Testing using web-midi-test #232

Open jjeff opened 2 years ago

jjeff commented 2 years ago

Work in progress...

jjeff commented 2 years ago

Okay. I think I've got all of the tests in place now. However, I think that this may have surfaced few bugs/problems/incompatibilities between the web-midi-test library and webmidi.

Some theories:

I don't know if these issues are problems with web-midi-test or with webmidi, but I'm guessing Jean-Philippe would have thoughts.

jjeff commented 2 years ago

Status of tests:

djipco commented 2 years ago

Thanks for your work on this Jeff. Unfortunately, as I mentioned in a prior message, I don't have much bandwidth to dedicate to this right now. Are you currently stuck?

jjeff commented 2 years ago

Thanks for your work on this Jeff. Unfortunately, as I mentioned in a prior message, I don't have much bandwidth to dedicate to this right now. Are you currently stuck?

Yeah. I think I'm stuck. Just trying to determine if these issues are a problem with WebMidi.js, web-midi-test, or (hopefully) something that can be adjusted in the test files.

It's mostly just down to the midiSrc.emit() and midiOutput.send(data, **timestamp**) problems. Details above.

I'll keep chipping away at these, but my progress is getting slower.

jjeff commented 2 years ago

I think I've found the timestamp problem and I've posted an issue for the web-midi-test project: https://github.com/jazz-soft/web-midi-test/issues/2

But now that I'm looking at the spec again, maybe this isn't the issue...