I’m rebuilding some AR patterns on DT II. How do I best replicate choke groups?
I thought nei condition would be the best to do this. I haven’t used them before, but my experiment didn’t really work. I’ve tried to recreate the closed and open hat choke group on DT by placing closed hat sample on track 15 and open hat on 16. I’ve then set all of the trigs on track 16 to not neighbor. I thought this would mean that the closed hat trigs on track 15 wouldn’t play if the open hat trigs on track 16 are playing. It didn’t work and the trigs on track 15 never played, no matter what happened on track 16. So my questions are: is nei/not nei the easiest solution to replicate choke groups? If so, what did I get wrong about applying them?
If nei doesn’t work as I have described, what’s the best alternative? I know I can just not place trigs in the same place or use conditions like 4:8 and not 4:8 etc. But that’s really complicated and doesn’t work in all cases. So if there’s an easier way, I’d prefer that.
In general, I’m not sure about one thing that might complicate things: is there a priority among two tracks in an AR choke group? Or are they interrelated? For example, does the open hat always choke the closed hat but the closed hat never chokes the open hat? The manual sounds like that, stating that “the right-hand track has a higher priority”. Or does the open hat first choke the closed hat but the next hit of the closed hat will choke the closed hat as well? If it’s the latter, this might make replicating choke groups on DT a bit more complicated. The manual seems clear on that though.
There are probably more elegant ways to do it but placing them on the same track by using sound pool / sound locks is the simplest way for me to achieve that. As a monophonic sampler, if they’re on the same track, they will be guaranteed to choke each other out.
Not sure if that helps, probably not the solution you’re looking for.
Thanks! I know of this method and have used it before. I agree it’s the easiest, so I should have mentioned it. I try to avoid sound locks if possible because it limits playing around with parameters live that I want to affect each trig on CH/OH.
Rereading the manual, I think I’ve placed the neighbor trigs the wrong way. I think it should work if I put the open hat on track 15 and the closed hat on track 16, then set all of track 16’s trigs to not neighbor.
If it works this way, there’s another solid reason why it would be great if Elektron allowed us to pick a condition that applies to all trigs placed on the track by default. So far, condition only has a lock symbol if you’re not holding a trig.
Yes you have to use /NEI and put trig conditions on reference track.
Not convienient. Choke group feature request ! (I’ve found a workaround with Digitone layers, not convenient either).
Yes, values added to probability parameter for instance…
I’ve come to the same conclusion that the neighbor function is better than nothing but doesn’t really work well. No comparison to how AR chokes its hats. I stick to other methods like not placing trigs or using the same sample with shorter decay, like it has been mentioned. I also like the method of one sample with both closed and open, really fun to play in. But it comes with some caveats like you can’t use random LFO on slice grid anymore.
I use a method with /NEI where the left track is an open hi-hat and the right track is a closed hi-hat.
Left track: Fill all empty trigs with lock trigs set to PROB 0%.
Right track: Set COND to /NEI for all active trigs.
I prefer this over the single track solution because I can mute and easily edit both sounds separately. It’s not a true one voice choke though, the open hi-hat release can overlap with the next closed hi-hat. However they don’t hit at the same time which is the most important thing for me.