Hi All,
I noticed that Pd doesn't receive the real time message 254 (0xFE). it's able to generate it, but will ignore it as input. I tried with [midirealtimein] and [midiin]. I'm sure my midi device is generating and receiving this message and Pd is ignoring it. I'm trying sending out the message via midi device, then the midi out of my device is connected to the midi in (loopback). of course I'm monitoring the device in and out with an external software, so I'm sure the message is sent and received.
does anyone know something about that?
cheers, Mario
I can confirm this! (Windows 7, Pd 0.48).
I also noticed the following: [midiin] won't output realtime messages while it does output sysex messages. [sysexin] outputs sysex messages as expected. [midirealtimein] outputs all realtime messages except active sensing. [midiclkin] doesn't output any clock messages while [midirealtimein] does so it's apparently broken.
actually it would be cool if [midiin] would really output all MIDI messages!
Christof
Gesendet: Donnerstag, 17. August 2017 um 15:00 Uhr Von: "Mario Buoninfante" mario.buoninfante@gmail.com An: pd-list pd-list@lists.iem.at Betreff: [PD] Midi Real Time Active Sensing Message Ignored
Hi All, I noticed that Pd doesn't receive the real time message 254 (0xFE). it's able to generate it, but will ignore it as input. I tried with [midirealtimein] and [midiin]. I'm sure my midi device is generating and receiving this message and Pd is ignoring it.I'm trying sending out the message via midi device, then the midi out of my device is connected to the midi in (loopback). of course I'm monitoring the device in and out with an external software, so I'm sure the message is sent and received. does anyone know something about that?
cheers,Mario_______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
2017-08-19 20:42 GMT-03:00 Christof Ressi christof.ressi@gmx.at:
I can confirm this! (Windows 7, Pd 0.48).
I also noticed the following: [midiin] won't output realtime messages while it does output sysex messages.
help file says it outputs all midi messages but realtime messages, so this is expected and documented.
actually it would be cool if [midiin] would really output all MIDI messages!
maybe... try and open an issue on github, or a Pull Request (PR) and make a case for that ;)
[midiclkin] doesn't output any clock messages while [midirealtimein] does
so it's apparently broken.
It is broken, and instead of being fixed, it is actually being removed, so the idea is to keep using [midirealtimein] for that.
I try sending a PR to fix [midiclkin], but it was decided just to let it go, see this vurrent PR https://github.com/pure-data/pure-data/pull/187
[midirealtimein] outputs all realtime messages except active sensing.
I guess we can easily fix this and make it output via [midirealtimein]. I opened an issue for that. As soon as that other PR of mine about midiclkin is taken care of, I can try and make a new one to fix this.
cheers