-
Notifications
You must be signed in to change notification settings - Fork 26
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
Teensy MIDI device not recognized by ansible #63
Comments
Midi debug session w
at which point ansible becomes unresponsive. It does this consistently. Any suggestions? EDIT: FWIW - linux lsusb -v shows this corresponding info for those last few strings:
so it seems to be barfing on the HID interface? |
As an experiment you might try removing the It could be that the code for the HID interface does something bad or is incomplete and this is just the first time someone has plugged in a HID capable device (and reported a problem). |
shouldn't in theory cause issues as HID is used by teletype (and polyearthsea/multipass), but i wonder if this is because the device reports itself as both HID and MIDI. |
Some followup testing.
additional debug in
If I comment out UHI_HID in
However, MIDI does not finish and midi from the teensy device is not received. |
A bit more testing... Tried testing with Polyearthsea on Meadowphysics and errors are the same (with UHI_HID still active). However - with whatever is different in @scanner-darkly's version of libavr32 - it does not crash the module. It keeps working ok if I remove the teensy and plug something else in. But still no midi from the teensy. |
Testing again with most recent libavr32 updates. results:
Going to add some debug again and see if I can track this down further |
Further testing and a breakthru... Digging around in uhi_midi.c What seems to be happening is this.... as the bInterfaceClass's are being evaluated, So... as a test at line 166 I added the following to break out of the loop if it hits an HID
This seems to fix my problem - it finishes the midi install process and I get So then... Is my fix a good solution, or is there a better way to fix this? EDIT - I have also commented out |
Tried testing my TeensyLC based usbmidi host-to-host adapter with ansible tonight. Hoping to be able to get this working for norns->anisble midi communication.
So... Ansible crashes (becomes unresponsive) when this device is plugged in and requires power cycling to get it back. I tried grid and other working midi devices)
Notes:
Wanted to log this while it's fresh in my mind. Will update with debug once I can get things compiled with UHI_MIDI_PRINT_DBG turned on.
Also need to test with other Teensy variants (3.2/3.6) to see if they also do this.
The text was updated successfully, but these errors were encountered: