Is there a way to download these old IPP versions?

I'm using an old HISE version that's a year and a half old, and the latest IPP version doesn't work with VS 2022 on the computer where I just installed it.

@Lindon Is it fixed on your side?

@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.

• NAM uses MIT License: https://github.com/sdatkinson/neural-amp-modeler?tab=MIT-1-ov-file
• RTNeural uses BSD 3-Clause License: https://github.com/jatinchowdhury18/RTNeural?tab=BSD-3-Clause-1-ov-file

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?

NAMModel_Feather.js

NAMModel_Standard.js

@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

@Oli-Ullmann Oh, that's great thank you.

I will try this, I hope when the DAW tempo changes, the values would be updated automatically.