This cannot be confirmed.

When reporting a possible bug it is standard procedure to mention what firmware version you are using and verify it (if possible) on multiple units. It is possible the issue is only with your particular unit due to a parts failure, or it could simply be that is old firmware. Although I do not recall any such an issue ever being the case. You should have your instrument looked at and make sure you are running current firmware.

Just FYI
When making assignments via the [CONTROL ASSIGN] button, once pressed you are prompted to activate the Controller you wish to assign, by touching [ASSIGN SWITCH 1] you will be taken to the PART’s “Mod/Control” > “Control Assign” screen. If any items are already assigned to this Assign Switch 1, they will also appear; your current assignment will be ‘added’ as the highest numbered DESTINATION. A maximum of sixteen Destinations per Part are available.

Bad Mister wrote:

This cannot be confirmed.

When reporting a possible bug it is standard procedure to mention what firmware version you are using and verify it (if possible) on multiple units. It is possible the issue is only with your particular unit due to a parts failure, or it could simply be that is old firmware. Although I do not recall any such an issue ever being the case. You should have your instrument looked at and make sure you are running current firmware.

Just FYI
When making assignments via the [CONTROL ASSIGN] button, once pressed you are prompted to activate the Controller you wish to assign, by touching [ASSIGN SWITCH 1] you will be taken to the PART’s “Mod/Control” > “Control Assign” screen. If any items are already assigned to this Assign Switch 1, they will also appear; your current assignment will be ‘added’ as the highest numbered DESTINATION. A maximum of sixteen Destinations per Part are available.

Firmware version : 1.60.1

I start from INIT Normal (awm2) or Init Normal (FM-x) so nothing is assigned.

The behaviour is confirmed so my unit have this bug.

this happen only with ASSIGN 1 - 2 button
Mod wheel, pitch bend and ribbon controller are ok

here we use to say : "I come from the dead and you say he is alive..."

Reproducible exactly as Roberto describes here. Bug confirmed on my Montage. (Firmware 1.60.1)

Well, I was just going to upgrade... I'll wait next firmware :p

I have not read that the bug can or cannot be reproduced in older firmware. This is a fairly obscure issue and probably not worth holding off upgrading considering the improvements to be had in the latest firmware. However, you are free to stay at any firmware you wish if this problem is a high priority issue for you.

Jason wrote:

"This is a fairly obscure issue and probably not worth holding off upgrading considering the improvements to be had in the latest firmware."

Fairly obscure issue ? this issue have a dedicated button on the pannel of the Montage. Yes I can convive with it but .....

Hi, I never used the assign control button til now, didn´t even know what it does. just watched a tutorial, and now that I know how to do it: no, I do not have this bug. it works fine. (my firmware is also 1.60.1)

Joe wrote:

Reproducible exactly as Roberto describes here. Bug confirmed on my Montage. (Firmware 1.60.1)

I just tested it on a second Montage (same firmware). Bug appears there too..

Gabi wrote:

Hi, I never used the assign control button til now, didn´t even know what it does. just watched a tutorial, and now that I know how to do it: no, I do not have this bug. it works fine. (my firmware is also 1.60.1)

Curious

when I follow this video it works:

https://youtu.be/M6c_aGgZXCk

but true, it doesn´t work if I try anything else. but not in the same way the bug is described. mine messes up the destination. if I try to use the control assign button for example to assign OP freq to assign 1, it shows me a dialogue saying "part 1 - OP freq, activate the source controller". I press assign 1, and I get either no destination at all or a random one and only sometimes what I wanted.

that button doesn´t really seem to work in any useful way.

"Obscure" is opinion (mine). Like I said - you (or anyone) can label the bug as front-and-center if that's how you see it. This is one of those items where there are several ways to assign controllers and - in my usage - I do not use this method. So it's obscure for me since I have "played" with the control-assign method a few times to become familiar with the feature -- but I still use the Mod/Control menu to pick a source from the drop-down list over using the control-assign button.

Given there's "another way" - I would personally want to gain the goodness of the latest firmware and become familiar with the alternative method of assigning controllers.

I also say "obscure" because my understanding is that out of the 40 or so controllers, just two are affected - A.SW1 and A.SW2. That's a low percentage out of the available controllers where presumably the control-assign button works fine.

I rarely assign A.SW1 and A.SW2 as modulation controller sources. I tend to keep them, in my programming, as XA-usage-only. This is just my workflow - and certainly some may gravitate towards button/switch controllers for what they do. When I want button-type control - I will generally use scenes and leverage superknob where changing a scene will set superknob to a certain position -- then my curve (often user curve) servicing the super-knob will have discrete values that "line up" with the scene's value of superknob - so I setup a sort of scene-to-superknob-to-destination "table" that will function much like a switch -- but I have more than two values available.

None of this may be how you work - so you could rightly view this as not so obscure in your usage.

This is a very personal how-you-use-it impact. And there is a fairly narrow window of failure presented here thus far.

Unlike other bugs we've seen - this is not one that involves possibility of data loss/corruption. Not a "sky is falling" class of failure. Yes, an annoyance if you rely on this particular method of controller assigning and happen to be assigning these two buttons. Some of the reaction to the bug announcement is suggesting something more catastrophic than is really the impact here. I wanted to be sure that there was balance to the discussion.

Regardless, it should be fixed. I had an even more obscure bug pointed out a while ago (1 out of 127 for that one instead of the 2 out of 40 presented here). Not sure that one ever got fixed. Won't elaborate - just saying I'm all for squashing bugs - even "obscure" ones.

Hello, i cannot have test on OS 1.60 cause i was already on OS 2.00 for testing when you post this message, so i cannot infirm or confirm.

On OS 2.00 no problem, i select a destination like part volume or part FX dry/wet setting, press control assign button, press ASW1 or ASW2 and it have been set as source to control the volume or Dry wet FX destination.

On 7th february you will test yourself.

Same here, so if it was a Bug, it is now gone - so that’s the good news. I, too, have already been at 2.00 for a while - that’s why I could not confirm the Bug report.

Interesting that now you actually can, when using the [CONTROL ASSIGN] button to auto assign physical Controllers, you can now also assign the parameter to Motion Sequences, or Envelope Followers as the Source Controller.

Bad Mister wrote:
Interesting that now you actually can, when using the [CONTROL ASSIGN] button to auto assign physical Controllers, you can now also assign the parameter to Motion Sequences, or Envelope Followers as the Source Controller.

A nice addition!