12-21-2023, 03:36 PM
(12-10-2023, 08:05 AM)XORadmin Wrote: Right if you use CV in as a value then you would send 4095 clocks/triggers to the track if for example 000/FFF would be the result.
What you need to do is have the CV input in one row and in another row a function which would take care that for example only 0 or 6 is being send (6 clocks/ticks which would match a normal groove)
One option would be the pass command:
Code:CALC PASS 00=6 > TRK TRK1 TICK
Where 00 is the row of the CV input.
This would then send 6 ticks once the CV goes high.
I have a strange problem when using this that I'm not sure how to debug. I can successfully get an external gate/trigger clock signal to advance each step of the pattern whenever it the CV goes high. I do this by setting the mapping as described and setting the track clock to "mapping". However, for some reason the CV *outputs* are then all disabled (i.e., they stay at their previous value and don't change), and the advancing does not respect any breaks that I have in the pattern (i.e., I have a break at step 16, but it ignores that and just goes all the way through to step 64 and then returns to step 1 again).
So, to summarize:
* I can create a pattern that is clocked internally and outputs correct CV and respects the breaks that I put into the pattern.
* I can create a mapping like described above to clock each step of the pattern using an external trigger to CV input 1.
* Once I change the track clock on this track with this pattern to "mapping", the steps are advanced correctly for each external trigger received, but the CV outputs don't function anymore (they remain at whatever level they were before switching to "mapping") and any breaks in the pattern are ignored.
* If I then change the track clock back to "normal" the CV outputs and breaks are respected.
Has anyone experienced this and have a solution?
Thanks in advance for any suggestions!

