Best posts made by Simon

@ustk Awesome, that looks like it'll work great, though I'm getting slight flashbacks to similar control-layering jankyness in Kontakt.

For anyone reading this later, the solution is to script a panel to have mouse interaction slider behavior, or to use an invisible slider for mouse interaction and the panel only for drawing.

You can change which image is loaded using ScriptPanel.loadImage, and update the drawing of the panel with Graphics.drawImage.

David's tutorial covers a lot of relevant stuff here

I don't know what the situation is with IPP now in HISE, but the old dropbox link expired so here's an internetarchive link just in case: https://archive.org/details/intel-ipp

Ah it's a permissions thing. If you go into settings and allow full disk access to either Xcode or Projucer (I just enabled both), it builds and opens properly.

Thank you David. Providing a snippet is above and beyond, as usual.

@Lindon In Kontakt, a velocity curve does not work well if you go to extremes like I described. There is no way that I am aware of to decouple the velocity that is sent to the sample map from the velocity sent to the vel > volume modulator.

Imagine this were a user-drawn velocity curve taking the lowest dynamic layer and spreading it across the full velocity range of the keyboard:

In a situation like this, your input with 127 values gets quantized to something like 10-20 values.

With the HISE global modulator, the velocity sent to the sample map is different from the velocity sent to the volume modulator, which is exactly what I was after.

Hi there. I have a more conceptual question this time.

I'm trying to build a basic keyboard instrument with a sensitivity slider that does more than act as a LUT for incoming MIDI.

Imagine a soft/hard knob on an instrument with six dynamic layers. All the way soft would heavily weight incoming MIDI towards the lowest dynamic levels, and velocity 127 would trigger only dynamic level 3, with the highest two dynamic levels omitted entirely.

Same vice versa. With the knob all the way at "hard", incoming MIDI is weighted towards higher dynamics, and a note with velocity of 1 would trigger dynamic level 3, the quietest two dynamic levels being omitted entirely.

With the knob in the middle, you'd get a normal linear response.

If this were Kontakt, I would put each dynamic layer in a separate group and do the "which group to play from" decision making and velocity scaling in scripting. Each group would have a velocity>volume modulator with an upwards slanting curve such that each dynamic layer, when played with a velocity of 1, approximately matches the dynamic layer below it.

The idea is to be able to select one or multiple dynamic layers and map them across the velocity range without running into quantization like you'd get with a simple MIDI input LUT.

In HISE I'm guessing I could use separate samplers or rr groups to select which dynamic layer to play. Or maybe the velocity mapping secretly uses floats and there's a way to play with fractional velocities?

I'm asking now before exploring options thoroughly in case there's a very clever solution right off the bat. It's difficult to think outside the box when you've been stuck in Kontakt for years.

Huge thank you to @DanH for having the foresight to save the old IPP installers (I was kicking myself for not doing the same). I can confirm that using IPP from the link in his post here works fine.

Here is the direct link to the correct IPP version.

Here is a backup link in case the Dropbox one stops working for whatever reason.

This kind of nonsense in software development drives me nuts. If Intel had just kept the old links up we could have avoided wasting our collective time.

@Rudra-Ghosh I agree, HISE is not easy to get started with, but once you get over the initial hump it's much nicer. For this particular issue, do not retarget the project, but rather add the correct SDK version to Visual Studio. The version it's looking for is 10.0.16299.0.

You can add the SDK by running Visual Studio Installer, clicking Modify by Visual Studio 2017, then going to Optional, and checking it in the list.

Hopefully we'll improve the docs soon, at least to remove conflicting information.

I promise I'll stop clogging the forum now. Thank you David as always for your unending help.

This particular case was user error. I had disabled the main Container so it wouldn't play back while I was testing the vst. So I was exporting the plugin with the main container disabled. Doh.

Fooound it :D Will let you know if it works in a sec.