[bug] sustain-module not working

    Nov 16 2009 | 5:15 pm
    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)

    • Nov 16 2009 | 6:50 pm
      Thanks for the report - I can reproduce this and we'll have a look at it.
    • Nov 25 2009 | 3:30 pm
      this has not been fixed with 5.1? At least it does still behave in the same 'erratic' way ...
    • Nov 25 2009 | 5:54 pm
      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.
    • Nov 29 2009 | 10:30 pm
      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...