De: patco megalegoland@yahoo.fr Date: 2006/09/25 lun. PM 03:31:21 GMT-04:00 À: martin.peach@sympatico.ca, pd-list@iem.at Objet: Re: RE: [PD] midi synch strategy
martin.peach@sympatico.ca a écrit :
It does receive something, it just outputs zeros. MartinI guess that sending these numbers in message boxes is not the way how midiout works,
Yes it is how it works. [midirealtimein] only responds to numbers greater than 248 when I send them through [midiout] one at a time. 248 is MIDI Clock. The MIDI spec says that the slave has to count clocks at a rate of 24 per quarternote. I guess [midirealtimein] should bang a counter. It doesn't handle the count itself.
is it possible to know what kind of message this object is expecting?
[midiout] should pass any midi message but you have to send the right number of bytes (3 for noteon, 1 for clock, etc.) or it will hang.
Martin
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. Cliquez ici.
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Can someone explain again, more clearly, exactly what message(s) I should send to the [midiout], to be received as midi clocks ie:
[metro 20.833] l [???( l [midiout]
Also, is there some way to get position, start and stop, in PD? I did get [midirealtimein] working, and the zeros are indeed more or less coming in at 24 ppq.
~David
On 9/25/06, martin.peach@sympatico.ca martin.peach@sympatico.ca wrote:
De: patco megalegoland@yahoo.fr Date: 2006/09/25 lun. PM 03:31:21 GMT-04:00 À: martin.peach@sympatico.ca, pd-list@iem.at Objet: Re: RE: [PD] midi synch strategy
martin.peach@sympatico.ca a écrit : It does receive something, it just outputs zeros. Martin
I guess that sending these numbers in message boxes is not the way how midiout works,
Yes it is how it works. [midirealtimein] only responds to numbers greater than 248 when I send them through [midiout] one at a time. 248 is MIDI Clock. The MIDI spec says that the slave has to count clocks at a rate of 24 per quarternote. I guess [midirealtimein] should bang a counter. It doesn't handle the count itself.
is it possible to know what kind of message this object is expecting?
[midiout] should pass any midi message but you have to send the right number of bytes (3 for noteon, 1 for clock, etc.) or it will hang.
Martin
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. Cliquez ici.
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
David Powers wrote:
Can someone explain again, more clearly, exactly what message(s) I should send to the [midiout], to be received as midi clocks ie:
[metro 20.833] l [???( l [midiout]
Also, is there some way to get position, start and stop, in PD? I did get [midirealtimein] working, and the zeros are indeed more or less coming in at 24 ppq.
~David
[X] | [metro 20.833] | [248( | [midiout]
should work.
Martin
David Powers wrote:
Can someone explain again, more clearly, exactly what message(s) I should send to the [midiout], to be received as midi clocks ie:
[metro 20.833] l [???( l [midiout]
Also, is there some way to get position, start and stop, in PD? I did get [midirealtimein] working, and the zeros are indeed more or less coming in at 24 ppq.
Start is 250, stop is 252. Position would be 242 followed by two numbers each less than 128 that combine to make a 14-bit number representing the number of 16th notes: So
[242 0 0( | [midiout]
should reset the pointer.
Martin
Wow, it works, now I can make PD and Ableton play nice, with either one as master. That's awesome!!!
Now I could have Ableton playing beatmatch tracks, while PD sends out crazy generative stuff to my external MIDI gear, this could be really cool.
~David
On 9/25/06, Martin Peach martin.peach@sympatico.ca wrote:
David Powers wrote:
Can someone explain again, more clearly, exactly what message(s) I should send to the [midiout], to be received as midi clocks ie:
[metro 20.833] l [???( l [midiout]
Also, is there some way to get position, start and stop, in PD? I did get [midirealtimein] working, and the zeros are indeed more or less coming in at 24 ppq.
Start is 250, stop is 252. Position would be 242 followed by two numbers each less than 128 that combine to make a 14-bit number representing the number of 16th notes: So
[242 0 0( | [midiout]
should reset the pointer.
Martin
It does receive something, it just outputs zeros. Martin
On my windows box, [midirealtimein] only receives something with it's own instance of pd (is it FUDI related?), when I am sendind data but not from another MTC host, even another instance of puredata. [metro 20.833]-->[248(-->[midiout] gives absolutely nothing outside pd. Maybe it is related with virtual MIDI ports I am using, witch are MIDIyokeNT and mapple midi? Haven't tried on linux/jack yet. Patco.
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. Cliquez ici.
patco megalegoland@yahoo.fr a écrit :
It does receive something, it just outputs zeros. Martin
On my windows box, [midirealtimein] only receives something with it's own instance of pd ... Maybe it is related with virtual MIDI ports I am using, witch are MIDIyokeNT and mapple midi?
I've tried to make a loop with an USB midi cable, it works like a charm on another host...
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. Cliquez ici.
-
David Powers -
Martin Peach -
martin.peach＠sympatico.ca
-
patco