Gadgetoid
commented
6 years ago I've just realised this when testing today- it's not actually sending MIDI over Serial at all, but is instead sending a string representation of it.
See: https://github.com/Microsoft/pxt-midi/blob/fb9de98860c6c5cd0a60844673f450f1bc55abbf/midi.ts#L80-L95
The practical upshot of this is that the "MIDI" is very human-readable, but unfortunately isn't readable by any off-the-shell Serial->MIDI bridge software I've come across.
The format is:
midi:<command>,<arg>,<arg> \r\n
(Not I've taken liberty with the amount of whitespace, but that is part of the output)
You could write your own client in Python that handles MIDI messages in this format and injects them directly into the system. It'd be relatively easy using serial.readline.
However I think this library needs a new block: "useRawSerial()"
This block would run the following code:
function send(data: Buffer): void {
serial.writeBuffer(data)
}
midi.setTransport(send);This writes the raw - not human readable - MIDI data directly out to the serial port, and I can confirm this works with Hairless MIDI <-> Serial Bridge.
JonahPi
pelikhan
CaptainCredible
I used the Midi package with a very simple program but was not able to get out any tone. Using a similar Python code worked perfectly fine. In both cases I transmit the Midi-code via Pin 0 and use the Midi via Serial command. When I compared the signals from the Phython code with the one from the PXT-code there was an obivious difference. (s.a. forum entry here: link )