-
Notifications
You must be signed in to change notification settings - Fork 504
Add MIDIUSB-compatible library #3194
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
Conversation
ddc7d82
to
002004c
Compare
Runs arduino_midi_library and MIDIUSB native applications on the RP2040 and RP2350 over USB
002004c
to
855ed65
Compare
Thank you so much for this! I'll test it out when my current projects allow it! |
Cool, thanks. Do open up something with detailed info on reproducing if there's something amiss. I tried the MIDIUSB native output examples and the arduino_midi_library ones and they seemed to play fine when I cut-n-pasted the magic |
Ok, I did a (no so ) quick try, and I'm missed something:
But the library IS a fork of MIDIUSB and there is no "USBMIDI_CREATE_DEFAULT_INSTANCE()"? There are TOO many MIDI/ USB MIDI libraries/forks into the wild, so there is no way getting the "right" one. Ok, mostly I get this error message:
So I'm pretty sure, that I missed one (or more?) dependency /ies ? Thank you :) regards Matthias |
Ah, I am not the only one who can't figure out what MIDI library is the right one! 😆 Anyway, the examples in the core itself build and run (as part of CI, in fact) under MIDIUSB. I also then used arduino_midi_library needs an add'l library to support USB transport. By default a_m_l only has UART-MIDI since that's the lowest common denominator on boards: I hooked up both libs' SinpleSynth modified to use a PWMAudio output so I could just plug in my earbud and verify. Used Re: the compile error, you seem to be building the generic MBED MIDIUSB ( |
ok, I think there are some quirks: I completely deleted your RP2040 core, get rid of all Cache and "staging" files (packages and libraries), reinstalled it via Same results as before:
|
Well, you've gotten rid of the /home/xxx/Arduino/libraries/MIDIUSB which is good, but you're not running the version with MIDI support turned on. I have not done an official release w/the change yet, so you need to use the |
ROFL - The dumbest possible mistake on my part? |
Ok, enough for today, after struggling 2 hours around with GIT (especially python!!!!) under windows I got the git version running. Sadly the install manual for GIT won't work (for windows): https://github.com/earlephilhower/arduino-pico#installing-via-git Ok, it compiles now ok, MIDI IN is working (so I get DATA into the PICO), but no MIDI out (from PICO to PC) - no example would produce a MIDI out event - not even a simple loopback. |
Thanks for giving it a go. Windows makes everything hard, but FWIW There's a bunch of stuff you need to configure w/the OS before you can get a legit If you have the exact sketch and any options or apps/settings you used that would be helpful for the Pico-MIDI-out. There's a whole pile of stuff that it looks like you need to configure before getting any kind of MIDI-IN to the PC under Linux and I'm not sure where to start to confirm if the messages aren't being sent from the Pico, or they're being sent but in a wrong format, or the Pico is identifying in a wrong way, etc... |
I just found a simple tester and repro'd the MIDI-OUT issue. It was sending the packets using the wrong call. Using
|
(deleting all my text, because the error is found) :) |
Runs arduino_midi_library and MIDIUSB native applications on the RP2040 and RP2350 over USB