And now my assertions are working as well which is what I needed in the end

For the records if someone gets there, the scheme was set to hise debug but with a release build...

@griffinboy Thanks
In the end I've made a mistake, mixing a release build with a debug executable...
So I can get DBG to work

Is anybody knowing how we can output to the console (or xcode or anywhere really...) from a C++ third party node?

I'm 90% sure I did it in the past but I am not able to do it again...
tried debugToConsole with no success, I don't even succeed getting the MainController mc...

DBG("Value: " << someValue); // doesn't work either...

@DanH §(èù=ù:$^(§è"(... one more to block...

Next, being able to choose the spline function among 20 different... per section!

@HaizalD3 this is what @iamlamprey explained at first https://forum.hise.audio/topic/13835/duplicate-script-fx-network/2?_=1763124621738

@DanH as @iamlamprey, this is the way

@Christoph-Hart is there a way to reset a curve to exactly 0.5?

@HISEnberg Not sayin' Chris isn't strong... But having biceps as large as his brain might be the main reason you'll get banned...

@HISEnberg oh boy I missed that one so much

@HISEnberg said in How to Open CSS Debugger?:

Nevermind I see it: Top bar go to View > Reset Workspace. Always so many hidden features inside of HISE!

Oh nice, was easier than I thought in the end

@HISEnberg It means just close Hise, delete editorData.json in the Hisa appdata folder, restart Hise.
This will reset the entire workspace

@HISEnberg Quickly looking at the snippet, it's more or less what it does

@HISEnberg if it's just in the beginning and the end of the chain, then you can re-order them using the range parameter and an offset. In fact, even in the case you have fixed FXs in the middle, it should be possible to re-order in two chunks, before and after.

In the end it is just juggling with position numbers.

if you have 10 fx in total, and want to re-order from 3 to 7 (0 based, 3 fixed at start and 2 at the end)

the the slotRange is [3, 7] and chainOrder is for instance [4, 7, 6, 3, 5]
This leaves 0,1,2 and 7,8,9 untouched

If your chainOrder is based on indexes from 0 to 4, just add an offset of 3

@ustk That being said my curve is made for a waveshaper (not modulation). Meaning that the worst case scenario is to get point that aren't absolutely perfect but unnoticeable to the hear... The reading of the LUT is still interpolated of course. So in the end the mouse precision when dragging a node on the interface is far more approximative.

What I don't like though in the NR algorithm is the extra computation it requires...

@griffinboy Nice! I'll have a check on this to see how I can adapt...

Didn't want to pollute more @DanH thread https://forum.hise.audio/topic/13831/stock-table-upgrade

@griffinboy BTW, how do write your LUT from the curve?
since y AND x are determined by the curve's dynamic, x might not be an integer for writing the LUT

In my case I use a Newton-Raphson loop in order to find an integer for x, and so it's corresponding y value...

How do you handle this?

@HISEnberg sick! a contest! You have to know mine is as smooth as baby skin...

@griffinboy Yeah same here
I just send the nodes and tension information (called smoothing here) to C++ and build the curve in there...
We should have worked together on this lol

@HISEnberg Yep this article is nice. In the end it all depends on the interaction you want with the curve, because there would be as many spline constructions as desired interactions... I needed mine with curve passing through the points, and no possible overshoot on the y axis (when 2 points have same x, it's forbidden for the curve to pass those points (like in standard table) which isn't possible with standard cubic unless all control points are permanently resizing to follow their neighbours