I must definitely warn you about resellers, never work with ADSR Sounds!

From what I have heard from my acquaintances, they have a really bad reputation. They have unpaid invoices for developers for months, they are the kind of people who exploit people's labor.

@David-Healey

I'm leaving the solution here as a note in case others experience this problem. I had to look back to this commit: https://github.com/christophhart/HISE/commit/c948b81f7a86f24a8fce4ea81051c73b7129e2b5

There's a folder named JUCE in the downloaded "Hise-develop" branch. You need to copy all the files from the submodule into this folder.

From now on, the Projucer application will be launched inside this JUCE folder.

@d-healey Clever! Thank you!

@aaronventure said in ScriptNode Feedback After a Month of Heavy Use:

If you have 200 nodes...

I'm sorry I'm new, but I'm trying to understand how something complex can be done with 200 nodes :)

In my first attempts, I worked with a maximum of 20 nodes :)

@ulrik useful example, thank you for sharing this!

@Christoph-Hart Is the CPU performance issue resolved?
We look forward to being able to use NAM models quickly and efficiently in our plugins

@resonant I believe this graph is included in the Dynamics FX example in the Hise Tutorial Projects.

@dannytaurus said in Scheduled knob task after initialization:

@JulesV Interesting! What's the use case for this, if you don't mind me asking?

It can actually be used for other purposes.

But in my case, I'm actually using it for a bug workaround. When I buld a complex custom node with 23 parameters and use it in HardcodedFX, I noticed that in one parameter, the knob, wasn't getting its value during plugin initialization.

However, after init, when the knob is tweaked, the value is updated. That's why I chose this method. Creating a custom node with fewer parameters isn't a problem, by the way. As the number of parameters increases in custom nodes, the problems increase.

@DanH I noticed something interesting, while almost all AW plugins can be compiled separately, some AW plugins cannot be compiled as multiple dlls in the same project.

For example, Tube2, Huge and Mojo plugins can be used together in a project.

But LeadAmp and FireAmp cannot be used together in a project.

But all of these plugins can be compiled individually.

So it is related to the AW plugin combinations.

@orange said in Resonance Suppression:

Faust constantly surprises me

Here is a spectral denoiser article: https://inria.hal.science/hal-04507625/document

I haven’t tested the sound tho.

@orange Sorry for the long time follow-up question, did you manage to do this?

@David-Healey

I'm leaving the solution here as a note in case others experience this problem. I had to look back to this commit: https://github.com/christophhart/HISE/commit/c948b81f7a86f24a8fce4ea81051c73b7129e2b5

There's a folder named JUCE in the downloaded "Hise-develop" branch. You need to copy all the files from the submodule into this folder.

From now on, the Projucer application will be launched inside this JUCE folder.

@David-Healey I am not using GitHub and cloning procedure.

Previously, I was just downloading and compiling the Hise branch. What do I need to do to use it this way?

@David-Healey Sorry for the noob question,

What we need to do is to download the modules, extras & projucer folders in the submodule repository?

Then copy them to the tools/projucer folder in the latest Hise develop branch that we downloaded them from?

@dannytaurus @resonant Thanks!

I'm having trouble configuring the selected tab to appear wider and aligning the other buttons accordingly. Can anyone help?

HiseSnippet 1155.3ocuW0sahbCE1CgIJP6tMqZe.FsWrkzDgX3mjTkMpoPRZQsPnKjnJsMMx3w.VYvFMimrgVsRaeC5iTeF5yPuJpWzq6MsGOy.yP.QVHz5qlye96yGermia3HHTWWgCRKcqgCnHsOTu4PtrWkdXFGU8Xj1S0qgckTGi.UkGN.65RsPZZq8UJEZoRh7G+0WTFai4DZjJD5BAiP+VVelLRaii9Fls8oXKZKV+XdW7npDAuhvV3A7YM8bnAXx03tz5XkaIzQeM1sGR6yzIVEIEI61tnIF2YOy16Rauu4dlz8Ikr9bBASJ0lXVn.Fos9IVLovooDKotvjVVXMrYOwa3A.bAyk01lpDLQMAjCTipziYa0XTxwEgzR1HJUsVPp5SzqwrXi0Gkx1z2fQTDwSZZIlGkLW.JoEiRICnzyzaRbXCjQVT74CzqxgcvNXXuINUB7Ek3SWSuh.7fKy1GeM8TGPXbDYJVJ2NFEykaqCRqFvVjqz3FriQ8yqcU4ya05r5MMNznzAwL0.10J6IkfBvzqubjMk9FXN0dj5zcDNFYXfTtCLXFuL9jBJ1d6sR+yoMfQTjulcI39HB2kJqH5OPvAgLO22imarMLkaatEvXUniiOjQyaBBb49yvjAm0UEBW5HrqfssaCEoYDbeejRdnEHx25muXbaFmZzwiSjLA2XJOyPFA+NPty1ipVxorEDrsAy5VfpwfOKiaQu8rNQAA.kJU5T2OOFkuxZS4ck8BylpkSPFcprZVWnJbDo7Q9PCVXFX1YgKTzUg5g9L8EuHbADDCr9ea5oWtwml7WtigzwOhnQrTUcgjdFOieFAlLi6apSmYZKDJapyLMqt1wYdAlg60uM0I99gxQ3X1jmcW+86rKInTKliBdUNSd1.Zn7oBaK0YR02SeRGEVqBecd0iwRr5venNvuATGISQGsio2.W2FbUPJ8iotWKECfq1GWfiz1P5a8ogWTDrQfXVp.BDLQ2Fcmb8iFNV3ce2QugYIgaf00dIH2ix51Spjx.RR5sxfEfK9FZUdCGJTgntlAsPvmON7+3LgOhbylB4ejTnPLJ7tNKbFnviD9hwy.7EF9hOR3KEC9eyYgguzbgOc.7OYz+oT283i9F59eOQwWqXfCkBiA+um.7jZHDSR6OpwgTqu4l2kSERagiE0oI6mlnkj.suBaw7biq+lQGdmjwod.FmeUv3O5O9yecwY7hjXKrJn4uK93gqrD6Cw3hqjRg6Nj9+FiKsJX7c+xl+viiwS2VHzPpvxyFKmrKUU+6gFfe+MQqgp1+3tL4v382u.stlatst99Rwmo2fII8lMGSLCNB+X7+BNF1v+SzOoSGJQFQvj5m98Ka28O.7uR3IY7t0vRGFTVoW2qeSnDgPAz4pN1TkOITWBDHmSIqx.MobKeg+AFgFMUxZgFMGYD0GSbDWQBZ5Q8jhM70.bh6+jqTva+.YCSjeiPwyy8gW3bEgL4TMUf4W1.KrrAVbYCrzxF3tKaf6srAt+CGn5AneomTzO3XCBUqwI9cNpocBGCUf9Uqn+Ev0tpBc

const var NUM_BUTTONS = 5;
const var PageButtons = [];
const PagePanels = [];

for (i = 0; i < NUM_BUTTONS; i++)
{
    PagePanels[i] = Content.getComponent("Panel" + (i+1));
    
    PageButtons[i] = Content.getComponent("Button" + (i+1));
    PageButtons[i].setControlCallback(onPageBttnControl);
}


inline function onPageBttnControl(component, value)
{
	local idx = PageButtons.indexOf(component);
		
	for (i = 0; i < PagePanels.length; i++)
    {
        PagePanels[i].showControl(idx == i);
        PageButtons[i].setValue(i == idx && value);
    }

}
onPageBttnControl(PageButtons[2], true);

@sletz Thanks for the suggestion. I tried that and same result.

Now I understand that rather than versions, it is about input output numbers.

For example the below one. Naturally Hise complains about the input output channels. I am not sure how to handle that.

I believe this has been reported before a couple of times. I'm using Faust v2.75.7 and the Ambisonics library isn't working. Has this been fixed in later Faust versions or any plans to fix? @sletz

This is the basic code that I am trying to work. It works on the Faust web IDE, but not in Hise.

import("stdfaust.lib");
import("hoa.lib");

process = ho.fxRingMod(1, 200, 0.5, 12);

@Christoph-Hart Thank you for the info

Sorry for the basic Faust question.

How can I make a selection of the functions below, along with a few more functions, using a single slider?

re.jcrev;

re.zita_rev1_stereo(20, 200, 2000, 3.0, 2.0, 48000);

re.dattorro_rev(200, 0.5, 0.7, 0.6, 0.5, 0.7, 0.5, 0.2);

@resonant I believe this graph is included in the Dynamics FX example in the Hise Tutorial Projects.