submo

I'll try to ignore DIN MIDI stuff... however: With the current code (Teensyduino 1.60) in usb_midi.c there is the following problem: If you (by mistake or for bug-finding purposes) send a SysEx without terminating 0xF7 then the data gets added...

This is one of the main problems currently with the Default Teensy (Arduino) Midi Library. If a SysEx message is started with 0xF0, but doesn't receive a subsequent 0xF7 (due to an error of some sort) the Midi Library will get 'stuck' in a SysEx...

Just gave this a test and I'm seeing the same sort of thing. I was only able to send/receive SysEx messages (via a physical loopback cable) of about 110 bytes before it started to skip data. For example when sending a SysEx message of 238...

In that case it may help to post your MIDI library code, or maybe just have a look how the default Midi library sends SysEx. Sending SysEx (from usbMIDI for example) using the default Teensy (Arduino) Midi library is sent a byte at a time (no...

What Midi (Din) library are you using? The default Midi Library (included with Teensy) also has a SysEx buffer limit which you may need to increase (I think default is 128).

Other option would be roll back to teensyduino 1.59 untill a fix is in place.

Looks like a small error (for Teensy2 only) has slipped through in the new teensyduino release caused by this new fix. I'm sure @PaulStoffregen will fix this in an upcoming release, but for now you will need to locate the usb_api.cpp file...

I just hope that MIDI 1.0 will continue to be supported. I have lots of hardware using good old midi that just work. Also I have my own projects that I use good old MIDI and 127 different values per potentiometer is more than enough (can't move...

If I'm doing something with the input (like in your example) I will always use 'if'. I only ever use 'while' if I don't care about the Input, or I'm at risk of filling up the USB input buffer quicker than I can read it (which hasn't happened...

Glad you have a solution. It still doesn't sit right with me that Midi devices can work at High Speed on other Android devices, but not on the Pixel. I'd be interested to see if you can get anything to work at High Speed USB on the Pixel. Maybe...

Hello, I tried default 'MIDI' usb descriptors (no audio interface, with seremu) on a Samsung Galaxy A05s, and Samsung Galaxy A53, and they both pick up the Teensy fine (these are budget Android phones). I'm a little doubtful, and would be...

Did you try that .hex file I linked in my previous post on your Teensy 4, to see if it works on your Pixel 7?

Theres a single port version of the InputRead example hex file here (for Teensy4): https://drive.google.com/file/d/1HCal_8rfHvAqsPXFsmQI_hroNtgQHezU/view?usp=sharing I checked with TDD and it 'should' be a 'pure' Midi device, with the...

The easiest way I found to get rid of Seremu without causing issues elsewhere was this... In usb_desc.h find the Midi USB type you want and put another #define in there, think I used SEREMU_ENABLE or something like that. Then in usb_desc.c...

Hello, I just uploaded the Midi Interface_3x3 Teensy Example with the USB Type set to "MIDI 4" to my Teensy4, plugged the Teensy into my phone (Using a USB C OTG adapter on a OnePlus Nord2) and Android can see it. I went to this site via Chrome...