Hi Dan, Thanks for getting back to me. Yap, I had a look at the protocol and is like you said about retro-compatibility. I'm glad to hear that probably can be dealt with making some changes in s_midi.c, work that of course I know still takes some efforts. My question though, was more related to the new msg introduced by MIDI 2.0, with a different structure and resolution. But I suspect what you said is valid for that as well, right?
Cheers, Mario On Mon, 6 Apr 2020 at 14:23, Dan Wilcox <[email protected]> wrote: > Actually, form what I've read, I don't think MIDI 2 requires any (or very > many) changes to Portmidi as Portmidi wraps the various OS-level MIDI APIs > and gives you raw bytes. The actual MIDI protocol interpretation is handled > in the Pd core. > > MIDI 2 is basically an extension of the MIDI 1 protocol and MIDI 2 > messages can contained embedded MIDI 1 messages. There is an additional > query communication where a device can ask about the capabilities of > another device. Overall, it seems to be designed to work seamlessly with > older MIDI 1 devices/software. > > Short answer is: I don't think anyone is doing this, but it can probably > been done by modifying MIDI handling in s_midi.c. > > On Apr 6, 2020, at 12:00 PM, [email protected] wrote: > > Message: 1 > Date: Mon, 6 Apr 2020 10:51:26 +0100 > From: Mario Buoninfante <[email protected]> > To: pd-list <[email protected]> > Subject: [PD] MIDI 2.0 > Message-ID: > <CAHs=m8tce+yom8woxocdr7jzi_pzfmm3t0dkdwru0_6dwfa...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi all, > > Is there any plan to support MIDI 2.0? I know this is more of a question > about PortMidi, but I was wondering if anybody knows anything about it. > > Cheers, > Mario > > > -------- > Dan Wilcox > @danomatika <http://twitter.com/danomatika> > danomatika.com > robotcowboy.com > > > >
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
