There could be a problem here - but this could also be one of the consequences of how certain features are intended to work.

Sliders ...

If expression MIDI receive is turned turned off for a given Part then sliders will effectively be turned off for a given channel.

Sliders that impact volume if you have an offset as part of the motion control matrix set to "peg" the volume level at a low or high value it may be possible that the sliders cannot change the volume because there's an offset that pegs the value to a certain point and there's no way out (unless you can find the controller that's the source controller for this value and change the value such that it does not override ability of the slider to change the volume).

This kind of "pegging" of the value can happen to not only sliders but other things too.  I don't have a Montage M so I can't hands-on walk through these Performances on your kind of instrument.

What I would do for sliders is look at MIDI receive and just inspect Exp/Vol and see if that's turned on or off.

Then I would (for sliders and everything else) go to the Modulation/Control (Mod/Control or Mod/Ctrl) menu and look for destination parameters that match whatever it is you're trying to change with a controller or quick-edit.  See what the source controller is for this destination parameter and then alter that source controller (mod wheel, assignable knob, ribbon, etc.) to reduce the value as close to 0 as possible.  In order to really do this, you have to understand enough of how this system works so you know which way to turn the source controller knob or where to press on the ribbon or ... 

Understanding how this system works goes a long way to solving a lot of unexpected problems you're going to run into and also informs more of how you can use this to own advantage when programming custom Performances.

I guess it would probably be a good feature request as an assist to the uninitiated to be able to "turn off" Motion Control so nothing gets offset just to be able to clear that hurdle and/or prove to yourself that motion control is the thing that's more in control than what you otherwise expect should be.  And then one would just have to contend with the ability to disable controllers which is the only other thing I can think of that would be, properly without a bug, impacting your experience.

... if you wanted to, as an experiment, "turn off" motion control then you would go to the Preset Performance's Mod/Ctrl page and delete all of the destinations.  No need to [STORE] this since it's just an experiment.  And see if the sliders/other controllers work how you expect or not.  Ignore the sound that's produced because now there could be something "off" due to the deletion.  But otherwise it would tell you motion control is the thing that's causing the behavior you're experiencing and also would inform you it's not a bug but something to learn about how that system works.

To Yamaha - not for helping with this ...

... and, since this comes up so much - if that is the issue - then it'd (again) inform Yamaha that there may be a better way to present what's going on to a user in order to make use of the system more intuitive.   My request in the past was to have the offset value be displayed in some different color when it's an offset that is non-zero with a "button" on the screen to allow showing the programmed value.  And I guess if you're showing the offset values then perhaps have a way to press the value and drill down to the 1st destination that offsets this value or otherwise "wormhole" to the Mod/Ctrl menu with all destinations of that parameter shown (filtered).   Maybe even pressing the [CONTROL ASSIGN] button and clicking on a parameter on the touchscreen will do a control lookup (reverse assign).  Just spitballing.

Back to trying to help ...

It hasn't been lost that there may really be bug here.  I'm not railroading here.  Just wanted to see if we can clear the deck of the top misconceptions that have come up when dealing with some of the more tricky parts of this instrument.  And then go from there.

Everything is working as designed. Thanks for posting the details, and the specific performances, for what you are asking about.

Before reading the below just let me say that whenever you have an actual problem or issue you need help with the more detail you provide (like you did here) the easier it is for someone to help.

At least the following performances are affected by this issue: Wr Ballad, Slow and low, Hot E.P. Noodles.

Either 'CC' or 'Vol/Exp' is set to OFF for one or more parts in ALL of those performances. See p.301/302 of the Operation doc

CC (Control Change)

Sets the transmission and reception of Control Change messages on or off.
Settings: Off, On

Vol/Exp (Volume/Expression)

Sets the transmission and reception of the Volume setting on or off.
This parameter is not available when CC (Control Change) is set to Off.
Settings: Off, On

 

Take a look at the 3 perfs you mentioned and check the 'Mod / Control-> Tx / Rx Switch' screen as shown in the graphic on p.301.

Wr Ballad - for part 1 CC is OFF so NONE of the switches shown on the doc graphic will apply. For the other 3 parts the CC is ON but some switches are OFF

Slow and low - for part 1 CC is OFF so NO switches on the graphic apply. For the other 2 parts CC is ON  but some switches are OFF

Hot E.P. Noodles. - for part 1 CC is ON but Vol/Exp, MW and Sustain are both OFF. The other parts have Vol/Exp ON but some other switches are OFF

-----------------------------------

NOW SOME BAD NEWS!

-----------------------------------

You can expect to find 'gotchas' like this in many of the presets. For the most part the presets are designed to showcase what the instrument is capable of doing.

This means you can't necessarily just grab one 'off the shelf' and expect it to work the way you want/need it to. Maybe it will but more likely it won't.

HARD FACT - Every performance has been intentionally configured by a user/musician/human. Not talking about the OS code - talking about all the many things that a human can create a performance to do.

The configuration/programming it contains will control: WHAT it can do, WHEN it does it and HOW it executes what it is designed to do.

If you find it isn't doing something or isn't doing it the way you think it should it that is a STRONG indication that the programming hasn't been programmed to do that or to do it in the way you expect.

Many of the preset performances have left-over programming that isn't actually needed or used. The sound designer might have been testing something and just left it in there rather than delete it.

-----------------------------------

AND SOME GOOD NEWS!

-----------------------------------

We recommend developing your own workflow to minimize having problems in the future, especially with performances you have already found issues with:

1. Find a preset you want to use as a starting point for building your own custom performance

2. Thoroughly examine EVERY area of EVERY part of EVERY element/operator/oscillator to become familiar with what the performance contains.

3. Remove or modify those things you don't want or don't need in your custom version

4. Save the 'sanitized' version of the preset as a 'USER' performance with a suitable name.

5. Use your sanitized version as the base for your custom performance - don't use the preset anymore except as a reference.

If you review that screen of switches for each part of each of those 3 performances you will see there are some other switches (e.g. Sustain) that could trip you up in the future. You can't possibly remember all of those things the next time you visit that preset. That is why you need to create your own set of 'presets' so you know EXACTLY what they do.

Good Luck!

Use the front panel MSEQ ON/OFF switch to disable motion control.

Motion sequence is not motion control.  A motion sequence modulates virtual knobs called lanes over time by stepping through cycles.  When those are "disabled" it only impacts lanes as source controllers.  Not all the other source controllers (modwheel, pitch bend, expression pedals, assignable knobs, ribbon, assignable switches, etc).

All of the other sources remain active for their instantaneous contribution to the algorithms set for each destination offset.

Hey guys,

I didn’t expect such a quick response and solution to this issue. Thank you very much for your detailed and excellent answers!

Toby describes the right solution to my problem. I just changed the Tx/Rx switch settings for the problematic parts of the mentioned performances and the sliders/knobs are moving again! I probably would never have found the reason on my own…

There are a lot of preset performances which I like very much but now I understand that some of them are not finished or only sketches to start with.

Thanks again and best regards!
Jens

PS. If the CC-switch would be 'off' for one of the main performances (like 'CFX') and blocking the sliders by default, I could well imagine that this would be quickly changed in the preset for the next release