I have full MIDI parsing in a couple projects including PdParty. I could look into it at some point...
On Aug 20, 2017, at 5:33 PM, Alexandre Torres Porres porres@gmail.com wrote:
I thoguht adding "FE" would be so simple that even a guy like me could do a Pull Request for it... but no :/
2017-08-20 12:23 GMT-03:00 Alexandre Torres Porres <porres@gmail.com mailto:porres@gmail.com>: i guess it's that if you're dealing with raw MIDI, it could be annoying to filter out those messages, who knows? Well, Miller probably does know why :)
2017-08-20 6:52 GMT-03:00 Dan Wilcox <danomatika@gmail.com mailto:danomatika@gmail.com>: Good to know. As Pd dates from the late 90s, that might hit have been the case originally...
enohp ym morf tnes
Dan Wilcox danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
On Aug 20, 2017, at 10:08 AM, Ingo <ingo@miamiwave.com mailto:ingo@miamiwave.com> wrote:
Active Sensing comes in about 3 times per second with a single byte. Nothing to worry about ...
Pd has no problem handling 600 or more note, CC and pitchbend messages per second in my project. I'm seeing no problems whith 2 MIDI ins sending each 600 messages (total of 1.200 per second) - without losing any timing accuracy.
Ingo
From: Pd-list [mailto:pd-list-bounces@lists.iem.at mailto:pd-list-bounces@lists.iem.at] On Behalf Of Dan Wilcox Sent: Sunday, August 20, 2017 9:11 AM To: pd-list@lists.iem.at mailto:pd-list@lists.iem.at Subject: Re: [PD] Midi Real Time Active Sensing Message Ignored
I think the reason realtime messages are ignored when receiving is that, by their nature, there are *a lot* of them and they come *really quickly*. Based Pd's architecture, I can imagine a flood of realtime messages might make the GUI unresponsive, so they are left off. I might be wrong on this.
On Aug 20, 2017, at 4:20 AM, pd-list-request@lists.iem.at mailto:pd-list-request@lists.iem.at wrote:
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.
Dan Wilcox @danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
Pd-list@lists.iem.at mailto:Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list https://lists.puredata.info/listinfo/pd-list
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/