I think the current reason for SETW is really related to the built in waveforms. You can change a waveform that is already playing, like from sine to saw to square. The waveforms stay on until the next note command, so in this way you can dynamically change the waveform.
Sample choking prevents multiple related samples from playing concurrently, like open and closed hats. To truly implement choking, you would set a choke list by priority, and this list would compose the choke group.
That way on a single sample column in a track you can have one sample in the sample column, and 2 in the FX columns, all with different probabilities, and the sample with the highest priority and true probability will be the only one to play.
I would offer that this could be accomplished in the Nerd Menu, and I would be fine with the current list being also a priority list. So the Sample list could look like:
By default no samples are in a group. This way you could identify multiple groups and use the # column as the priority. 1 choke group per sample is sufficient...I can't see the need for assigning 1 sample to multiple groups.
Sample choking prevents multiple related samples from playing concurrently, like open and closed hats. To truly implement choking, you would set a choke list by priority, and this list would compose the choke group.
That way on a single sample column in a track you can have one sample in the sample column, and 2 in the FX columns, all with different probabilities, and the sample with the highest priority and true probability will be the only one to play.
I would offer that this could be accomplished in the Nerd Menu, and I would be fine with the current list being also a priority list. So the Sample list could look like:
Quote:# | Sample Name | Choke Group
By default no samples are in a group. This way you could identify multiple groups and use the # column as the priority. 1 choke group per sample is sufficient...I can't see the need for assigning 1 sample to multiple groups.