Clock output vs pattern output

[theotteryears]

Hi,

Sorry I'm asking so many questions recently but I have another clocking question.

The main clock output (when set to DINSYNC) is very consistent when sent to other modules, eg. they read the exact tempo.
However, when sending out a 24ppqn clock from a pattern (programmed 16th notes and then the track set to *6 speed) the tempo on the external modules moves between 160 and 162. is there a reason for this?

Also the patterns trigger output is slightly behind that of the main clock output. This is a problem for some of my modules which require a 24ppqn clock and a reset as if im clocking them from the main output, the reset for a track trigger output is slightly behind.

Thanks again!

[XORadmin]

No worries about asking questions.

You are using the latest version V1.21A?
I would expect the triggers to be stable. Maybe you have trigger delay turned on so they are always a bit late?
Please keep in mind that some modules need a 1:1 On/Off ratio for clocks to be able to calculate them well. And the clock out does this, however, triggers are different.
But also, reset signal must always be slightly later than the clocks, because else a clock which was for the last step is read after the reset.

I would think in general using clock multipliers to generate a clock is not a good option. In the first place because multiplication is always a approxisation with clocking and this could produce indeed jitters.

[theotteryears]

Yes using the latest firmware. There is no delay on the triggers... maybe it's like you said, that the clock output is better for the other modules to calculate from.
Can you think of a better way to do this?

Would setting a groove of 1 instead be preferable to using the *6 mutilplier on a track?

I'm just trying to send out 24ppqn to various other sequencers, so I can turn on and off their clocks at different points in the song

thanks for your reply!

[XORadmin]

I think it is in general tricky what you want to do. But it's possible.
Groove 1 should be the better option indeed.

Still you are sending triggers and not clocks. If the gear clocks on the raising edge only, all is fine.

Why are you not using the normal clock output and then a bit delayed triggers to do the reset?

[theotteryears]

only because my Grids is a little annoying when it comes to reset... if I use clock output and a track to reset it then it stutters.
I have to have a track for reset and a track for clock, and the track for the clock has to be on an output after the reset for it to work properly! annoying, but ive tested it in various ways for a few weeks now :S