"keeping generating the sounds internally" is what "set volume to zero" does. Both approaches have their use. Mute, which does not still generate the sound internally, has the advantage of not having all those silent voices unnecessarily using up polyphony. "Set volume to zero," which is, as you suggest, still playing the sound (albeit silently) means you could fade the sound in, even after having played the keys, but it does mean that all those triggered notes that are playing (even though you can't hear them) are using up polyphony.Interesting. I did not know that MUTE works this way. I thought it only mutes the audio signal (pre insertion effect) while keeping generating the sounds internally.
I'm not sure what you're illustrating there. So much for clarification.For clarification, let me share an audio example to make it clearer what I mean by seamless switching between tones with seamless sustain pedal: seamless.mp3
The Montage ideascale link I pointed you to was relevant to how a held sustain pedal behaves across Performances, it was not related to the KBD CTRL (keyboard control) setting in Scenes, sorry if I misled you there. (It was also kind of picking up from WEM's January 9 comment, about how Yamaha defines "seamless sound switching".)The purpose of this topic was to clarify whether the sustain pedal is seamless when enabling/disabling keyboard control. This question has been answered: The sustain pedal is not seamless. However, there is apparently something on ideascale to address this limitation.
To the bigger point here, the sustain pedal is seamless when switching Performances, in that it continues to sustain the old sound even after you've switched to the new sound (something that does not happen, for example, when you switch Performances on your Motif XF). What some people don't like (and that Ideascale post addresses) is not that it isn't seamless (because it is), but rather, the issue is that the new Performance does not inherit the current state of the pedal (i.e. depressed). Rather, it considers it not pressed until it is pressed again after having switched to the new Performance. Which means you have to release the pedal in order to engage it on the new sound, and THAT will, indeed, cut off the sustain of the previous sound. So while the switch between Performances did indeed happen seamlessly, the fact that the new Performance doesn't inherit the sustain pedal status from the previous performance is what's creating the issue. As I mentioned earlier, sometimes this is desirable (it essentially becomes a sostenuto function)... but the user should have some way to control which behavior he wants.
Statistics: Posted by anotherscott — Mon Feb 12, 2024 4:15 am