Step by step book error in chaining_counter abstraction ?
Hi, I noticed an issue when trying to understand the 01_livestep_chaining_1 patch and the chaining_counter abstraction (p130-131). When playing a sequence of 32 steps (so 2 sequences of 16 steps) when passing from first to second sequence, the sequencer is not playing the first step of sequence 2, but instead it plays the first step of sequence 1 then goes straight to sequence 2 second step while skipping sequence 2 fist step. Any help would be appreciated, I notices a few errors in the book, and while I find it pretty useful to become a better programmer, I find this kind of errors incredibly frustrating and time consuming. Would it be possible to have a list of all the errors in the fist edition of the book ?
Hello,
Yes, the ordering is wrong. The step value is sent before the sequence change. Simple fix is to add a trigger after the number box to correct the order...
Many thanks !
Ok now I'm in 02_livestep_chaining_2 and another issue first step is always skipped and another step is added at the end (if I want to play 16 steps as 4 sequences of 4 steps, step 1 of 1 will be skipped and the patch will play a last step as the first step of a fifth sequence) I tried to replicate the solution from the previous patch without luck, the issue is still there. And why this trigger bang and this other trigger 1 are not routed anywhere ?
I mean for a beginner this is pretty confusing, is there a way to contact Gregory and ask him if a folder with corrected patches is available ?
Yeah.... there's a missing [- 1] before the counters maximum number inlet. Its there in the previous version of the abstraction on page 131, but looks like it got missed in this one. I guess the extra outlets on the trigger where there for testing (maybe the wrong pic got used for the book). There's an email for Gregory on page 270 of the book if you wanted to try to contact him.
Here's a working version (I think). I personally didn't like the buddy, or join though, they were causing lots of triggering that wasn't needed so I gots rid of them....
Thanks, your patch is working except for one thing, when switching toggle off it will play the first step of sequence 1 and when switching toggle on it will start to step 2 of sequence one and cycling as it should after that, I'm trying to find what the issue could be but no luck so far, any idea ?
Yeah... Turning the toggle 'off' is resetting the counter to 0 immediately, causing the counter to output a 0 which triggers the first step of the sequence. Turning the toggle 'on' also resets the counter to 0 immediately, which means the sequence starts from the 2nd step. Move the patch cord along one inlet to the "reset on next clock" inlet of the counter and that should sort it oot.
Working perfectly fine now, thanks !
I have another question, what is the purpose of the change object in your version of the patch ? (is it to prevent the same seq to be played two times in a row ?)
It just filters out repetitive numbers. The output of the [/16] will look something like 1.. 1.. 1.. 1.. 2.. 2.. 2.. 2.. 3.. 3.. 3.. 3.. (Depending on the sequencer settings).
Adding the [change] will mean it will only let a number through if it's changed from the previous number. (So the above would become 1.. 2.. 3..) It just removes repeated numbers, which stops any repeated triggering, and in turn, bombarding the live.step with unnecessary repeated messages it doesn't need (about which sequence to use/display). It will work without, but it's much cleaner with it in.
Also would probably be better if I put it before the [+ 1] not after.
HTH
That makes sense, thanks.