<br><br><b><i>martin.peach@sympatico.ca</i></b> a écrit :<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> > <br>> De: patco <megalegoland@yahoo.fr><br>> Date: 2006/09/26 mar. AM 10:12:01 GMT-04:00<br>> À: pd-list@iem.at<br>> Objet: RE : [PD] midi synch strategy<br>> <br>> Hello,<br>> some people might be interested about this attached patch for a midi sync.<br>> <br>> [242 0 0( won't work as expected because the second argument is for midi port.<br>> <br><br>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.<br>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.<br><br>Actually now I do. In the source code s_midi.c, the function sys_dispatchnextmidiin():<br>
/* other kinds of messages are just dropped here. We'll<br> need another status byte before we start letting MIDI in<br> again (no running status across "system" messages). */<br> case MIDITIMECODE: /* 1 data byte*/<br> break;<br> case MIDISONGPOS: /* 2 */<br> break;<br> case MIDISONGSELECT: /* 1 */<br> break;<br><br>Martin<br><br></megalegoland@yahoo.fr></blockquote>Okay, that's perfect.<br>All info are indeed in source files.<br>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.<br>Patco<br><p> 
<hr size="1">
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. <a href="http://fr.rd.yahoo.com/evt=42054/*http://fr.answers.yahoo.com">Cliquez ici</a>.