Just to clarify, by ‘temporary Chain’, I am referring to the scratchpad row.
If the Chain light is lit, you are in Chain mode. Pressing the Chain button will turn it off, but you will still be on the scratchpad row that contains the chain.
This can look as if you have another pattern cued but in fact you are still on the (now inactive) scratchpad row. Pressing Function and Chain (“New”) will create a new empty scratchpad row containing just the active pattern.
From here, patterns will cue and play correctly with CHNG.
There is most definitely potential for a doh moment after this, or perhaps a subtle thing or maybe it’s buried in the song edit stuff you mentioned, or possibly a gremlin that tidies up when a new project is launched
Either way, we’re all seeing different results, it’s not a mode I use to the point of good understanding so i’m hoping for that one little nugget of info that makes it all make sense, particularly for helping future peeps confused by the manual wording
I’m on 1.23. I really hope this isn’t something that was broken in the latest update. Patch notes only mention a fix for Direct Pattern Changes.
I’m updating now.
EDIT: OK it is “broken” in 1.23B.
As far as I can tell, the only way CHNG works in 1.23B is if Master is not set to INF. It works fine with Master <= 1024. (So long as you are not playing a Chain).
Support hinted at this during my exchange with @Ess in February.
@Ess said: “Pattern chaining with automatic switching does not work with a master LEN of INF. This is by design. If you would make it so that the CHG parameter dictated when a Pattern switches, you would either have a short pattern, or a long wait when you press cue. Neither of the cases are very good or flexible, so chaining is not supported with INF patterns.”
I don’t understand his point here but Master set to INF did allow CHNG to change patterns when cueing patterns before 1.23B.
Now it seems as if there is no way to move from a pattern with Master INF to another pattern. Neither Cueing nor Chaining/Song mode work in all Pattern modes (SEQ,DIRECT START,DIRECT JUMP). This is not the way I would want it to behave.
I just downgraded to 1.23 and it is “working” again.
Maybe @Ess can step in with the official word when he gets a chance.
I don’t have a Rytm but you probably don’t want to downgrade it below 1.3 anyway, because that’s when the new machines were added wasn’t it?
I’m puzzled by why this change was made. It seems at odds with the original intention of the CHNG parameter as stated in the manual:
CHNG controls for how long the active pattern will play before a cued or chained pattern will begin to play. This setting is important when for example LEN is set to INF.
That quote seems to be a bit out of context. It only refers to an inquiry about the Chain/Song Mode with INF patterns, and perhaps external sync, correct?
CHNG is there to use sequential pattern switching (cueing) with patterns of infinite length. Chain / Song Mode needs to have a finite length to work.
Just a direct quote from the manual, from the page @avantronica screen-grabbed above. The manual needs updating, as you said in February.
I wish CHNG would work with Chains/Songs but if it is at least fixed to how it was in 1.23, I’ll stop complaining
EDIT: Ah - sorry Simon - just realised you were referring to the quote I attributed to you rather than the quote from the manual… It was from Ticket #11702, for reference. Thanks!
Just pulled a bit of hair out as I was explaining to someone what Change length does and how it can be used for chaining patterns as well (like on the Digitone takt syntakt)
But nope, it does not. Only for cuing.
But still, in the manual is written the following:
CHNG controls for how long the active pattern will play before a cued or chained pattern will begin
to play. This setting is important when for example LEN is set to INF.
I’m surprised that this is still not fixed in the current firmware (or added if it’s not a bug)