I went into the acoustic piano DA sound to reduce the amount of sound level to the reverb. However, it is already set at zero. I am totally confused as to why the sound still has reverb when the reverb send level for the part is set to Zero. I'm totally at a loss to understand how this can happen, when it works perfectly on other sounds.When you run into a situation where either a Send amount or even the Volume level is set to zero, yet there still is the Effect send, or still Volume audible, you can bet that instead of using the common Control Change controllable parameter (cc91 Reverb, or cc7 Volume), the control over Reverb Send (or control over the Volume) has been assigned to a different control device for real time performance control. It is under "direct" parameter control of an assignable controller.
This brings up my request to push some button so you can see the OFFSET values instead of programmed values in all boxes - would help identify "oh, some control is changing this parameter". Although not what I previously asked for (because not as helpful) - maybe a compromise would be IF the destination parameter is already a destination that you select - flash the [CONTROL ASSIGN] button. Currently, the [CONTROL ASSIGN] button will illuminate if you CAN assign the destination parameter to a source. It may be at least marginally more helpful to flash the LED if the parameter has already been assigned to a source. That way you could think "ok, I need to go hunt down the source because this can be offset behind my back, although I don't see if it is or is not offset right just yet."Really not necessary, as the EDIT/COMPARE feature is always available to see what the STORED value was. And since assigning a parameter a control destination using the illuminated [CONTROL ASSIGN] button automatically takes you to the CONTROL ASSIGNMENT area where it will be very apparent what is assigned to what...
There's lots of ways to change this behavior:Er, perhaps not... Unlinking the assignment from the SUPER KNOB (on the Common/Audio level) does not solve the issue completely. Yes it stops the COMMON level from affecting the REVERB SEND. But when the PART 1 is selected, the AsgnKnob1 is still assigned to control the Reverb Send amount (which will still override the Mixer setting). Besides if the "PART 1 ASSIGN 1" happened to be doing something else you would eliminate that as well (not the case in this particular Performance but it certainly could). It is probably best to use (b) - Delete the DESTINATION within the PART - it is where the assignment initially takes place. Doing it elsewhere can throw other babies, unnecessarily, out with the bath water, while not fixing the assignment at its origin.
a) With new firmware you can "unlink" superknob from spinning a global assignable knob. So you could stop the control that way
b) You could have deleted the destination you don't like in the PART
c) You could, using scenes, make sure you save the superknob position - and save it (for all scenes) at a setting where superknob "zeros out" all parameters. This may not be possible for all situations - since it's just as likely that all superknob positions offset some parameters. But for the parameter you want to zero out, you can force superknob to that position. For the default Acoustic DA performance, this would mean saving a new user performance which sets superknob to position 0 (full counter clockwise) and also saves this position for all scenes you want a zero reverb offset.
EDIT/COMPARE doesn't help me illuminate offsets of parameters. The context is that I'm looking at the reverb send setting ("Edit - Part1 - Common" screen, "Part Settings" -> "General". If I press EDIT/COMPARE - I don't see anything different if I turn superknob which changes the offset of reverb send to offset values vs. not turning the knob. Reverb Send always shows the non-offset value here (the programmed value). EDIT/COMPARE is only useful to me if I change the programmed value of reverb send in the edit buffer and want to see what the last stored performance set this parameter to.I didn't think the issue was "offset parameters" but more that the original poster wanted realtime control over Reverb.
_ it would help to have some clue that a parameter is linked to a controller. Which I cannot seem to tease out a way to actuate using any of the methods you've suggested. I didn't see anything in the new features documentation that would align with this.Since that wasn't the question here no need to bring that into this discussion. The architecture does tend to err on the side of the programmer versus the person trying to decipher what a programmer did. I find this the proper balance.
I didn't think the issue was "offset parameters" but more that the original poster wanted realtime control over Reverb.