phasor/midiclock

Dlab's icon

Hi,

anyway to make phasor output stable midiclock?

I have phaser->what->edge-> to bang out midiclock tick to midi out but it is just all over the place...

when I max everything in audio settings and turn everything off on mac it still wobbles +-1 bpm constantly...

well the goal is to push slight variations in tempo through phasor but it seems max is doing it for me as a default :-)

Thanks!

Source Audio's icon

you are converting signal into data domain, and will allways have fluctuations

when sending midiclock.

by the way same would happen on clock receiver side when you use metro instead,

only that it will fluctuate much less.

here comparison, showing measured min/max clock deviation in ms

comparing metro with phasor, with or without audio interrupt.

midi beat clock sent / received through IAC buss on mac.

You migt expect some differences if measured using midi hardware.

but as you say you have fluctuatons of ± 1 bpm,

could be that you have rounded result.

depending on what you use to measure clock timing.

Dlab's icon

I was just looking at what digitakt is showing as received BPM so nothing scientific but it was just wobbling between 146-148 when the bpm was set to 147 sometimes it dips to 145 etc...

what is the best practice here if I want to use max as clock master with hardware and still use phasor as internal clock in max?

thanks!

Source Audio's icon

what your digitakt shows is a try to measure incoming clock

and calculate bpm from it.

Depends what it makes out of it.

in traditional midi clock usage,

one simply progresses when ticks ar received.

same as drummer on such galeon sets rowing speed.

But if your device tries to recognise tempo, and then use it

for own sample stretching and whatever else, then

it could get weird.

Now to best paractice to use midi clock, signal based clock, and similar.

It really depends what you want to sync together, and in what relation.

One could even use realtime progress, like sample count,

and rip everything else from it.

pdelges's icon

Is the timing accuracy better when using [sync~]'s rightmost outlet?

Dlab's icon

so sync with set bpm wobbles around the same i think. I know this is not precise enough but you can see some of the message are pretty off...

14:57:28.269 To Fireface 400 (F4E) Port 1 Clock

14:57:28.278 To Fireface 400 (F4E) Port 1 Clock

14:57:28.295 To Fireface 400 (F4E) Port 1 Clock

14:57:28.316 To Fireface 400 (F4E) Port 1 Clock

14:57:28.329 To Fireface 400 (F4E) Port 1 Clock

14:57:28.346 To Fireface 400 (F4E) Port 1 Clock

14:57:28.363 To Fireface 400 (F4E) Port 1 Clock

14:57:28.380 To Fireface 400 (F4E) Port 1 Clock

14:57:28.397 To Fireface 400 (F4E) Port 1 Clock

14:57:28.415 To Fireface 400 (F4E) Port 1 Clock

14:57:28.431 To Fireface 400 (F4E) Port 1 Clock

14:57:28.448 To Fireface 400 (F4E) Port 1 Clock

14:57:28.465 To Fireface 400 (F4E) Port 1 Clock

14:57:28.482 To Fireface 400 (F4E) Port 1 Clock

14:57:28.499 To Fireface 400 (F4E) Port 1 Clock

14:57:28.516 To Fireface 400 (F4E) Port 1 Clock

14:57:28.533 To Fireface 400 (F4E) Port 1 Clock

14:57:28.550 To Fireface 400 (F4E) Port 1 Clock

14:57:28.567 To Fireface 400 (F4E) Port 1 Clock

14:57:28.584 To Fireface 400 (F4E) Port 1 Clock

14:57:28.601 To Fireface 400 (F4E) Port 1 Clock

when running click~ to the sync~ from phasor it is almost the same... maybe I should run digitakt as master and use sync~ to create a ramps for internal timing. But when I run it with hw it sounded ok so probably I should stop looking at the numbers and just start tweaking the knobs...