I wonder if we should consider adding midi 2.0 support for 7.0. Looks like it's in CoreMIDI already. 

Prof. Victor Lazzarini
Maynooth University
Ireland

My first thought is to provide a module interface, in a similar way to what we do for MIDI 1.0. Then we can implement experimental plugin modules for CoreMIDI and perhaps Windows when it comes out. If/when portmidi implements it, we can then do a portmidi module. This will also include any internal changes we may need to accommodate it (maybe not too many).
If we have MIDI 2.0 ready system, it will probably be a win.

At the moment, I think the cleanest way to do this is to keep it separate from MIDI 1.0, so we might have a different option to enable it, something like --midi2=dev. 
Users can choose this instead of -Mx. 

I’ll add a ticket and then we can discuss it there.
========================
Prof. Victor Lazzarini
Maynooth University
Ireland

> On 27 Feb 2024, at 23:52, Stephen Kyne  wrote:
> 
> P {margin-top:0;margin-bottom:0;} *Warning*
> This email originated from outside of Maynooth University's Mail System. Do not reply, click links or open attachments unless you recognise the sender and know the content is safe.
> What would that look like in terms of implementation?
> 
> https://github.com/PortMidi/portmidi/issues/59 I see that portmidi has no plans to implement it.
> 
> It seems Windows support is still in preview stages: https://github.com/microsoft/MIDI
> 
> Stephen
> From: Csound-developers  on behalf of Victor Lazzarini 
> Sent: Tuesday 27 February 2024 23:16
> To: CSOUND-DEV@LISTSERV.HEANET.IE 
> Subject: [Csnd-dev] midi 2.0   I wonder if we should consider adding midi 2.0 support for 7.0. Looks like it's in CoreMIDI already. 
> 
> Prof. Victor Lazzarini
> Maynooth University
> Ireland