[PD] Midi Real Time Active Sensing Message Ignored

[Dan Wilcox]

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
robotcowboy.com


> On Aug 20, 2017, at 10:08 AM, Ingo <ingo at 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 at lists.iem.at] On Behalf Of Dan Wilcox
> Sent: Sunday, August 20, 2017 9:11 AM
> To: pd-list at 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 at 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
> robotcowboy.com
> 
> 
> 
> 
>