midiin is not suposed to receive realtime message so it seems...

but then i guess it receives active sensing and midirealtimein does not, and maybe midirealtimein should receive it and midiin shouldn't

but how about clock messages, are you able to get them with midiclkin? I can't at all!

Conversely, I guess [midiout] can send realtime messages and everything, right?

cheers

cheers

2016-08-31 22:43 GMT-03:00 Ingo <ingo@miamiwave.com>:
I'm using [midiin] and I can receive active sensing as well as all other
MIDI messages.

Ingo

________________________________________
Von: Pd-list [mailto:pd-list-bounces@lists.iem.at] Im Auftrag von
Alexandre Torres Porres
Gesendet: Donnerstag, 1. September 2016 02:43
An: pd-list@lists.iem.at
Betreff: [PD] is [midiclkin] working? should [midirealtimein] output
clockas well?

howdy, by looking at the source of [midiclkin] I see a comment saying it
deals with midi "FA FB FC FF", which is 250, 251, 252 and 255

But I can see it receives other messages, including clock (F8 - 248), it
does detect from 248 to 253 and also 255, so only 254 is not detected
(active sensing). So, if it does receive all these messages, maybe
change this at the code's comment? 

Well, I did later check the help file for [midirealtimein] and it says
it receives "all realtime midi messages", so yeah, seems the code's
comment is wrong and that it should receive clock messages.

But Now... I was trying to ger midi clock with [midiclkin] and couldn't
do it, I just got it with [midirealtimein] 

I wonder if it is working, is anybody else using this with success?

thanks