04-06-2021, 02:40 PM
(04-06-2021, 01:56 PM)mgd Wrote: Ok.
I think I've adjusted my understanding of how clocking of tables works [enough] to make things work the way I want them to work. Except for the realization that all tables share their position pointer. I honestly had thought they are independent and considered that part of the power of SPFX 011.
I still think that individual position pointer per table would be an extremely valuable addition as it allows for all sorts of evolving patterns to happen (and I could get rid of all my external 8-step sequencer... tables are more powerful anyway). And it would turn tables into real sequencer inside the sequencer.
The concern w/r to added complexity IMO could be dealt with by providing extra commands to move the position pointer of a particular table, possibly add a "reset all table pointers to 0" command (for SYNCH). The current SPFX 011 command would then be renamed to "increment all table position pointers" (or something to that end), i.e. all existing stuff remains unchanged.
I understand that the existence of complicated functionality will also lead to people trying it and being frustrated by "it not working the way they think it should". I do hope that this could be prevented by proper documentation. If it would help convincing you to make that happen I'd certainly be willing to write up use cases and example HOW TOs for this. Basically along the line of the stuff I wrote in this thread (w/o the mistakes due to me not understanding how things work)
Kind regards,
Michael
I think one pointer per table (per track...each track got it's own pointer of course) is really already complex enough to handle. Also the tables in general are a powerfull tool, combined with FX etc they are endless possibilities. Also regarding to the accumulate effect, something like that can be done. Not exactly, not everything. But parts of it and much more beside it. There is actually one little thing I added to the FX with the latest Release Candidate and that is that MOD and CV are not only pitches anymore, but can now also be notes. This includes now also notes into the +-*/ functions (and these also with or without the use of tables).
As for the rest, I had second thoughts about the Accumulate functions in the Metropolix and I don't think it will be high on my 2do list. I understand the enthousiasm when a new sequencer comes out which has function X or Y. But the NerdSEQ is it's own thing and the concept is totally different and this is definitely not a killer feature but more a tool to make limited loops more interresting (no offense to metropolix, I really like what I see and for what it is it is top). The NerdSEQ is able to make complex sequences and generative things are added more and more.
And there is still enough to come on my list which is more interresting for the NerdSEQ ecosystem and for the sequencer in general.
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!


)