pon., 25 lut 2019 o 19:10 Christian Schoenebeck <schoeneb...@linuxsampler.org> napisaĆ(a):
> From what you described so far, I don't see why you would need to open a > separate concept to the existing key group conflict concept. As far as I can > see it, the key group concept just would need some additional options for > allowing what you want to do. Thank you for your explanations. I'm a hobbyist drummer and hobbyist programmer and I don't aspire to bring a final solution for those issues. I suppose the common engine interface is not going to be released in near future. Therefore, I'll finish my sfz implementation using events, since that's what I need for now and send the patch to the mailing list. > Still sceptical? :) Not at all. Misunderstanding came from the name "Key Groups (a.k.a Exclusive Groups)" and actual implementation with no other possible behaviour. I think this sfz 2 opcode (default on) could be a sane default behaviour for each engine, even with sustain pedal on: http://www.sfzformat.com/index.php?title=Note_selfmask ("higher-velocity notes turn off lower-velocity notes, but lower-velocity notes do not turn off higher-velocity notes"). Best regards Jacek Roszkowski _______________________________________________ Linuxsampler-devel mailing list Linuxsampler-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel