Dear admin, I found a problem when using CBPB's clock FX. For some reason, it will not sync with the master clock after division or multiplication. I set a step of 00-12. I have calculated that the total number of steps should be 64 steps after they are affected by the clock FX, but in fact it is shorter than 64 steps, between 63 and 64 steps. Of course, I can use track sync to force it to sync, but the effect is not what I want to happen at all. I have used different master clock settings, external or internal, and have also excluded the influence of odd clocks. I wonder if this is a defect? How can I do it according to my understanding? For this I upload photos of my sequence, thanks for your help.
p.s In steps 00-12, the total should be a perfect 64 steps.
![[Image: iLZtyma.jpeg]](https://i.imgur.com/iLZtyma.jpeg)
Hi Thomas, sorry the previous link may be broken, I have edited the post with the photos, hope you can take a look at it when you are free, thank you, best regards
Hey,
sorry I saw your question and the photo but I am still on the road from superbooth. It is right now hard for me to really follow all the different clock changes to find out if in the end your expected clockings are right.
But as a basic rule the clock dividers are always based on the main clock and if you change the clock then you might stop and break a former clock setting that was not finished yet. Also another rule is that except for the first step which will prefetch the 'next clock setting' if you use it on any step in the sequence then this step is already running when you change it. The prefetch is essential to know how many ticks need to be generated (or 'negative ticks) to get a dividing/multiplying functionality.
So when I am back I will check your sequence and will see if it is possible at all to create a sequence like this. It gets quite complex and was not the intended use in the first place.
Got it, thank you for your hard work in explaining, I'm so glad for your efforts and success in superbooth! This method of playing does seem a bit excessive, but after observing it for a few days, I know what I need to do to perfectly match the main clock. There is just a little limitation. The step length caused by the total clock and the number of steps in the pattern row must match the main clock! Now I can play based on the tracker method, and also based on the variable step length sequence method, which is really exciting! Thanks for designing nerd! Cheers
I’ve been doing some precise testing with CBPB clock FX and may have found a timing inconsistency that could be a bug.
Test Scenario:
• Pattern length: 4 steps
• Each step has CBPB 106 (clock divider /8)
• On step 4, I trigger a TRKx → SYNC to force track resync
• I start playback from a stopped state using Shift + Play, ensuring alignment with main clock zero-cross
• Expected total duration: 4 steps × (1 row /8) = 32 steps
Observation:
After about two full loops, I hear a clear stutter or “glitch” when the SYNC command is triggered. This implies that the pattern playback loop actually completes faster than 32 steps, despite the CBPB settings suggesting it should take exactly that long. The SYNC occurs before the expected main clock zero-cross at step 32, leading to an audible desynchronization.
Control Test:
When I perform the exact same test using a track clock divider of /8 (instead of CBPB FX), the loop plays back with perfect timing — every 4 steps take exactly 32 steps, and the SYNC aligns perfectly with the main clock zero-cross. There is no stutter or drift.
Conclusion:
This suggests that while CBPB FX are clocked based on the main clock (as documented), their implementation may allow the pattern to advance steps faster than expected, likely due to the playback engine continuing to step through rows regardless of trigger delay. That would mean CBPB affects event timing but not actual pattern step duration, resulting in loops playing faster than intended if you rely on CBPB to control overall timing.
Let me know if this is expected behavior, or if it might be worth reviewing how CBPB timing interacts with step progression and sync points.
Thanks as always for your incredible work — the system is genius!
As mentioned in the manual, the only safe use of CBPB 1XX is on the first step. If it is called on other step then it will always overrule current counting of the dividers/multipliers (dividers and multipliers are accomplished by adding or subtracting internal ticks).
Another thing is also that a SYNC appears on the mainclock zero cross, not a track zero cross which can be different. If you say 32 steps then I am not sure you mean the mainclock or just the current pattern.
In general, the CBPB change clock now 1XX command is only guaranteed to work 100% properly if it is being set on the first step.
CBPB 1XX change clock now in the first step with dividers caused sync issues in versions 2.0 -> 3.0 Will be fixed in V3.01
Hey folks (and Thomas),
I'm writing because I also always seem to have trouble with the CBPB 1XX function. I have read the relevant section of the manual and also the above posts, but still have issues with the things getting out of sync. I'm only using the CBPB 1XX on the first step of the pattern, but as soon as the pattern repeats things start to get out of sync. Calling CBPB 1XX multiple times, even if its always in the 1st row, causes issues.
My performance scenario is this: I have groups of patterns on multiple tracks that get played, looped, etc. At some point I stop the Nerdseq, perhaps have some transitional material, and then start a new group of patterns below the first to start the next piece. Sometimes I want certain tracks to have new clock divisions when restarting the sequencer.
Using CBPB OXX doesn't really work, because the new division doesn't start until the NEXT pattern. Using CBPB 1XX does work, but that pattern can never repeat, or else that track goes out of sync.
I guess I'm looking for the proper workflow so that I can start a new piece, with a new clock division right away, but without the sync issues cropping up if the pattern is used again or repeats.
Any advice?
(02-01-2026, 07:36 PM)kilgore Wrote: [ -> ]Hey folks (and Thomas),
I'm writing because I also always seem to have trouble with the CBPB 1XX function. I have read the relevant section of the manual and also the above posts, but still have issues with the things getting out of sync. I'm only using the CBPB 1XX on the first step of the pattern, but as soon as the pattern repeats things start to get out of sync. Calling CBPB 1XX multiple times, even if its always in the 1st row, causes issues.
My performance scenario is this: I have groups of patterns on multiple tracks that get played, looped, etc. At some point I stop the Nerdseq, perhaps have some transitional material, and then start a new group of patterns below the first to start the next piece. Sometimes I want certain tracks to have new clock divisions when restarting the sequencer.
Using CBPB OXX doesn't really work, because the new division doesn't start until the NEXT pattern. Using CBPB 1XX does work, but that pattern can never repeat, or else that track goes out of sync.
I guess I'm looking for the proper workflow so that I can start a new piece, with a new clock division right away, but without the sync issues cropping up if the pattern is used again or repeats.
Any advice?
Can you send me the project for this so I can reproduce it directly? It might help as well to find out if this is related to any settings. I was not aware yet about this issue.
(02-02-2026, 09:11 AM)XORadmin Wrote: [ -> ] (02-01-2026, 07:36 PM)kilgore Wrote: [ -> ]Hey folks (and Thomas),
I'm writing because I also always seem to have trouble with the CBPB 1XX function. I have read the relevant section of the manual and also the above posts, but still have issues with the things getting out of sync. I'm only using the CBPB 1XX on the first step of the pattern, but as soon as the pattern repeats things start to get out of sync. Calling CBPB 1XX multiple times, even if its always in the 1st row, causes issues.
My performance scenario is this: I have groups of patterns on multiple tracks that get played, looped, etc. At some point I stop the Nerdseq, perhaps have some transitional material, and then start a new group of patterns below the first to start the next piece. Sometimes I want certain tracks to have new clock divisions when restarting the sequencer.
Using CBPB OXX doesn't really work, because the new division doesn't start until the NEXT pattern. Using CBPB 1XX does work, but that pattern can never repeat, or else that track goes out of sync.
I guess I'm looking for the proper workflow so that I can start a new piece, with a new clock division right away, but without the sync issues cropping up if the pattern is used again or repeats.
Any advice?
Can you send me the project for this so I can reproduce it directly? It might help as well to find out if this is related to any settings. I was not aware yet about this issue.
Thanks Thomas. My actual project is a huge messy file, so I managed to recreate the issue in a simple project file with just a few patterns.
Actually I discovered something interesting when recreating the issue. Using CPBP 1XX on the first row when *multiplying* the clock seems to work just fine, the patterns stayed in sync even when the pattern repeats. I could only recreate the issue when *dividing* the clock. I think if you just play the project (all patterns are in the sample row) you'll hear the sync issue pretty quickly.
Found and fixed the latest issue. That will find it's way to the release candidate which is coming up soon.