Bart De Lathouwer

@0ba-pia Was the above useful? See also franky47's note: https://github.com/FortySevenEffects/arduino_midi_library/issues/188#issuecomment-748511841

Leonardo uses `Serial1`, not `Serial `in the above example. Change to: `MIDI_CREATE_CUSTOM_INSTANCE(HardwareSerial, Serial1, MIDI, CustomBaudRate);` See also: https://github.com/FortySevenEffects/arduino_midi_library/blob/d9149d19df867abbf78cfcd37ef9d0e14dedca7f/src/serialMIDI.h#L105-L109 and https://github.com/FortySevenEffects/arduino_midi_library/issues/65

Should the USB part of this table be moved over to https://github.com/lathoub/Arduino-USBMIDI?

@UgaDaBuga Have you been able to test @YuuichiAkagawa library?

> > It just occurred to me that the other transports expect thru to be off by default, and I haven't tested any transport other than the baked-in serial. >...

Good [reading on Active Sensing](http://midi.teragonaudio.com/tech/midispec/sense.htm) Another [reading on impact of Active Sensing](https://www.popschoolmaastricht.nl/college_midi_activesensing.php) (in Dutch) > The load that Active Sensing would mean for your midi data is heavily overestimated by...

> The terminology for timeouts could be improved, it's not an error... I kinda agree, the naming for the handler `Error` came out of a Parsing error. In the case...

Just implemented the 'having it's own handler' and its memory neutral (balanced the additional bit checking code calling the error handler)

How do we call this thing? `using ActiveSensingTimeoutCallback = void (*)(bool active);` or `using ActiveSensingExceptionCallback = void (*)(bool timedOut);` ...

> false on timeout and true when stream resumes activity. Active Sensing tested (both receiver and sending)