Niels

Hey I'm trying to build a simple clock so that I can run my max patches as well as eurorack in sync using the expert sleepers ES-9. 

So I've made this thing using the phasor object but when I patch it to Pams New Workout its really wonky. What am I not getting?

sig~

rate~

dac~

scope~

attrui

message

qlim

loadbang

umenu

metro

transport

phasor~

panel

Hey I'm trying to build a simple clock so that I can run my max patches as well as eurorack in sync using the expert sleepers ES-9. 

So I've made this thing using the phasor object but when I patch it to Pams New Workout its really wonky.  What am I not getting?


building-a-clock-for-eurorack-integration

What exactly do you need to output as a sync clock ?

According to the pams new workout manual it should be 24 PPQN gates. So im guessing gate signals that run from 0 to 1.

According to the pams new workout manual it should be  24 PPQN gates. So im guessing gate signals that run from 0 to 1.  

I think a clock is just a unipolar signal, going from 0 to 1. So a saw wave with a DC offset would work too.

one can run rawticks output through modulo with any interval set

why then all this phasor~ rate~ and rest of it complication ?

Different gear might require different puls length or Vpp.

then why not simple triggered click~ ?
Transport seems to be used anyway,
one can run rawticks output through modulo with any interval set
and bang on zero.
why then all this phasor~ rate~ and rest of it complication ?

Different gear might require different puls length or Vpp.
That's why I asked.
It must be stated in docs of that grear.




I just realized that my reply yesterday was scrambled by my attempt to write it on the phone. Sorry about that. cleaned it up now. 

So I was under the impression that clocks were usually made with phasor~ objects to keep everything at audio rate and then clock division with rate~. And that this is sort of the max/msp way of doing things but looks like I'm wrong. 

Using the rawtick/modulo works. Thank you!

Just in case anyone else is finding this thread later. One of the reasons I got some drift was that on an M1 mac my I/O Vector size was too high. Setting it to anything below 128 does the trick and actually decreases CPU load. 

I just realized that my reply yesterday was scrambled by my attempt to write it on the phone. Sorry about that. cleaned it up now. 

So I was under the impression that clocks were usually made with phasor~ objects to keep everything at audio rate and then clock division with rate~. And that this is sort of the max/msp way of doing things but looks like I'm wrong. 

Using the rawtick/modulo works. Thank you!

Just in case anyone else is finding this thread later. One of the reasons I got some drift was that on an M1 mac my I/O Vector size was too high. Setting it to anything below 128 does the trick and actually decreases CPU load. 



Building a Clock for Eurorack integration