Jump to content

Recommended Posts

Posted

No, currently the only supported algorithm is "oldest note will be killed first" if there is no free voice anymore. Free voices will be cycled from 1..6

Best Regards, Thorsten.

Posted

Couldn't the algo still kill the oldest note first but interleave the channels, though? Random might be a tad more difficult programatically, but, and to be fair I haven't looked at much beyond the shift-register definitions in the code, that seems like it could be pretty easy to do assuming that the CORE is the one that controls note kills?

Posted

The current approach is the best method to overcome the ADSR bug!

You will notice this while playing the default multi patch, where sustain is set to a value > 0 which is normaly critical for an ADSR "hick-up" - with the implemented cycling it doesn't happen as long as notes are not played too quickly.

Your requested mode would lead to unwanted side effects (ADSR bug would be initiated more often, or even randomly), therefore I think that it isn't worth to spend the time for implementing alternative methods.

Another reason is, that such an option would be well hidden in a 3-character acronym, so that nobody would remember anymore what it means after some weeks.

Best Regards, Thorsten.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...