[bug] sustain-module not working
Hello,
beta 9 (reported that for beta 8 two weeks ago) ...
The sustain module in Max is not working as one might expect it to work.
example:
1) hit a chord (c-e-g) and with keys down, press the sustain pedal
2) while sustain pedal pressed, release the chord and play e again and hold it
3) with e still held down, release the sustain pedal
-> e gets a note off message ... whereas it should be still playing as it is still pressed down.
this does not happen if I do steps 1-3 again but instead if playing e (in step 2) play f .... this results in right behaviour.
Would be great if this could be fixed. Pretty, pretty please ... (or let me know if you will not do it and I program a Java external ... no problem, but please let me know)
Thanks
Hi,
Thanks for the report - I can reproduce this and we'll have a look at it.
Cheers
Andrew
Hello,
this has not been fixed with 5.1? At least it does still behave in the same 'erratic' way ...
best
Yes it didn't make the cut for the release due to our code freeze cut off. It's a funny one. The sustain object has been like that for 20 years, so we can't change its default behaviour, however wrong it appears now in the light of sampled instruments. We'll probably add a new mode for it.
-A
I can't imagine that anybody relies on a misbehavior, even if it sits there for 20 years. Just fix it, its not worth to create a mode for keeping a bug...
Stefan
Sorry to resume this very old thread, but I suppose the behavior of [sustain] is still the same.
Am I wrong?
Check out the repeatmode attribute.
Thanks @Ben.
The object is working correctly with repeatmode 0, but not with 1.
with repeatmode 1 it does not keep track of the held notes.
Es:
play C
> sustain
leave and re-press C
> sustain off
= the C pitch is cleared even if it's still pressed on the keyboard.
And to me, this remains a bug.
a way round might be found here thanks to Adam Murray: https://cycling74.com/forums/turning-sustain-off-kills-notes-from-still-depressed-keys#reply-58ed2006b7244922ce25de24