Hello,
Here is a quick reminder on how to generate raw midi in order to use the midiout object.

A question: is there another way to work with multiple midi ports, or is midiout the only one, pd vanilla.

bye

RawMidiBase.pd

If you want it to work across platforms, [midiout] and [midiin} are the most reliable options. I have a collection of vanilla abstractions to make all this easier which I am almost ready to post, these cover sysex, RPN, NRPN, and CC, and dealing with data from controllers which send relative data, but they just went through a massive overhaul because of the new [list store] methods coming out in 0.52 and I will not bother sharing them or even finishing them until 0.52 is finalized. I will probably stick these onto deken since they should be useful to enough people to warrant it, mostly aimed at easing the creation of interfaces between midi controllers and pd or using pd as an intermediary between the controller and other hardware/software but should come in handy anytime one needs to deal with midi.

Ok nice.
An update with sync stream.

I think also 250 is a start sync message and 252 is a sync stop message but I could not verify.

And for more in depht tutorials about midi,
the website of the Midi Association,
that defines the midi specifications.

https://www.midi.org/specifications

@Il-pleut Yes.... 250 and 252.
This might interest someone...... https://github.com/IndustrieCreative/Harmonync
I haven't uploaded it so as not to upset @Eeight
Although it was built a long time ago for extended the heavy midi lifting was done including sysex and sysex bulk dumps with checksum (maybe why no-one is having much luck with bulk dumps at the moment)...... sysex.zip
Though mostly Vanilla of course.
David.

@whale-av This server is mimicking humans emotions: ups and downs, it does have his limits But good news, because it's a server and not a human, we can just throw money at it!