@d-healey said in Reading (and then using only part of..) a preset file:

You'd need to keep a kind of internal preset with the current state of the controls and then after the preset has been loaded you can restore the controls you don't want changed.

Yeah that'd work .... thanks.

@lalalandsynth I usually use a sweep. I've not found any issues with phase so far capturing my 5150. I'm going to experiment some more with it.

This plugin has been pushed down the priority list a little as I have 4 others in line first but I'll be getting back to it very soon :)

The tick method should work just as well though, from the videos I've seen on it.

How deep do I have to dive to achieve something like this look on the eq curve for example ?

yagya Eq.jpg

@lalalandsynth Nope, I make my vectors using Hise paths, but I might improve them with Lottie in the future...

@LightandSound

Thanks for the help! Will look into it.

@d-healey Cool ;)

@orange said in audio to midi feature?:

drum trigger

I'm looking for a simple drum trigger.

@Lindon Gotcha. Thanks Lindon! Fun days ahead 😲

surely it should be doable though, seeing as we export fx's from hise to begin with, so the code is there to have audio inputs somehow

aaah well, maybe one day!

@ustk that's why I say it's a fringe case, essentially if you set them as variables or for example use getvalue() without setting the min/max value of the panel then you could run in to problems. But there shouldn't be a 'real world use' for a range of 0 to a larger range, since all that does is spit out the same value. It's just to protect for the inevitable case where human error gets in the way.

@d-healey it's like changing items in a combobox or Viewport, I have to set it to zero then apply the new items

Yes, definitely needed , unless it already possible and I am unaware ?

In my case I am using an image , and with that disabled allows mouseclicks going trough.:)

@Natanr https://docs.hise.audio/scripting/scripting-api/engine/index.html#createandregisteraudiofile

I've implemented this now in my local repo.

@Christoph-Hart I haven't hit any issues but can you think of anything I might have broken with this change? Shall I make a pull request? I was thinking, shouldn't the lower velocity range limit be 1 instead of 0, since 0 = note off?

Now we need vertical zoom in the mapping editor :)