Hihat choke with implementation with user-defined MIDI inputs
-
This post is deleted! -
This post is deleted! -
@ObsydianX Sorry I didn't understand your question at first, and maybe still :)
Is this what you want to accomplish?
function onNoteOn() { var nn = Message.getNoteNumber(); if (isDefined(kitSource[nn])) Message.setNoteNumber(kitTrigger[nn]); }
-
There is a choke group midi processor that might be helpful.
-
@d-healey I saw that and I experimented with it but I honestly have no idea how to make it work. Because my end users can reassign the MIDI notes that actually trigger the kit, the low and high note in the choke processor probably won't work for me. I think I need a different solution.
-
@ulrik Might be on a different page. I've got the user selected MIDI working just fine, but I need a way for one note to cut off another note.
-
If you‘re doing the reassignment before the ChokeProcessor using setTransposeAmount(), the choke settings can be static - otherwise the range parameters of this module can also be controlled by a script.
-
@Christoph-Hart Now, pretend like you’re explaining it to a 5 year old. Haha. I mean, I just learned how to use my first arrays.
I’m honestly tempted to post the project on GitHub and collaborate with everyone on a drum sampler template.
-
@ObsydianX said in Hihat choke with implementation with user-defined MIDI inputs:
Now, pretend like you’re explaining it to a 5 year old. Haha. I mean, I just learned how to use my first arrays.
Maybe start with a simpler project ;)
A MIDI processor is like any other module, you can set its parameters from your main interface script. So when the user re-assigns the triggers keys you can (via scripting) change the range of the choke group MIDI processor. Or as Christoph said you can use the transposition function to handle the key remapping.
-
@d-healey I was never able to work this out but I found an easy solution by just limiting the voices for each thing I want choked to 2 and putting them in their own sampler. Not the most realistic but it's all I can figure out for now.
I learn by tackling the problems before me, not necessarily by trying different things first. My main reason for switching to HISE is because I'm trying to build a drum sampler, not much else. Therefore any issues I have with building a sampler is something I HAVE to overcome because I'm not really trying to become a programmer or developer, just hoping to be able to create what's on my mind.
That all being said, I'm going to put this project on github once I'm finished building the UI so anyone else can use it as a starting block for their own drum sampler. Hopefully, more people working on it will help it become a really good starting template for others.
My hope for the future of HISE is to implement something along the lines of Kontakt's exclusive groups via UI not scripting because it's pretty useful to have.