Track Clock Switch at global Zero cross

[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.