|
|
Post by admin on Feb 28, 2019 22:25:45 GMT
Please note that there is now a page on the tangible waves website that lists all discontinued modules for historical reference. www.tangiblewaves.com/store/c7/Discontinued.htmlThese modules are no longer in production and can't be ordered from the shop. |
|
pol
Wiki Editors
Posts: 1,349
|
Post by pol on Mar 15, 2019 12:17:18 GMT
I actually rather like the step 10 as it isn't stuck on 8 or 16 steps so varies stuff around normal, 4/4 time more!
|
|
|
|
Post by NightMachines on Mar 15, 2019 12:35:13 GMT
I actually rather like the step 10 as it isn't stuck on 8 or 16 steps so varies stuff around normal, 4/4 time more! It’s not though  You have a reset input, so you could patch the step 11 output into the reset to get 10 steps ... I think. I don’t own the TRIG164, but this is how the SEQ16 works and how those sequencers behave in general. You can even modify the step count dynamically while the sequencer is running, by using LOGIC, DIVIDERs or other modules that process gates or triggers. |
|
Lugia
Wiki Editors
Ridiculously busy...ish.
Posts: 556 
|
Post by Lugia on Mar 15, 2019 21:03:27 GMT
Yep, another thumbs-up for the Step10 here, too. While the Triq16 is more more akin to a "proper" trigger sequencer, the Step10 had some abilities that made it very suitable for clock modulation without tying up a Triq16 channel. I viewed it more as something like that: a variable clock modulator, which could send user-defined clocking steps on to another sequencer or two. It would also come in handy as a subsequencer for the 3VCSwitch, I think. I can see losing the other two discontinued modules, but this one might need a bit of reconsideration and revisioning it more as a "utility" or "clocking" module.
|
|
Lugia
Wiki Editors
Ridiculously busy...ish.
Posts: 556
|
Post by Lugia on Mar 18, 2019 12:26:35 GMT
After some rethinking (and waking up at about 5 AM with this on my mind), something hit me about the Step10...
It doesn't have to be used simply as a step sequencer. By patching it so that the TRIG out goes to the RESET, and selecting only one given step, you've then got yourself a clock counter, which can be used to establish metrical aspects for use elsewhere in a patch. For example, if you were doing something in 7/4, you'd only select step 7, do the patch above, leaving the other TRIG free to be multed elsewhere within the patch for restarts of sequencers, etc on the downbeat. The active step would then become your "one" beat, putting anything connected to TRIG in metrical sync. It should also be possible to chain Step10s to create longer metric values. But the upshot is that by having the Step10 along with the TRIQ164 and SEQ16, you can change meter on the fly by simply changing two switches on the Step10 to reflect the new metric value.
While the TRIQ164 also has this capability, that module seems to me to be more akin to a "proper" multichannel trigger sequencer, plus it has the ratcheting capability. The Step10, though, would still have some important uses as a "subclock" as noted above, which would relieve the need to use one of the TRIQ164's channels as a metrical control, which would also require several button pushes (in theory) to function in as direct a way as the Step10 in this different functionality. While the 2OSC and ENV are definitely now superceded, I don't think that the TRIQ164 is 100% the successor to the Step10; there still seems to be some very real reasons for keeping it in the active module lineup, and I hope that the choice to discontinue it might be reconsidered.
|
|
pol
Wiki Editors
Posts: 1,349
|
Post by pol on Mar 29, 2019 22:44:23 GMT
I actually rather like the step 10 as it isn't stuck on 8 or 16 steps so varies stuff around normal, 4/4 time more! It’s not though You have a reset input, so you could patch the step 11 output into the reset to get 10 steps ... I think. I don’t own the TRIG164, but this is how the SEQ16 works and how those sequencers behave in general. You can even modify the step count dynamically while the sequencer is running, by using LOGIC, DIVIDERs or other modules that process gates or triggers. You are correct, but the Step 10 does it without further patching.... I haven't used the SEQ16 on anything other than 8 or 16 steps yet, but have been varying what it does via the beat divider, good fun. Just need to compose around it now! |
|
You have a reset input, so you could patch the step 11 output into the reset to get 10 steps ... I think. I don’t own the TRIG164, but this is how the SEQ16 works and how those sequencers behave in general. You can even modify the step count dynamically while the sequencer is running, by using LOGIC, DIVIDERs or other modules that process gates or triggers.
