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 :)

Yes this is already step 1 of my marketing masterplan - once we‘ll release HISE 3.0 ;)

@ulrik @d-healey

Yes I was excited to see @Christoph-Hart push some new features to the tempo.sync node in scriptnode a few days ago.
However, exported fx using this node sound very strange when using them in a DAW as mentioned in this thread https://forum.hise.audio/topic/2120/flanger-in-scriptnode/17).

I’m gonna keep exploring the timer solution for now 😀

@Christoph-Hart That's what I do for signals. But here I just want to make a calculation based on a knob input, and output the result.
For instance, I'd like to input a time in ms and output a frequency value in Hz to set the oscillator.
There might be another way than using a jit, but I don't see how...

Untitled.jpeg

float TimeIn = 0.0f; float FreqOut = 0.0f; void setFreqOut(float newValue) { } void setTimeIn(double newValue) { TimeIn = (float)newValue / 1000.0f; FreqOut = 1.0f / TimeIn; //setFreqOut(); }

There might be a better way for this example, but not necessarily for another one...
(I know it looks weird but it's just for the sake of the example)

@d-healey I very much agree on all your points, I am all for sharing and keeping it as open as possible within my personal projects, so maybe I should have explained it better.

It's not fear or paranoia on my part, but rather trying to see if there could be practical options since I do often work with clients in the video game industry that are incredibly stringent on this aspect by default (the last project went for four years + insane data transfer protocols and contracts ).

@Christoph-Hart Thanks for the suggestion on the NDA's - I will definitely go this route :)

@ustk said in Font weight property due to rendering difference between OSX and WIN:

Unless the parameter is not portable between the two renderers, or not easily accessible...

this.

@ustk oooh Silly Me 🤭 Just Need To Change The Shapes From Hp To Lp