Nice, well done, and thanks.

Coming from Kontakt I think of it this way, each sampler you use in HISE is essentially what you get when you have a single NKI in Kontakt. Each sampler can have groups, just like a Kontakt instrument, into which you can map your RR or dynamic layer samples.

onInit is enough (actually you only need to call it when the mapping changes)...

My use case was to put a CC modulator in each sampler to control gain via expression and then have a table on the interface that controls the table of each modulator. After playing with it some more I realised I could just grab the CC value in the script and scale it to the table setting, then forward that to the modulator. This saves me having to specify the modulators in the script too.

Wow that was fast! I'll try it out soon

Fixed in the latest commits.

Aha! I misunderstood what was happening. The current behaviour is fine :)

It creates an extra timer but it runs in the message thread, so I would use it for audio stuff, and actually since ScriptPanels also have a timer for animation it became pretty useless - I think I added it before I added timers to the Panels but left it in the code base for some weirder use cases. Somehow the API doc didn't make it in the autocomplete list, but this is the usage:

const var timer = Engine.createTimerObject(); timer.startTimer(150); // in milliseconds timer.callback = function() { Console.print("tut"); };

I thought it was there, but it wasn't. But I added it now, this is a reasonable request.

Alright, it's fixed.

That makes sense, thanks for confirming

ok cool, thanks

Thanks, really easy :)

Brilliant, thanks :) this will be very helpful

I don't know. They're both pretty cheap so I don't think this will be a bottleneck anywhere but if I have to guess I would say the scripting functions are a bit faster.

I'll have to see if I can recreate it in a more isolated context

Oh, that simple :) thanks