-
Right now, all MIDI message are sent to the configured grid midi device.
We could add a new node parameter that allows to choose the midi device per node, with the grid one being the default.
-
**Describe the bug**
Sending messages from MME MIDI app to midi monitor causes Green Screen on the USB MIDI 2.0 driver and loopback device
This issue only occurs if the device is running with the USB …
-
**Describe the bug**
When a device sends a Function Block Notification request, after the initial enumeration process after insertion of the device, the Windows MIDI service does not seems to process …
-
**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 …
-
**Describe the bug**
If I send a 1-byte length System Exclusive Start message (F0 xx) in MT3 format, MIDI Service gets stuck.
If this happens, MidiSrv cannot be stopped and restarting OS is required.
…
-
Currently the list of MIDI devices is sorted alphabetically.
It would be nice if you would be able to reorder the device list. This way you could display devices which are most interesting first, b…
-
### Port, board and/or hardware
rp2 port, pico 2 board
### MicroPython version
MicroPython v1.24.0 on 2024-10-25; Raspberry Pi Pico2 with RP2350
### Reproduction
This is the script I us…
-
**Describe the bug**
A legacy MIDI app which uses MME MIDI API cannot receive System Exclusive messages through a MidiSrv enumerated port.
**To Reproduce**
1. Load [the attached firmware](https://git…
-
**Describe the bug**
MME MIDI app receives wrong data when sending MIDI 2.0 data.
This was found by a compatible test of MIDI 2.0 message to MIDI 1.0 message conversion.
**To Reproduce**
1. Set the …
-
System- Windows 10-22H2 Build, AMD 8 core 3.6 Gig, 24 G ram, standard sound card,
MIDI device Alesis Q61
Chrome Browser
Hello need some advice. I have set up your program, and I have been try…
xstek updated
2 weeks ago