I want to controll the speed of a metronome with midi sync, how should i do?
I have searched the forums and googled but can't find a good answer how to do this and the documentation for midi in messages is kinda sparse.

Also since its my first message i guess i should say hi:
Hi everyone!

hey thanks boonier. i didn't think midi sync was going to work for me, but it just did and all thanks to you and this patch. cheers.

no probs what did you end up syncing, and is it quite tight sync?

cheers

well, i just synced a sequencer here in linux, but actually i have no idea how to use that program so it was just running without any output. but it was definitely getting the 250 start, 252 stop and 248 clock messages.

the final goal though is to help a friend sync some stuff i made to ableton live.

hi boonier,
thanks for the patch. could you please explain how exactly it works? because i might be wrong, but it seems incorrect to me.
There is a [== 248] object and [t b b] after it.
From what i understand, the == object doesn't send bangs to the outputs, but 0s (if not equal) or 1 (if equal), so the [t b b] object is banged (with zero) even if you receive other than 248 (=clock) midi message from the [midirealtimein] ??

could you (or sombody) explain it to me, please?

i'm very confused as i'm unable to find documentation for "midiin" and for "midirealtimein". when i right click and choose help, it opens a help page where these objects are not mentioned.

(i'm having troubles syncing two of my patches on two machines using midi clock in/out. on receiving the clock, i seem to be receiving more bangs per measure than i expect and i'm getting out of sync because of it.)

thanks and regards
daniel

edit: I am in windows os, so the midirealtimein should work...

just about the post this thanks i will give it a test with my daw

@dnk777 said:

hi boonier,
thanks for the patch. could you please explain how exactly it works? because i might be wrong, but it seems incorrect to me.
There is a [== 248] object and [t b b] after it.
From what i understand, the == object doesn't send bangs to the outputs, but 0s (if not equal) or 1 (if equal), so the [t b b] object is banged (with zero) even if you receive other than 248 (=clock) midi message from the [midirealtimein] ??

could you (or sombody) explain it to me, please?

I find the same problem, it doesn't make any sense to me the [== 248] object since [t b b] will still trigger its bangs either if the condition is satisfied or not.

Besides, I don't understand this patch correctly. Which is the purpose of delaying 500 ms each bang and resetting the counter to 0? Could you explain this patch thoroughly?

Hi - quite a while since I saw that patch! not sure about the [== 248] bit as the triggers will still be there regardless as you say.

THe purpose of resetting the counter to 0 after the stream of 248s stops coming in is so that the counter fires on the downbeat when re-started, and not off beat...

To be honest, I think I stopped using this method in favour of just using the [midirealtimein] to trigger the stop/stop pf an internal metro as the timing was more rock solid and only relied on the initial start trigger being relatively accurate. THe stream of 248 was subject to jitter over the IAC bus. Using this last method seemed more satisfactory.

Perhaps the first method is worth revisiting now as Jack osx now has sample accurate midi?

hope this helps/clarifies

thanks a lot

I hate to re-visit an old post like this, but I'm trying to use PD as my main sequencer - I've built a nice little (not-so-little really) patch that receive MIDI clock fine, but I'm trying now to send the MIDI clock so I can use PD as the master - obviously there's no [midirealtimeout] object, can I somehow get away with using [midiout]?