even if I activate the asgn1 and asgn 2 keys and store my performance, when I recall the performance later, I see that these assignment keys are not active.

You'll need to tell us exactly what you did to 'activate' those two assign buttons.

Are each of them set to 'Momentary' or to 'Latch' on the Common Audio General tab?

Did you use either of them as the source of a control assignment? If so, how?

We can't tell you what you did wrong without knowing 'what you did'. You also never told us if we solved your portamento problem.

I use asgn 1 and 2 of the preset as it should be in the latch setting. I activate element 3 and element 4 with asgn1 and 2 respectively by switching the asgn keys to on mode. I want element 3 and element 4 to be active when I call the preset in live mode.

You also never told us if we solved your portamento problem.
-I have not yet been able to answer my previous questions because I have just completed the instructions. Thank you for following.

The Assign Switches will always default to OFF… this by specification. And is very normal.

What you do is set the target parameter exactly as you want it be when the Performance is recalled., and that means is you must program the action of the switch to be opposite.
Turning the switch On, will defeat the function.

In the example below, the Assign Switch is assigned to control an Insert Effect.

Extra Credit:
Recall Performance “Vintage’74” — classic Rhodes Suitcase sound - with Auto Pan.

Notice the Auto Pan is stored so it is there when you recall the program.
Press [AsSw1]
Notice this turns the Auto Pan = Off

This is what I mean. Here’s how to see where this is done

select PART 1
Press [EDIT] > “Mod/Control” > “Control Assign”
Find and activate “Auto Select” (green)
Tap [AsSw1]
You will be taken to the assignment screen.

Notice this has a ramp going down — turns the parameter down or towards off
This is done with the negative RATIO (-20)

The programmer here set the sound exactly as they wanted it to sound when it was recalled, and they reversed the application of the controller so that it is an OFF-ON a switch, rather than an ON-OFF switch…

Every controller (MIDI spec) will have a default setting… that is, it will normally *reset* to a specific value; usually
0 / Off — like MW
127 / On — like FC
64 / Center (+0000 in the case of PB)

See Data List booklet for Controller Resets.

Hope that helps.

Of course I will. I just wanted to know if it was possible. Thanks.

The Assign Switches will always default to OFF… this by specification.

I believe there may be a CAVEAT related to that. My tests on a Modx show that what the switches 'default' to depends on the setting of the Hold/Reset (Controller Hold/Reset) parameter on Utility - Settings page.

I'm referring to page 192 of the Reference doc.

Hold/Reset (Controller Hold/Reset)
Determines the status of the controllers (Modulation Wheel, Aftertouch, Foot Controller, Breath Controller,
Knobs, etc.) when switching between Performances. When this is set to “Hold,” the controllers are kept at
the current setting. When this is set to “Reset,” the controllers are reset to the default states (below).

The table below the text does, indeed, show that the 'default state' for the assign swithes is OFF.

But, unless I am wrong, they will NOT 'always default to OFF if the Hold/Reset value is Hold. And my tests show that the setting for the Hold/Reset parameter is saved when the power is turned off. So that once set to HOLD it will always have a value of HOLD until manually changed to RESET.

Have I missed something?

when I recall the performance later, I see that these assignment keys are not active.
. . .
I just wanted to know if it was possible.

Yes - it is possible.

But you need to set the Controller Hold/Reset value to Hold on the Utility Settings page.

See page 192 of the Reference doc.

WARNING #1 - that parameter affects ALL of the controllers listed in the table on page 192 - not just the assign switches.

So if you use HOLD then NONE of the controllers will be reset when you change performances.

WARNING #2 - the setting of HOLD will be saved when you power down. So once you set the value to HOLD it will always be hold until you manually change it to RESET.

That can cause future problems if you forget you use HOLD for some gigs but not for others and you forget to change the setting back to RESET for the other gigs.

I believe there may be a CAVEAT related to that. My tests on a Modx show that what the switches 'default' to depends on the setting of the Hold/Reset (Controller Hold/Reset) parameter on Utility - Settings page.

Well your tests are spot on. The default resets, that I mentioned, are MIDI-wide… meaning, not just your MONTAGE/MODX/MODX+.

The HOLD/RESET parameters you have just discovered are a ‘local’ feature found in the Yamaha synths. That is not necessarily a thing you would find in every MIDI instrument.

Hope that difference is clear and helps with your understanding of this topic.

Extra Credit:
The reason that manipulating the Controller Hold/Reset option is not a solution is because the Switch would remain wherever it was left last (instead of resetting) the idea of recalling a program when you’ve programmed controllers is to *know* (like, for absolute sure) where the controller is going to start out.

Those who set the Controller RESET to “Hold” typically do so to avoid purchasing a standard Stereo Volume Pedal that would go between the synth’s Main L/R and the sound system (which provide a foot controlled ’master’ VOLUME). It allows them to work with their FC7 as a “live” volume control. Useful when you want to manually control overall volume without depending on the stored volume.

It does indeed affect other controllers, as well — no need to worry about Pitch Bend since it has a spring that automatically RESETs that controller. But if you are holding PB in place and you change programs, the pitch will Hold.

You can bet these folks quickly learn to be very careful about retuning the MW to minimum, every time! Because if you leave it up, whatever the MW is programmed to control will be offset to whatever should be applied at that position.

The reason it is not a solution, the Switch would remain wherever it was left last (instead of resetting) the idea of recalling a program when you’ve programmed controllers is to *know* (like, for absolute sure) where the controller is going to start out.

LOL!

That, of course, just begs someone to ask one of those WHY questions that can never really be answered: why not let the performance/program dictate the value if you've programmed it rather than allow a common utililty setting to override what a performance has programmed?

Not asking that question myself since it is what it is. Just pointing out that no matter which way it worked someone would find fault with it.

Yamaha might consider adding a Controller HOLD/RESET option to performances saved in a Live Set.

I consider Live Sets to be a place to create a collection of performances that are used together. So, for me, it makes sense to have COMMON Live Set parameters especially for the controllers. Maybe even indepedently for each controller.

Fits into the hierarchy:

1. Elements share a 'Common' area at the part level
2. Parts share a 'Common' area at the performance level
3. Performances could share a 'Common' area at the Live Set level

Another one for IdeaScale.

Not asking that question myself …

If you were, some people use the keyboard simply, others have almost impossibly complex setups within their MONTAGE… most are somewhere in the middle…

If you have an easy gig where all you need is a piano (no need to design and designate a different one for each song) and access to an organ sound, and a few lead sounds… which you will recall and play individually. You can see why this person doesn’t want to take the time and pre-balance the volumes, and tweak a thousand details… etc., etc.… they just want a real-time volume that they can control with their foot, so that when they switch sounds they have volume immediately under their control.

That’s why you’re given a preference in UTILITY to configure *your* instrument.

Also you seem to be discounting this fact: Of all the parameters that you program in the creation of a Performance, there are but a scant few that are directly impacted by the Controller Reset/Hold issue… Volume (of course) this is the big one. Those that are impacted by received standard MIDI messages are vulnerable… if you are connected to an external device that has a stored Volume message (cc7) that it broadcasts, this will impact your Performance.

And you are absolutely right — you cannot please everybody! You hope they ‘get out’ more so that they can recognize how many different ways people work. Just because one person can’t use the Arpeggiators, does not mean others can’t find it a compelling assist in composing music. Different strokes for different folk… you just would think they could at least imagine that someone else might actually work completely different from how they work.

That is one of the problems with writing a tutorial, it becomes ‘the way’ people think the *have to* work. It’s not, it is one-way that you can work.

However, those who do dare to experiment will discover many different ways to approach solving a problem and may find a completely new way to work.