Posts made by Simon

To implement keyboard playing like you find in DAWs, might there be a way to get the current keyboard layout as well? I'll specify that I want to use the (PC) keyboard to set the current chord in a plugin, not play a MIDI note directly.

@d-healey As usual I found it right after asking. Thanks David!

I'll bring this topic back from the grave and ask the compliment of David's question. Is it possible to get normal keypresses? Specifically, letters A-Z, maybe characters too.

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

Sorry for the basic question, but is there a way to re-open the token parser for samples already in the mapping editor, the same way you can run automap on selected samples in Kontakt? Searched forum and interface, but no luck.

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.

That was the first thing I tried, but ran into "error reading" errors in xCode and assumed I must be doing something wrong.

I opened that .jucer in Juce 5.4.7 and building with Xcode 11, which throws

Error reading 'HISE-scriptnode/JUCE/extras/Projucer/Source/Application/jucer_AutoUpdater.cpp'
and
Error reading 'HISE-scriptnode/JUCE/extras/Projucer/Source/Application/jucer_CommandLine.cpp'

Both files are definitely there in the correct locations. Any ideas?

Same issue here. I'm not quite sure where to get started building the projucer, any tips?

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.

In Kontakt, if the sample is mapped to one velocity, then the velocity modulator will only affect the sample when the output of that modulator is that exact velocity. You would need to control the gain of the sample via script with change_vol, at which point you don't need modulators at all anymore.

I'm guessing there's no way to do this with modulators and I'll just script it.

@d-healey Sure, but I had a vague hope that HISE would have a way around this limitation of Kontakt. For instance if a sample was mapped to a single velocity in the GUI, it might still be possible to scale the input velocity range of 1 - 127 down to that one velocity, while still having modulators affect the sample with 127 discrete levels.

Essentially you'd be applying a curve to the actual sample map itself, rather than to the input MIDI. From the perspective of a sample, this looks like fractional velocities.

I am guessing from your ellipses though that that's not even close to being the case.

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.

@AudioHobbyist Have you managed to get the new installer to actually work with HISE plugin exports?

Sorry if this has been asked, but I couldn't find anything in the API or forum. I'd prefer to stick to scripts as much as possible and not deal too much with routing in the GUI, so is there a way to control mic gain without routing to Simple Gain?

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 You should use the Projucer application that comes with HISE.

@Rudra-Ghosh That may be, but if you want to build HISE you should use 2017, and you should not update the projucer application that comes with HISE.

@Rudra-Ghosh I believe I had quite a lot of trouble with 2019 and never got it to work. Installing 2017 is the way to go.

@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.

@DanH Life saver. It's completely insane of Intel to have removed the old downloads.