Topics created by orange

@orange Yes I did, but I don't see where this path has been modified, the width is still the one from the panel with no reduction

p1 = gr_peakreduct.createPath([a[0], a[1], a[2], a[3]], [0,1,0,-1], 1.0);

[a[0], a[1], a[2], a[3]] this is equivalent to just write a

@DanH Ive used it on three and it compiles without issues!

@aaronventure Definitely a bug. But random.
I think the probability of doing this increases as the network becomes more complex.

I think that these computers will be a real pain in the ass in the not-too-distant future. Especially on the artificial intelligence side

I have the same issue. Framex block doesn't work.

But can all this structure be done with frame2 block?

@ustk I'll try it when I go to the computer, but normally this should change automatically.

@Christoph-Hart After completing elements such as knobs, buttons, sliders, combo box, panels..etc. +1 cent for the Draggable filter panel

@Christoph-Hart you can see in the video that the network itself gets saved to a file. This happens by default when you Save XML.

Doesn't a network (in this case UpDown) have to be a file in order to be importable into another network as a node?

Why wouldn't hitting Save XML also save the changes in the external/child network?

Can something be done about the UX of making changes there where a reload of the entire host network (either by ejecting it and loading it back or by reloading HISE) is necessary when any changes are made to the external/child network and Save XML is executed?

Any networks that also host the changed network should automatically reload when the project is saved.

@orange if possible you can also use a slider pack to reduce the number of parameters (if that is a sensible choice for your node).

But 40 should be fine, the node interface might look ugly as hell though…

@Christoph-Hart I think it should be fixed now, Thanks!

https://github.com/christophhart/HISE/commit/fbc02d78d4d33b809ce4b2c07e4b29a52e036480

@aaronventure Nice one cheers!!

@d-healey said in Warning: undefined parameter 0:

@orange said in Warning: undefined parameter 0:

undefined parameter 0

That's telling you that the first parameter that you are passing to a function -- the thing in () -- is undefined.

Makes sense :) But it wouldn't warn previously

@dannytaurus said in Warning: undefined parameter 0:

@orange Is there a line number shown with the error message?

Yes the code that I shared above is the dedicated line.

Sorry for the late reply. I just realized that I'm using a 3rd party node for my LUT test.
Here's the full project you guys can take a look:
https://hub.korneffaudio.com/index.php/s/xPcEwQicPH63Fkd

@orange Yeah I removed that because it was super glitchy.

@orange If low ratio is 1, high works independently for me:

highalone.gif

@orange In french, "GPT" sounds exactly like "I farted" (j'ai pété)... Maybe that's just the real sense of it all in the end, with a real philosophical thought behind...

@DanH I thought that, at least the fixed band number can be set inside the FloatingTile.

It seems it is not possible without source code modification

@Christoph-Hart Great example! Thank you