Hi, this is what I got working on LooseXP

and BTW IMO MIDI is always kinda soft-rough, I use it but Idont xpect too much.

mvh/ Steffen Leve Poulsen

Si Mills skrev:

Hello List

I was wondering what the current state of play is with regard to
syncing to midiclock on OSX? (and windows I guess too). I have
managed to either generate a midi timecode or read it using
[midirealtimein] over the IAC bus and using [alternate] and [timer]
to create the clock in PD. (incidently [midirealtimein] shouldn't
work on OSX but it outputs something akin to 24pulse/quarter note!).
However, jitter makes it simply unusable for anything serious. I
suspect there needs to be some sort of lower level support as midi
over iac is not timetagged and relatively low priority in the OS.

I have seen a number of objects such as [midiclkin] or
[midirealtimein] but they either seem to be incomplete or supported
on one platform. What is the currently the best strategy to syncing
to either other apps, or hardware for that matter? If one of the
developers could shed some light on this that would be much appreciated.

Many thanks

Si

---

PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

#N canvas 486 41 565 560 12; #X obj 112 10 midirealtimein; #X obj 112 96 timer; #X obj 112 125 select 0; #X obj 147 357 spigot; #X obj 191 263 del 500; #X obj 190 289 1; #X obj 112 67 t b b; #X obj 147 445 f; #X msg 220 470 0; #X obj 165 499 + 1; #X obj 217 217 0; #X obj 147 471 moses 95; #X obj 273 465 select 0 24 48 72; #X obj 166 191 t b b b; #X obj 166 379 24; #X obj 217 337 t f f; #X obj 292 133 /; #X floatatom 292 73 5 0 0 0 - - -; #X msg 292 105 60000 $1; #X obj 273 505 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1; #X obj 305 505 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1; #X obj 338 505 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1; #X obj 371 505 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1; #X text 341 73 <-set to master BPM; #X text 276 432 MIDIClock is 96 tics per bar; #X obj 323 200 cpu; #N canvas 0 0 534 580 comments 1; #X text 56 29 This is working on winXP with ;; #X text 116 97 - PD-Puckette 0.40-2; #X text 56 141 It's a workaround , since [midirealtimein] doesn't ; #X text 159 357 start: 250 (FA); #X text 158 379 clock-tick: 248 (F8); #X text 158 401 stop: 252 (FC); #X text 157 423 continue: 251 (FB); #X text 111 70 - MIDI-yoke and! MIDI-oxe; #X text 60 164 give you standart MIDI-Clock-messages , only timing. ; #X text 403 16 december 2006; #X text 53 207 So the startmessage and first tick appears as time 0 [select 0] , wait one beat , start counting.; #X text 135 328 MIDI-Clock-messages are ;; #X text 37 533 Steffen Leve Poulsen slagmark at worldonline dot dk ; #X restore 8 9 pd comments; #X connect 0 0 6 0; #X connect 1 0 2 0; #X connect 2 0 13 0; #X connect 3 0 7 0; #X connect 4 0 5 0; #X connect 5 0 3 1; #X connect 6 0 1 0; #X connect 6 1 1 1; #X connect 6 1 3 0; #X connect 7 0 11 0; #X connect 7 0 12 0; #X connect 8 0 7 1; #X connect 9 0 7 1; #X connect 10 0 15 0; #X connect 11 0 9 0; #X connect 11 1 8 0; #X connect 12 0 19 0; #X connect 12 1 20 0; #X connect 12 2 21 0; #X connect 12 3 22 0; #X connect 13 0 14 0; #X connect 13 1 4 0; #X connect 13 2 10 0; #X connect 14 0 7 1; #X connect 15 0 7 0; #X connect 15 1 3 1; #X connect 16 0 4 1; #X connect 17 0 18 0; #X connect 18 0 16 0;

#N canvas 275 199 454 304 12; #X obj 211 53 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 1 1; #X obj 211 177 midiout; #X obj 102 80 select 0 1; #X msg 102 114 252; #X msg 139 114 250; #X msg 211 107 248; #X obj 211 77 metro 20.8333; #X floatatom 309 49 5 0 0 0 - - -; #X obj 266 24 expr (60000/$f1/24); #X floatatom 264 1 5 0 0 0 - - -; #X text 207 0 BPM-->; #X connect 0 0 2 0; #X connect 0 0 6 0; #X connect 2 0 3 0; #X connect 2 1 4 0; #X connect 3 0 1 0; #X connect 4 0 1 0; #X connect 5 0 1 0; #X connect 6 0 5 0; #X connect 7 0 6 1; #X connect 8 0 7 0; #X connect 9 0 8 0;