04-06-2021, 12:04 PM
(04-06-2021, 11:35 AM)mgd Wrote:(04-06-2021, 11:06 AM)XORadmin Wrote:(04-06-2021, 10:52 AM)mgd Wrote: I tried to insert SPFX 011 while tables 01 and 02 were playing and removed the SPFX 011 at the end. That results in table 01 and 02 skipping every other step. The HP 00 is still not executed.
Are you really sure the project does what it should and that the tables are indeed working correctly?
How could I make the HP 00 in table 01 and 02 to get executed?
From what I see any SPFX 011 moves tables 01 and 02 forward no matter what. I do suppose the same is true for table 00 but since that does nothing I can't tell.
[I want an SPFX 011 that specifically targets a table and possibly incr/decr the current position in the table by more than 1, but that is for a feature request once I'm more comfortable with the tables.]
Kind regards,
Michael
When table 00 is for expample set to Table Step 3 and you switch to Table 01, then 01 is also on step 03 if in loop mode (or step 0 if resync). There is no own table counter for each possible table in each track. So the behaviour here is right. No HOP is executed because always the SPFX 011 is happening when table 00 is active.
Have you actually tried to run the project?
Also may I point you towards a test I made:
(04-06-2021, 10:52 AM)mgd Wrote: I tried to insert SPFX 011 while tables 01 and 02 were playing and removed the SPFX 011 at the end. That results in table 01 and 02 skipping every other step. The HP 00 is still not executed (at least not that I realized it)
I'm not sure that what I do is correct, but the tables don't behave the way you describe they should... or I simply don't understand you.
To be clear:
I think they almost behave the way I expect them to. My only issues are thatCurrently my understanding (based on my experiments - may be completely wrong) is
- HP 00 is not executed and I have found no way to do so
- the initial setting of the tables is executed twice, i.e. it seems the first SPFX 011 initializes all position pointer (or however you call them) to 0 and thus results in table position 0 being executed twice
- all tables set to SOURCE PTN-SFX share a position pointer, i.e. they are not "moved"/played independently [I would want them independent --> possibly feature request material; required for Accumulate like functions via tables and useful for all sorts of generative music]
- HP 00 [possibly HP in general but I have not tested that] is ignored for tables set to SOURCE PTN-SFX
Basically I wish to understand what's happening and why
Kind regards,
Michael
Yes I did try your project before I answered in the first place and I don't see any issue with the sequence. It behaves as I expect it to.
Tables in a Track share 1 position pointer and that will stay like this (so I don't give independent pointers a big chance, since I think they are hard to manage by users and understanding a sequence would be impossible. It's now already difficult sometimes). If you switch to another table, the pointer doesn't change except for if you set it to resync. A new step is executed in your case with the SPFX command. In your project when this command is being executed it never plays table 01,02 or 03. (you can see the active table for this track in the pattern screen).
- HP 00 [possibly HP in general but I have not tested that] is ignored for tables set to SOURCE PTN-SFX
It works as advertised and executes the HOP. I just tested that.
- the initial setting of the tables is executed twice, i.e. it seems the first SPFX 011 initializes all position pointer (or however you call them) to 0 and thus results in table position 0 being executed twice.
As with clocking in general, a step is executed when a tick/clock is happening. With the table you use, there is no clock in the first place but the first clock comes on step 14 which is then also the first execute. They are also fine here.
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!

