De: patco megalegoland@yahoo.fr Date: 2006/09/26 mar. AM 10:12:01 GMT-04:00 À: pd-list@iem.at Objet: RE : [PD] midi synch strategy
Hello, some people might be interested about this attached patch for a midi sync.
[242 0 0( won't work as expected because the second argument is for midi port.
It looks like you have to send single numbers in sequence, like 242 followed by two numbers less than 128. Below is a patch that should do that. At least [midiout] actually sends the message. For me [midiin], on the other end of the cable, outputs 242 and the right outlet is always 2. I don't know where the data went.
Actually now I do. In the source code s_midi.c, the function sys_dispatchnextmidiin(): /* other kinds of messages are just dropped here. We'll need another status byte before we start letting MIDI in again (no running status across "system" messages). */ case MIDITIMECODE: /* 1 data byte*/ break; case MIDISONGPOS: /* 2 */ break; case MIDISONGSELECT: /* 1 */ break;
Martin
#N canvas 519 13 297 272 12; #X obj 158 161 midiout; #X floatatom 69 80 5 0 0 0 - - -; #X floatatom 24 80 5 0 0 0 - - -; #X obj 20 123 unpack 0 0 0; #X obj 20 100 pack 0 0 242; #X floatatom 111 162 5 0 0 0 - - -; #X floatatom 65 162 5 0 0 0 - - -; #X floatatom 20 162 5 0 0 0 - - -; #X floatatom 20 -15 5 0 0 1 position - -; #X obj 20 33 / 128; #X obj 65 33 % 128; #X obj 20 57 % 128; #X obj 20 9 t f f; #X connect 3 0 0 0; #X connect 3 0 7 0; #X connect 3 1 0 0; #X connect 3 1 6 0; #X connect 3 2 0 0; #X connect 3 2 5 0; #X connect 4 0 3 0; #X connect 8 0 12 0; #X connect 9 0 11 0; #X connect 10 0 1 0; #X connect 10 0 4 1; #X connect 11 0 4 0; #X connect 11 0 2 0; #X connect 12 0 9 0; #X connect 12 1 10 0;
#N canvas 519 13 297 272 12; #X obj 158 161 midiout; #X floatatom 69 80 5 0 0 0 - - -; #X floatatom 24 80 5 0 0 0 - - -; #X obj 20 123 unpack 0 0 0; #X obj 20 100 pack 0 0 242; #X floatatom 111 162 5 0 0 0 - - -; #X floatatom 65 162 5 0 0 0 - - -; #X floatatom 20 162 5 0 0 0 - - -; #X floatatom 20 -15 5 0 0 1 position - -; #X obj 20 33 / 128; #X obj 65 33 % 128; #X obj 20 57 % 128; #X obj 20 9 t f f; #X connect 3 0 0 0; #X connect 3 0 7 0; #X connect 3 1 0 0; #X connect 3 1 6 0; #X connect 3 2 0 0; #X connect 3 2 5 0; #X connect 4 0 3 0; #X connect 8 0 12 0; #X connect 9 0 11 0; #X connect 10 0 1 0; #X connect 10 0 4 1; #X connect 11 0 4 0; #X connect 11 0 2 0; #X connect 12 0 9 0; #X connect 12 1 10 0;
martin.peach@sympatico.ca a écrit : >
De: patco Date: 2006/09/26 mar. AM 10:12:01 GMT-04:00 Ã: pd-list@iem.at Objet: RE : [PD] midi synch strategy
Hello, some people might be interested about this attached patch for a midi sync.
[242 0 0( won't work as expected because the second argument is for midi port.
It looks like you have to send single numbers in sequence, like 242 followed by two numbers less than 128. Below is a patch that should do that. At least [midiout] actually sends the message. For me [midiin], on the other end of the cable, outputs 242 and the right outlet is always 2. I don't know where the data went.
Actually now I do. In the source code s_midi.c, the function sys_dispatchnextmidiin(): /* other kinds of messages are just dropped here. We'll need another status byte before we start letting MIDI in again (no running status across "system" messages). */ case MIDITIMECODE: /* 1 data byte*/ break; case MIDISONGPOS: /* 2 */ break; case MIDISONGSELECT: /* 1 */ break;
Martin
Okay, that's perfect. All info are indeed in source files. We can even send MTC code with 48 packets that contain 241 followed by one argument, but it seems very complicated to set up with pd patches. 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.