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.
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?
@Christoph-Hart In the plugin, all controls are set to plugin parameters. Also most of them are set to isMetaParameter. And all controls are initializing with default values
@Christoph-Hart When I open a project previously saved in a DAW using a plugin compiled with 2024 commit HISE (I only tried in Reaper and Logic on macOS), with the same plugin compiled with new HISE, the saved settings are not loaded in the DAW. The plugin is loaded with the default state.
Honestly, I experienced the same problem. Presets and saved settings from older projects don't load in the DAW Project with plugins compiled using the current HISE.
I think HISE's backward compatibility has been broken since this new modulation system was added. I have to stay on the January 2025 commit for now.
Thank you for the info.
@David-Healey said in What to do? NAM with MIT & RTNeural with BSD 3-Clause Licenses:
So you need to include the whole license basically (list of conditions and disclaimer) and you can put it in your installer or documentation, you don't need to display it within the plugin.
I think installer way is better. But my installer already contains my own license text. So do I need to paste this license text into my own license text file?
Folks I really need help for the license of the Neural syetems. Sorry for the noob license knowledge.
To clarify,
For NAM:
To use the NAM inside the plugin, we don't need to mention anything, do anything, or make it open source, right?
For RTNeural:
if we want to build a plugin RTNeural inside;
“This product includes RTNeural, Copyright (c) 2026, jatinchowdhury18, licensed under the BSD 3-Clause License.”
Is it enough to just write the text inside the plugin's Credits page? Or anything else we need to do?
@David-Healey Thank you for the info.
Is this cheaper than AWS and GC?
Do you think its performance is good when many users are loading simultaneously?
From what I've seen, a high number of license authentications isn't something classic WordPress sites can handle on shared hosting with limited php workers on it.
And the professional approach is to have separate website hosting and license authentication systems. What do you use for this? My research shows AWS and Google Cloud are commonly used. But I'm not sure if serverless or a traditional system would be better. (AWS Lambda, AWS EC2...etc. which one to choose?)
I hope knowledgeable guys can help; I really need clarification.
@Mors Is it possible to have a faust sync reverse delay?
Here is a reverse delay but not in sync: https://forum.hise.audio/topic/11445/free-reverse-delay-built-in-rnbo/11?_=1774466149983
I have two different NAM models with varying rendering quality: Standard and Feather (which uses approximately half the CPU as Standard).
In HISE, the Standard model works, but Feather doesn't. I've attached the files below.
Do you have any suggested solutions?
@Christoph-Hart said in Agentic coding workflows:
But how and why did we get to the point of writing code using AI
Simple: the latest iterations of the SOTA models make AI coding on par with a reasonably well skilled developer.
It is the begining of the end then :)
For those who think AI can't create good plugins, train your AI yourselves, and eventually this prophecy will finally come true :)
