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
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
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
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
that comment actually belongs to [midirealtimein.]
[midiclkin] should only receive F8, according to the source code.
midiin is not suposed to receive realtime message so it seems...
[midiin] is supposed to recieve all midi messages. if the other objects don't seem work for you, try [midiin] and route the messages you care about. if you still don't get what you want, there might be a problem with your midi configuration.
Christof
Gesendet: Donnerstag, 01. September 2016 um 03:50 Uhr Von: "Alexandre Torres Porres" porres@gmail.com An: Ingo ingo@miamiwave.com Cc: "pd-list@lists.iem.at" pd-list@lists.iem.at Betreff: Re: [PD] is [midiclkin] working? should [midirealtimein] output clockas well?
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[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[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 _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list%5Bhttps://lists.puredata.info/l...]
2016-09-01 5:19 GMT-03:00 Christof Ressi christof.ressi@gmx.at:
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
that comment actually belongs to [midirealtimein.]
that's what I meant to write, sorry, my bad
[midiin] is supposed to recieve all midi messages.
but help file says it doesn;t get realtime messages
if you still don't get what you want, there might be a problem with your midi configuration.
I'm getting the clock with [midirealtimein] so my MIDI is not the problem, but [midiclkin] is not getting it!
Anybody is getting [midiclkin] to actually work?
I went ahead and made a bug report anyway
cheers
but help file says it doesn;t get realtime messages
indeed... out of curiousity: did you try nevertheless? I'll try myself when I've set up all my stuff again (moved into a new flat and everything's still a huge mess).
Christof
Gesendet: Donnerstag, 01. September 2016 um 14:56 Uhr Von: "Alexandre Torres Porres" porres@gmail.com An: "Christof Ressi" christof.ressi@gmx.at Cc: Ingo ingo@miamiwave.com, "pd-list@lists.iem.at" pd-list@lists.iem.at Betreff: Re: Re: [PD] is [midiclkin] working? should [midirealtimein] output clockas well?
2016-09-01 5:19 GMT-03:00 Christof Ressi christof.ressi@gmx.at:> 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
that comment actually belongs to [midirealtimein.] that's what I meant to write, sorry, my bad [midiin] is supposed to recieve all midi messages. but help file says it doesn;t get realtime messages if you still don't get what you want, there might be a problem with your midi configuration. I'm getting the clock with [midirealtimein] so my MIDI is not the problem, but [midiclkin] is not getting it! Anybody is getting [midiclkin] to actually work? I went ahead and made a bug report anyway cheers
I tried it and i didnt get realtime messages in midiin
please try if you get [midiclkin] to work too :)
2016-09-02 10:23 GMT-03:00 Christof Ressi christof.ressi@gmx.at:
but help file says it doesn;t get realtime messages
indeed... out of curiousity: did you try nevertheless? I'll try myself when I've set up all my stuff again (moved into a new flat and everything's still a huge mess).
Christof
Gesendet: Donnerstag, 01. September 2016 um 14:56 Uhr Von: "Alexandre Torres Porres" porres@gmail.com An: "Christof Ressi" christof.ressi@gmx.at Cc: Ingo ingo@miamiwave.com, "pd-list@lists.iem.at" < pd-list@lists.iem.at> Betreff: Re: Re: [PD] is [midiclkin] working? should [midirealtimein] output clockas well?
2016-09-01 5:19 GMT-03:00 Christof Ressi christof.ressi@gmx.at:> 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
that comment actually belongs to [midirealtimein.]
that's what I meant to write, sorry, my bad
[midiin] is supposed to recieve all midi messages.
but help file says it doesn;t get realtime messages if you still don't get what you want, there might be a problem with your midi configuration.
I'm getting the clock with [midirealtimein] so my MIDI is not the problem, but [midiclkin] is not getting it!
Anybody is getting [midiclkin] to actually work?
I went ahead and made a bug report anyway
cheers
-
Alexandre Torres Porres -
Christof Ressi -
Ingo