The question is not at all clear as to what you want... are you saying the assignment to automate the Super Knob is some how easier than automating some other functions. You realize in order to physically move your two Foot Controllers would require some kind of motor and possibly hydraulics 🙂

Of course, you assign the parameters, not the physical controller, itself. Don't mix up the fact that you can see the automation of the Knobs as something other than eye candy. Seeing the foot pedals actually move would be a bit scary, no? (And impractical to pull off).

Motion Sequences can be applied to most any parameter(s) you can dream of, sorry, the light show given by the Super Knob and its Assigned Knobs is rather unique to it.

What do you wish to automate?

i dont find also a way to change the source of modulation control without losing the settings.

Move the cursor to the box labeled "Source" - you can change the source of the modulation without losing your other settings.

Although there may be specific controllers Natalini would want to target as destinations, I imagine the crux of the suggestion / wish is that controllers share the ability to act as destinations in a similar programmatic way as super knob - not that there be LED indicators for the position. Also, when you set super knob, through automation, to move to various positions - the encoder's rotational axis itself does not move - so moving the controllers physically is certainly not what is being called for here.

What's the full list of desired controller destinations, Natalini, you are requesting to add as destinations?

I would imagine the list would include FC1, FC2, Ribbon, Mod wheel, Pitch bend, possibly Assign 1 and Assign 2 switches. Since ribbon has a mode where it "snaps back" to the center - this cannot be supported with RB as destination and must assume RB=hold mode. Same with pitch bend. Maybe neither of these two are in the OP's list of desired destinations.

I could only see this useful for automating presets - as this would minimize the amount of programming needed to automate control of these performances. If you're building a performance from scratch - than this kind of automation is not going to help reduce the workload (on the user) since you will have to assign destinations to the controllers as well as associated the controllers as destinations to MS Lane sources - which is actually more work.

Since FC can already be assigned to super knob - I'm also assuming this request does not involve linking any controller to the assignable knobs.

Now if automation of a controller such as mod wheel or pitch bend would also send out the associated MIDI CC message - then this would indeed extend the capabilities past what is currently available for external control (not just be a "lazy" way out of assigning destinations using the current list of possibilities).

i found nice way to use physical controllers, specially the foots, for shaping the sound during the play
but then if i like to reproduce some of these moves i discovered within the motion sequencer,
i have to reprogram all settings,multi assignations, curves and so on. pointing the MS
directly to the controller will have avoid this. in fact just the ability to copy and paste a whole setting.

but of coarse the geek inside me would like a second super-knob showing his hypnotic light linked with another foot.
two feet, two super-knobs:D , that make sense

... thought about the request a bit more and have the following to add:

Another use for this would be destination conservation. There are only 16 destinations. If you want the RB, mod, etc assigned as sources for manual control (say when MOTION SEQ=OFF) but want automated control (MOTION SEQ=ON) as an option for the same performance - then currently you need to replicate the destinations for both the physical controller and MS Lane (causing using more destinations). I'm not aware that "source" can be anything other than a single item in the destination/source assignment screen. If, say, mod wheel was assigned to 8 destinations - then for automated control - an MS Lane to control the same things as mod wheel would need to have 8 destinations for MS Lane. This just "ate up" all your destinations since destinations is a very limited resource.

If MS Lane could be assigned to mod wheel as a destination, then this would only "consume" one destination rather than 8 (saving 7 for other assignments).

Not sure how wide-spread the need to do the above is. It represents a certain amount of value-add in the face of limited destination resources. Another fix would be to increase the destination count so consuming destinations is not so much of an issue.

the MS pointing directly at a controller like it does for the super-knob is the elegant way, less consuming i suppose? it is just a routing.

No, I don't think it is, "just a routing". The assignment capabilities here are by no means limited in the sense you can't making interesting music. And you are mixing up Sources (physical controllers) with Destinations (parameters). I hate discussions like this because they really go no where and are very self defeating. Try making use of what is available before you run into these supposed limitations that are really not limitations at all. Because your Foot Controller is assigned to multiple destinations, you want to assign something to move the Foot Controller... I contend that is not a parameter you should be looking for, you should be looking at the appendage just below your ankle! 🙂

Post a program and show us how you are prevented from doing something musical because you don't have enough Source/Destinations in this control matrix.

i think at this point that you don t read enough my post , i wish you are busy.

''to reprogram all settings,multi assignations, curves and so on pointing the MS
directly to the controller will have avoid this. in fact just the ability to copy and paste a whole setting.''

and i never speak about ''there are not enough assignations'', at the contrary it is all about economics ergonomics and routing.

You did say "pointing the MS directly to the controller" - this shows that you don't think of the Motion Sequence as a Controller. Please think of it as a Controller, because that is its role in Montage.

Controllers are Sources
Parameters are Destinations

Sources are PB Wheel, MW, Ribbon, Aftertouch, FC1/2, FS, BC, AsSw1/2, AsgnKnobs 1-8, MS Lanes 1-4, Envelope Follower (1-16, AD, Master)

thank for answer but i was just asking if there was or would be a way to copy a multi targets setting of a controller into another controller for avoid to do it manually, then come the Motion sequencer , a controller able to point to the setting of the super knob controller. so why could it not target the setting of any controllers ?

So it's clear - you want to "copy" all assigned destinations for one controller (say for example, ModWheel) and assign all the same destinations to an MS Lane (say MS Lane 1) - AND leave both the ModWheel and MS Lane connected to the same destinations? Or do you want to -move- the destinations from, for this example's purposes, from being assigned to the ModWheel over to being assigned to MS Lane 1?

The difference here is if the original controller is still assigned to its previous destinations or not.

Right now, moving (as opposed to "copying" = leaving previous assignments to original controller) is supported by tapping on the touchscreen "Source" and picking one of the MS Lanes (or anything else) from the list. This will -replace- the previous source controller with the newly selected controller. If there are 16 destinations assigned to the previous source - all 16 destinations will move to the new assignment.

BM - no confusion here what a source vs. destination is and how the architecture works. I gave some musical examples for why someone may want to use this unsupported feature citing both a local control and external control use case. Other threads I have commented on how one may run out of 16 destinations without referencing multiple sources for the same destinations - and here noting how if multiple sources were desired - then you would "eat up" destinations at a 2x rate in the MS Lane-as-a-source-plus-physical-controller example.

Natalini - part of the issue of having controllers as destinations is that you'll notice all destinations have a limited scope in that they, at most, affect a single part. There is no cross-part destination as the whole destination engine is pointing to items within the part where the destinations are assigned. I could see something like controlling the sustain pedal would be an interesting effect - but sustain is a global (not part level) controller. It affects all parts that do not ignore sustain from a midi control on/off "box" setting. So such a change would be a departure from the current architecture which is going against the grain and not likely to make it past the 1st line of feature request filters no matter what justifications are made. In this example, however, one could use the existing parameters to turn on/off sustain by using the element AEG release parameter on every part to replicate what a sustain-as-a-destination would otherwise do.

BM - are you sure that multiple destinations will all change to the new source setting? I didn't see this in the firmware release notes as a change. What I see is that only one out of the multiple destinations (the selected destination) "follows" the source when you change the source setting - not the complete list of destinations.

It may help to speak in specifics also. Follow me:

1) [CATEGORY SEARCH] - search for "Rd Soft Touch Wah" and select this preset performance
2) Touchscreen (TS): Press part 1's name and select "Edit" from pop-up menu. This performance has only one part.
3) TS: Touch "Mod/Control" -> "Control Assign" menu
4) TS: Make sure "Auto Select" in upper-left of screen is green (turned on)
5) Press [ASSIGN 1] button (switch) - this should now show on the touchscreen "AsgnSw 1" in the "Source" box.
Note: notice how there are 4 destinations. I picked this performance because there are a lot of destinations assigned to a single source.
6) TS: Press the "Source" box - a popup appears with some (not all) of the possible sources listed. Not all are listed because the mode is to display a single "page" of the options. To expand the list, press the lower-right icon that looks like:

= = = =
= = = =
= = = =

This will show all options
7) TS: touch "MS Lane 1"
8) press the [ENTER] button

Notice how the MS Lane 1 source now has one out of the 4 total destinations assigned. The other 3 are still left assigned to the AsgnSw 1 controller.

Note for Yamaha: Maybe a "job" button which allows selecting all the destinations - or simply just copying over all the destinations (not just one) when the source is changed would be more appropriate.

When you change the source, you lose settings, no copy function ?

When I change the source - one destination is moved (not copied - I consider a copy would keep the original assignment of the destination copied and also replicate this destination to its new, "copied" source assignment) and the rest are left behind.

The expectation would be changing the source would move all destinations assigned to the original source or, "ok" but not as preferred: provide a mechanism to select which destinations should be moved in a "job" type workflow. Neither of these expectations are met with the current experience here. Instead, the behavior is as summarized in the above paragraph - or detailed in the previous post.

The 8-steps to follow is a fairly short list - so you can take a few moments to run through them and arrive at a conclusion from first-hand usage.

To change all Destinations to a different Source, you can simply re-assign the Control Number. If you wish to change multiple assignments from the AsSw1 to the FC1, for example, change FC1's CONTROL NUMBER to match AsSw1 (cc086). This turns the FOOT CONTROLLER into the Assign Switch 1.
Press [EDIT]
Press [COMMON]
Touch "Control" > "Control Number"
Since Controller assignments are per Performance, you can use this to quickly reprogram all Destinations to the Source you desire.