05-02-2025, 01:39 AM
Update: After trying to use CALC SHTR, I finally got the answer. I realized that I couldn't get a table clock that was not synchronized with my variable clock. It turned out that I had always misunderstood the operation of nerdseq. I thought that when I set the clock in a step, such as a /32 step, it would stretch the number of ticks, that is, increase the interval of 6 ticks, but the fact is no. In fact, this step is still calculated based on the master clock tick, just multiplying it. So no matter what I do, the table tick will still be synchronized with the master clock. I think there are two possibilities to solve my situation:
1. I will make all the clock numbers into a table format such as div 2 1 div 4 1... and so on.
2. Just see if I can update the clock based on the length of each step in the future, that is, the length of one row.
1. I will make all the clock numbers into a table format such as div 2 1 div 4 1... and so on.
2. Just see if I can update the clock based on the length of each step in the future, that is, the length of one row.

