On 2025-11-22 09:50, Alexandre Ratchov wrote: > I'm instested in the note to control-change conversion as well. I've > got one of these controllers. No promise, but'll try to look at this > thjese days. I've run midish through doxygen and looked through the result. Crikey - looks like a pretty spiderweb. I've also dusted-off my Uni C textbooks. As a "simple"?? exercise to try to (re)learn what I have since long forgotten - I thought I'd try to extend the device definitions. If nobody has any objections? No guarantee of success but I'll allocate a few hours to the attempt over the next few weeks. What I was thinking was something like: dnew 0 "28:1" rw #HW CTRL dnew 1 "28:0" rw #HW MIDI dnew 2 nil rw "piano" hw #Keyboard dnew 3 nil rw "ctrls" hw #Controllers The goal would be an easier to identify port name that shows in the drop-downs of the various applications. Port Client name Port name 0:0 System Timer 14:0 Midi Through Midi Through Port-0 128:0 sysex-controls listen:in 129:0 midish/3 midish-piano 130:0 midish/2 midish-ctrls However, it appears that at least Musescore and Ardour only show "hardware" MIDI ports in their config dialogs. Annoying as otherwise the only way to connect midish to the applications is via a virtual patchbay. I have tested SND_SEQ_PORT_TYPE_HARDWARE and in that case midish does show in Musescore & Ardour. Musescore also identifies SND_SEQ_PORT_TYPE_SOFTWARE but Ardour does not. Does anyone object to the optional inserting of a "hw" key allowing midish to lie to the applications? dev->port = snd_seq_create_simple_port(dev->seq_handle, "midish", mode, SND_SEQ_PORT_TYPE_MIDI_GENERIC | SND_SEQ_PORT_TYPE_HARDWARE); Lets see what mess I can get myself into...?Received on Sun Nov 23 2025 - 22:35:27 CET
This archive was generated by hypermail 2.3.0 : Mon Nov 24 2025 - 01:30:02 CET