Track Clock Switch at global Zero cross

[andisyntz]

Hello, I would like a function that can reset a pattern in a track at global zero crossing when the track clock is changed to a different track clock, so that the track clock switch does not wait until the pattern has run through, but until the global zero crossing occurs.
Currently, when you change the track clock, it waits until the end of the pattern, which can take quite a long time at /32 until the pattern has run through. I would prefer it if, when I switch the track clock, the corresponding track would be reset after the global 64 steps and the new track clock would play the pattern from the beginning. 
Thank you for your efforts.

[XORadmin]

Did you try to change the sync type in the settings. I am not sure right now in my head but the sync option does always start the new cued pattern on a zerocross regardless of the clock.

[andisyntz]

Did you try to change the sync type in the settings. I am not sure right now in my head but the sync option does always start the new cued pattern on a zerocross regardless of the clock.

The sync option has no effect on this specific situation. The track clock is only updated at the end of the pattern.

[XORadmin]

Yes but the clock change now in the new pattern should definitely have impact.

[andisyntz]

Yes but the clock change now in the new pattern should definitely have impact.

I couldn't detect any influence of the sync option on the track clock switching behaviour in running mode.  If you change a new track clock during operation, the new track clock is only set when the divided pattern has reached its last step then the track loop begins again with step 0 and a new track clock. It seems as if the individual track clocks always refer to their own dividet track loop. I would prefer it if a global 64-step counter served as a reference, so that when the global clock crosses zero step, the new selected Track clock would also be activated for the track clock.
To clarify, my query concerns the switching behaviour during a running loop. I have mapped the track clocks to  faders and would like to change the Track Clocks in running mode, but when I set a divider (e.g. /8 or /16) as the Track Clock, Nerdseq wait for the newly set values to change until the divided Clock in a track has counted to 64 (divided) steps, which can take quite a long time with /32, for example. However, I don't want to stop Nerdseq during live operation to force the change.

[andisyntz]

Yes but the clock change now in the new pattern should definitely have impact.

I have noticed similar behaviour (track clock switching only at the end/Zero Cross of the loop) with the Combined Playback FX (regardless of the setup option: Pattern Launch Type: Normal or Sync):
Steps to reproduce:
1. New pattern
2. Pattern column 00: FX1: CHPB 009 (Combined Playback Normal)
3. Set track setup: Track Clock: /4
4. Play pattern

Expected behaviour: Track clock switches directly to track clock normal at step 00.

Current behaviour: Track clock only switches to track clock normal when transitioning from step 63 to step 00.

I hope that this problem and the one I described earlier can be solved somehow.
Thanks for your efforts.

[XORadmin]

Yes but the clock change now in the new pattern should definitely have impact.

I have noticed similar behaviour (track clock switching only at the end/Zero Cross of the loop) with the Combined Playback FX (regardless of the setup option: Pattern Launch Type: Normal or Sync):
Steps to reproduce:
1. New pattern
2. Pattern column 00: FX1: CHPB 009 (Combined Playback Normal)
3. Set track setup: Track Clock: /4
4. Play pattern
Expected behaviour: Track clock switches directly to track clock normal at step 00.
Current behaviour: Track clock only switches to track clock normal when transitioning from step 63 to step 00.
I hope that this problem and the one I described earlier can be solved somehow.
Thanks for your efforts.

CBPB 009 changes the clock indeed when the pattern is finished.
CBPB 109 changes the clock directly.   <--  this is the one you need

From the manual (page 41):
"1XX Same as 0XX but it changes the clock immediately. Use this with caution as this might cause an un-synchronized pattern if being called somewhere in the middle of a pattern. If it’s being set on the first step then the new clock setting will run properly synchronized within this pattern. (Depending on if the last pattern was synchronized)
This works regardless of the running pattern order. This command on the first step will always been fetched before."

That does work if in SYNC mode if you cue a new pattern and then on the zero cross. In the next pattern you got the 'clock change now'  command which takes care that it will run with the new clock setting.

I just tested it to be sure and it works as expected.