-
Continuing #1475.
SysEx strings, at least 32 bytes long, are required by any GM/GS/XG/GM2-compliant MIDI event sources/targets, most of them vital for the compliant sources/targets to work properly…
-
Right now sysex messages are treated as MetaEvents which are prefixed by 0xFF, but it looks like SysEx events don't require this prefix either in realtime or in midi files.
I believe this can be fi…
-
I know holding FROM TAPE and hit PROGRAM 6 dumps ALL presets (which is very nice because this wasn't possible before), but I want to dump the current program bank only (by holding RECORD and hit PROGR…
-
If I understand the sysex message format its lead-in is 0xF0 followed by an arbitrary number of bytes ending in a final 0xF7. Bit 8 may never be set in the payload, which means they have to be less th…
-
According to the [RtMidi Tutorial](https://www.music.mcgill.ca/~gary/rtmidi/index.html#windowsds), RtMidi supports sysex messages with a maximum size of 1024 bytes. All larger messages are discarded.
…
-
This is for SysEx
-
Seems like it's possible to trip up the MidiHandler with certain SysEx data
Reported on slack:
> So I've just found that the following midi message will freeze the libdaisy midi handler but no…
-
I'm using `amidi --send-hex` to send data to a Commodore 64 via a CLab MIDI interface. The problem is that even with 100 bytes the probability of a buffer overrun is about 30%. I didn't find a way to …
-
A potential memory leak issue was [reported](https://github.com/djipco/webmidi/discussions/426) to me by a user of the WEBMIDI.js library. This library uses `jzz` in the Node.js environment to emulate…
-
Hello there, thanks for those insights, I will certainly build a real editor with a nice GUI someday
anyway, as a side note, it would be nice to add the following:
for the MPK261 there are 4 MIDI …