-
**Describe the bug**
If I send a 1byte/2bytes length System Exclusive Continue message in MT3 format, output wrong conversion results.
**To Reproduce**
1.Set the Roland UM-ONE mk2 to class-compliant …
-
Hi,
I read all you nice documentation about the sysex on Arturia (I own Keylab Essentials from Arturia) but I have a question about creating the sysex data message. Your documentation is very nice …
-
### Bug Description
When my script sends multiple MIDI sysex messages in quick succession, it often makes Mixxx trigger an assert;
```
[Controller] fatal /usr/include/qt6/QtCore/qhash.h:790 ASSE…
-
Due to the fact that a MIDIPort object can outlive a MIDIAccess object, we could have ports that are created, but whether or not they support sysex is opaque unless you actively open and call send on …
qdot updated
17 hours ago
-
Some MIDI devices regularly send the active sensing message 0xFE after some fraction of a second without other messages on the bus to indicate that they are still present on the bus. This causes any p…
-
Hi @gbevin! Amazing work with ShowMIDI – immediately became my go-to tool for visualizing MIDI.
Here's an idea I've had for a while – it might be useful in certain situations to be able to translat…
-
Ok so sorry for the barrage of issues, I've been meaning to log these and never got around to it. It appears that something has changed in the handling of longer sysex messages so that they are not be…
-
MIDI-CI messages are backwards compatible with MIDI v1. Technically they are just System Exclusive messages. But they follow a strict protocol just like any other regular MIDI message.
I think it's…
-
Hello!
Actually I don't know if this is a bug or it is something that I ignore about sysex messages, but my problem is when I try to send a sysex message using the sender of the library it works very…
-
The encoder IDs of Bank2 and Bank3 are unknown yet. If you can, please try to modify one and copy the output of the MIDI console of the MIDI Control Center (View/Midi Console).