Hi Lothar,
Thanks for the question.

Scenes do not have a memory switch to memorize the Assign Switch status.

Assign Switches 1 and 2 generate cc86 and cc87 messages, respectively, by default. Pressing these buttons while recording is documented in the Track like other controllers that you directly physically manipulate.

Also the Length of a recorded Track is individually programmable prior to recording it, maximum Length is 256 Measures.

I’m not sure of exactly how you have your Assign Switches set to behave. They can be latched or set for momentary behavior. When set to momentary, the On status (127) is immediately followed by the Off (0) as soon as the button is released. However, if “latch” is the set behavior, like most MIDI commands, the last value sent will persist until a message to change its status is received.

The Assign Switches, like all physical controllers that generate cc messages, will default to a specific initial condition. Assign Switches default to Off... they cannot be stored in the On condition, they reset to Off when initially recalled. Like most controllers, the initial value is known, MW, for example, will always reset to 0 (minimum) while FC will always default to 127 (maximum), and RB to a Center value.

Also like all cc managed and physical controllers, the last value sent will persist until a new message is received to change the value. This means if you activate AsSw1 by pressing the button, it will remain on in the next Scene, unless there is a message in that Scene to tell it to change.

What you do when you want something other than the default reset, is program that parameter so that the default for the controller recalls the parameter value you desire. If, for example, you desire the AsSw1 = On condition as the default, you must reverse the programming so that AsSw1 = Off recalls the condition you desire.

If AsSw1 On is Rotary Speaker = Fast, because AsSw1 will always default Off (Slow), if you would rather Fast be the initial setting... simply reverse what pressing the button does. Set the Rotary Speaker to Fast, and have the application of switching AsSw1 On, do the reverse, switch it to Slow.

Once you record a cc message into a Pattern Scene the most recent value will remain until a command to change it is received. CC’s do not reset between Scenes, only when the program is initially recalled do they reset.

Hope that helps.

Lothar,

Assuming scene (blue) buttons ...

There are times when I'd wish I could save A.SW1 and A.SW2 to a scene. This would also be a way to change the default (upon Performance recall) of these switches since there's such a thing as a default scene and the scene settings we do have can override defaults (like superknob) since the scene setting is respected.

The only controller scene buttons can save store a state of is the super knob. So whenever I "wish" I could save the assignable buttons to a scene - what I do is reconfigure the assignable switch to the superknob through an assignable knob. This works as long as the assignable switch is not for XA control. Because XA control can only be assigned to A.SW1/2 and cannot be moved to any other controller.

In cases where I want to have a scene button "press" the A.SW1/2 button(s) because I want to use this for XA control - I sometimes reconfigure from using XA control to using element levels or PART levels instead of XA control. Which works for "on/off" type - and not for legato or key-off type XA control. And also this can still "eat up" polyphony - so it's not a best choice - but something I would sometimes do. Another option I have, if I'm not already using an ARP, is to setup a control ARP that presses A.SW1, A.SW2 (or both) - either ON or OFF (there isn't a MIDI command to "toggle" - meaning take the current state and invert it). With an ARP - I can have the scene button change the ARP. The ARPs can be setup to loop and "constantly" run from the first keypress of a tune - so changing scenes should more-or-less "instantly" change the ARP number to another one that "presses" an assignable switch differently than the previous scene. It's a lot to setup - but an option. And doing this would conserve polyphony and also keep from making major control changes - shifting the burden to ARP creation, parameters, etc.