@Christoph-Hart Nothing that I can test make it work, using develop branch. (note that it crashes with develop when a scriptFX is present in the tree)

A macro or a flag I missed perhaps?

@ulrik of course. Git is the single tool across all software development that pays off. I couldn‘t imagine doing any non toy project without version control. How are you tracking your progress?

@document-cat said in HISE 4.1.0 crashes when compiling faust scriptnodes:

I have just compiled HISE 4.1.0

Latest commit on develop branch?

@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

@David-Healey yep great, and dumping the quarantine worked for me so thanks.

@Christoph-Hart said in Recent commit to Processor.cpp breaking old project:

Also the script is completely empty, all you're doing here is declaring some parameters in the XML.

Not sure what you mean

a3c8b145-6d2a-498c-8e9e-7cfb616e3c57-image.png

c6710f15-5439-4161-8381-4a189005c274-image.png

@Christoph-Hart not that I'm aware of, I didn't even know this macro 🤷♂
I checked and it's 8 as it should...

@ulrik sure

I had Claude give it a go. I also noticed that the linear-slider class is added to knobs, even though they're not linear.

Also made it available in laf and added getStyleSheetProperty too

https://github.com/christophhart/HISE/pull/935

@boim98208 For some reason this was only happening when I did learn midi CC. I decided to just stick with a set CC channel for the knob to be better safe than sorry.

@David-Healey Ahh cheers dude. Yeah I get it now. So I've done this for my factory content and it worked fine. I need to figure out expansion packs, but I would guess it is a similar approach; making sure my expansion pack installers put the files in the correct place, and having the plugin scan on startup.

@David-Healey Thanks David

Also, worth remembering... a compiled plugin CANNOT use the builder - at least for the most part. So what I've also got is a PluginStateData namespace, which maintains a key:value dictionary of module id's to module references. This runs on plugin instantiation, retrieves all of the actual object references, and stores them in a const dictionary.

You should only use the builder to build the module tree. You should not use it for retrieving or storing id's or object references.

@David-Healey That did it! I updated to the latest develop branch and multi-file drag/drop istarted working immediately. Thank you much.

@xxx 100% they can. It's not the best method and doesn't show you how to interact with a server or WooCommerce, it's just a starting point for within HISE.

Just did these renderings for Genki Instruments that just released their Katla synthesizer.
Mostly been working on watch animations, getting a bit bored with that, if anyone needs either a UI design or 3d renders/animations of their plugin, I am available :)
Still 2025-11-06 172656_4.1.10.T.png Still 2025-11-06 172656_4.1.8.T.png Still 2025-11-06 172656_4.1.6.T.png Still 2025-11-06 172656_4.1.12.T.png Still 2025-11-06 172656_4.1.4.T.png

@oskarsh i was having this same issue (and a lot of others when testing a hardcoded Faust FX swapping/reordering plugin idea lol) but what worked for this same DAW crashing bug (with Claude's help) was in the Hise source code changing this line in the "/HISE-develop/hi_core/hi_modules/hardcoded/HardcodedModuleBase.cpp" file from

HardcodedSwappableEffect::~HardcodedSwappableEffect() { jassert(shutdownCalled); jassert(disconnected); factory = nullptr; }

to

HardcodedSwappableEffect::~HardcodedSwappableEffect() { if (!shutdownCalled) shutdown(); factory = nullptr; }

then rebuilding HISE and compiling the plugin again

i want to also clarify i am definitely not an expert at this stuff , but maybe this can help someone in the right direction or for @Christoph-Hart to fix this bug ! the creative potential in easy reordering of is so huge im excited to see it grow

@Oli-Ullmann Thank you so much

Is it possible to tell the AI not to do some of those tasks?

sure. I mean you have to tell it to use these tools in the first place, so if you keep it a secret from your robot, it will never call hise-cli. Once the dust settles I'll try setting up system prompts / agents.md file templates that teach the AI the optimal usage of this tool.

The ROI on it letting it compile the project for you is pretty narrow, so that particular set of commands might not be the most thrilling thing to teach the agent - however the hise-cli offers a script runner that can perform build steps for you.

/hise launch # open HISE /builder reset # clear the module tree /project # Enter project mode export dll # compile the DSP network dll load MyProject.xml # load your XML preset backup export project # VST3 as default export project with format=Standalone # export App /exit # leave project mode /hise shutdown # good bye

is basically the full cross-platform build script that automates the export for you. you then just need to call hise-cli --run "build.hsc" (or even register hise-cli as shell script runner, then the script file itself becomes executable).