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?
@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 :)
@David-Healey I understand, but isn't this technically vibe coding? @Christoph-Hart
Also, I think it seriously jeopardizes the future of the profession. Saying that AI can't produce good plugins while simultaneously training it to do so is, in my opinion, wrong and will pose a long-term health problem for those who make a living doing this job :)
I think AI could be used this wrongly :)) Wouldn't it be much better to focus on analytics and DSP topics, as I mentioned above?
Please correct me sorry if I'm wrong. But as far as I remember, when people here were talking about creating AI-powered plugins, they were referring to plugins that use AI for DSP operations, analysis, etc.
But how and why did we get to the point of writing code using AI? I find that weird.
Isn't writing code and creating plugins with AI a bad idea?
@Dan-Korneff But this isn't a solution for loading the plugin with the settings the user saved in their DAW project, is it? This issue happens on sliders too, not only buttons.
@Christoph-Hart Could you find a solution for this? This is a big one.
@Lindon said in Plugin parameter values in Pro Tools doesn't load as saved:
Frankly I abandoned AAX...
Oh no!
@gorangrooves @Lindon @Dan-Korneff @orange @Fortune
Were you able to resolve this issue in Pro Tools? Which AAX SDK are you using?
Has anyone previously encountered a situation where the plugin parameter values in Pro Tools didn't load when the DAW project was loaded? VST and AU work, but AAX settings don't load when the DAW project starts. PT 2025
