Essential- choke / exclusive/ voice note groups

  • @Christoph-Hart Thank you so much for the updated snippet. 👏 The script works great. The first line of code was different from I had (and what was in the original). From -1 to +1. Not something I would have figured out in 100 years. 🙂

    If you were providing the hardcoded script in the current form, then yes, you would need a thousand variations. However, there is a much simpler and more practical way to achieve the same.
    The way to achieve this (as is the case with most samplers) is to have choke/ voice groups. So, whatever elements are in group 1 (for example), they all mute one another. There is no need to specify trigger and target. Every note in a group is both the trigger and the target or every other note in the same group. So, in the case of hi-hat: open hat is not the only one being choked. A closed hat should also be stopped by open, as you can't play both at the same time in real life. However, because closed hat has such a short duration, muting it becomes unnoticeable. Especially if a decay is set. By the time decay is done, the closed hat sound is finished anyway.

    So, if you could create that little option, not only will you make it easier on every future drum producer using HISE, but also on yourself, as you don't have to keep on tweaking and customizing code for the same function. Makes sense? 🙂 Take a look at how it is done in Kontakt for example. This is a standard feature on other samplers.

  • Well to be fair a open hi hat sample should not be choked by another open hi hat sample (same as ride cymbals should not kill themselves when retriggered), so this is clearly a compromise due to the choke group logic.

  • @Christoph-Hart No, I don't mean for one note to choke itself. For example, lets take A, B and C notes.

    A can choke B and C
    B can choke A and C
    C can choke A and B

    A can't choke A
    B can't choke B
    C can't choke C

    So, each note follows the polyphony of the sampler, but choke group creates monophony only between different notes. Makes sense?

  • @Christoph-Hart After doing some testing, I have discovered a little bug that needs a tweak.

    When hi-hat note overlaps in duration another note of the same kind, the second note is not played. The first note is not being treated as a one-shot note. Take a look at the following examples:

    1. All 4 notes are short and play properly (all closed hats)


    1. 1st note overlaps all others and the 2nd note does not play (all closed hats)


    1. 1st note (closed hat) overlaps the others. 2nd note is open hat and it plays, but 3rd note (closed hat) does not


    In any combination, the note immediately following the long note (a.k.a. the 2nd note) does not get played.

    Can you please take a look at the script you made and revise it, so that all notes get treated as one-shots regardless of their duration?

    Thank you so much!

  • @gorangrooves @Christoph-Hart
    I've already noted this previously. It's currently impossible to create a drum plugin until it's sorted 😞

  • @dustbro Oh, man. This is no good. This is an essential feature we can't do without. This is standard on every professional sampler.
    @Christoph-Hart How quickly and what will it take to get this resolved, please?

  • Alright, I‘ll ramp it up on my priority list then - I think the problem is that the system that assigns the event IDs is not supposed to accept multiple notes at the same time, but it shouldn‘t be too hard to fix this.

  • @Christoph-Hart Thank you so much. I have full confidence that you will nail it. And i promise you that it will be well worth your time. I will be releasing 15 drum instruments this year, as long as i get the first one working 100%. We are almost there!

  • giphy.gif

  • Check the develop branch 🙂

  • Hey @Christoph-Hart, the hi-hat choke script you provided a while back has been working great for the regular hi-hat. I have since created an advanced version for variable hats which has several stages of open and close (tight, close, 25% open, 50%, 75%, 100% open). These are nested containers and I switch between them using CC64 controller. I have altered your original choke script to allows CC64 to choke notes. It works great.

    Now, the next step where I am failing is that I am trying to add a choke script on the parent container (that contains 6 child containers) which would choke a note using another note. Basically, the same as what we achieved with your original script. However, it is not working properly. It starts working, then it fails. It gives me a number of warnings, such as:

    Shank100 Script:! onNoteOn() - Line 28, column 36: Illegal operation in audio thread: String creation {U2hhbmsxMDAgU2NyaXB0fG9uTm90ZU9uKCl8NzQ0fDI4fDM2}

    The line of code in question is:

    Synth.addVolumeFade(eventId, decayValue, -100);

    This happens for all child containers that get played once I start using the controller. This "choke by controller" script is present in 4 child containers and works great until the parent "choke by note" script is enabled. I am guessing that there is some sort of double volume fade clash, but I don't know how to go around it.

    Can you help, please?

    Thank you!