Hi, I also received a very kind but unsatisfactory answer:
Thanks for the report. If a pattern in a chain or song has length set to INF, some user action is needed before the CHNG parameter comes into effect (i.e. manually selecting the next pattern in the chain). This is by design but I will discuss this with out developers.
(my consideration) It is assumed that one creates a chain to create automatisms that avoid having to manually select the patterns and that the CHNG parameter is there to replace LEN set on INF to define when the next pattern in chain should be activated, as a user I think this is the right operation, otherwise there could only be the LEN parameter and no need for a CHNG.
Having also pointed out what the manual reported, I was answered:
I’m sure this is how it has been designed, and the manual is not accurate on this. I have discussed this with our developers many times over the last year but will report again since apparently many users considers it to be wrong. However, I can’t promise that it will be changed unfortunately. It is not considered a bug.
it is also possible that LEN and CHNG actually work this way, i.e. set LEN to 64 but CHNG to 16 so if the chain is active the x pattern lasts 16 and then changes and if there is no active chain instead it lasts 64
The real problem is that CHNG does not work in any case! I have the rytm in front of me, I just tried this: pattern A1 LEN 64, CHNG 16, pattern A2 LEN 16, CHNG OFF. With the chain mode activated, the pattern A1 play 64 and then changes, therefore the CHNG parameter does not work precisely because after 16 the A2 pattern should have been activated, and this will report it immediately