Topics created by RCJacH

@rcjach Hanging notes are bad... Hanging notes are wrong... Hanging notes are frivolous, insidious, perfidious... Hanging notes contribute to losing your mind, hence favour anxiety, malnutrition, leading to grave diseases and even cancers. They are not compatible with new year wishes we want to spread all over the world. So join the league now and help us fighting against Hanging Notes!

This was a message from the NMHN community (No More Hanging Notes).
NMHN, For a better world...
😛

@rcjach You might be better off using a dedicated XML editor rather than a text editor for your sample maps.

@rcjach I try to make my scripts independent so they don't need to communicate with each other. Sometimes I'll have scripts that control components on other scripts using setAttribute

@d-healey okay thanks for the reminder.
I refactored the script like you said and used a switch condition :face_with_tears_of_joy:

I have some sample maps which work well in hise but once in the compiled vst, the Samples are mixed. it's really boring

Using a script in every sampler is a good approach. You can use a single external script so you don't end up with lots of tiny individual scripts.

You can delay events with delayEvent().

For my strumming system I had everything in a single sampler, each string and up/down was mapped into a different area of the mapping editor. This idea isn't original with me, I've seen it used by a few guitar libaries. I created the strum using a timer to play the strings one after another.

24eef671-6b1f-4b68-bb17-2a4e06797108-image.png

Thx, oh so Id is the name string :face_with_tears_of_joy:

@RCJacH Oh you're doing something fun. I spent several months of 2019 working on a still unfinished guitar strumming engine. :D

When you include a script it's the same as if you've copied/pasted the script directly in to the MIDI processor's on init callback. So yes, each one is independent. You should use a namespace in your external script too so that a) you get access to more reg variables and b) it's easier to see where various function calls are coming from.

If you edit the external script though those changes will be reflected wherever you have included it.

stay local to each of the processors that imports the module.

I'm not fully understanding your terminology here. What do you mean by processor and what do you mean by module?

Ok understood. Thanks for the explanation.

You need to apply some sample start mod (s.mod) time to the samples - just like with Kontakt. If you want to use the whole sample then just set this to the full length of the sample but then the whole sample will be loaded into RAM.