Some thoughts on future possibilities

[Zentrumsounds]

8. Clock multipliers that allow for different tupelos (triplets, maybe even quintuplets, septuplets. etc... but definitely triplets. I've searched forum for answers to this and have not found anything that works using multipliers. Groove for me is quite a slow solution.

I do triplets by SCLK /3 immediately (I think it is SCLK 103) or SCLK *3 immediately (SCLK 10D) and then using half or double the number of steps in the pattern. I got back to normal (SCLK 109) as soon as the triplet is finished.

This requires some extra care (and careful computation) when there are several pattern playing in parallel but it works. Though you may consider this too complicated.

Aha moment. Yes that's not hard at all. My XOR forum search of "triplets" just discussed some elaborate groove manipulation. This I can work with! (perhaps I just keep forgetting about the Direct version SCLK 109 versus the non direct version SCLK 009) Thanks.  

9. Okay this one may be impossible... BUT. How about an EVERY or MAX function that can supplement the generative side of things like probability? For instance, EVERY 6 would only play THAT entry every 6th pass. Or Maybe every even EVERY 0606 is every 6th pas and EVERY 0406 is a repetition between four and six times on every pass (just add a random between 0 and 2 to 4 every pass to determine when the next event takes place. Similarly a MAX entry could state that an entry occurs a maximum of N times (So MAX 0009 would mean the entry happens 9 times and then stops).

IIRC such loop counters have been requested repeatedly. My memory tells me the biggest problem with them is, that there is not enough spare memory to store these and no infrastructure to keep track of the loop counts. After all would that count for single patterns or would you want to allow repetition of islands? What happens when you jump between patterns. Does that reset the counter? Etc. pp.

Don't get me wrong:
I had asked for such counters myself. But I see that apart from the trivial cases they actually are quite complicated and I think Thomas more than once stated, that he does not see a way to implement them.

Kind regards,
Michael

Yes I had a strong suspicion that this one is impossible due to memory... hence my opening line on that one. There is no doubt already a massive memory commitment in the Nerdseq. But from a musical perspective an EVERY command would be SO useful. Otherwise it means perhaps sending out triggers to something like a Teletype and performing the EVERY and other logic memory hogs there. 

In fact do you know how one might dynamically change probability using the CV inputs? Can I route to FX 1 %?  

Many thanks,

Jürgen