Just a quick question without polluting the thread to much.

Is this what I need if:

I want to create predefined modules only in "dev mode" (meaning I can use a macro processor during development and disable it before export) I want to add scripts to those modules (they would be scriptFX that are using their process callback) add/remove corresponding buttons on the interface

The rationale behind this is to dynamically create a set of tools (modules + scripts + components) that are helping me during development then throw everything away before export with a simple macro (or uncommenting an included file which is about the same)

@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

@Orvillain The ch file is just the samples, not the sample map. The sample map is embedded in the plugin.

There is no method for adding additional data to the sample map, a separate file (or files) is the way to go. If these are data files (like json or xml) you need to put them in the app data folder when the plugin installs so that you can find them. If you want them to be embedded in the plugin you need to make them .js files and valid script so that they can be included as scripts.

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

@Lindon Still a good read either way. Good stuff to know. 🤛

@David-Healey I’m changing the array right away. Thanks a lot and Yeah :D I finally got all the mechanical recordings done in the studio. Since I had already finished the grueling dynamic velocity layers a while ago capturing the mechanical sounds this time around was an absolute breeze in comparison.

By the way, I watched your Ardour video and built my own workflow for sample editing based on it. It is incredibly helpful, thank you so much for putting that out there.

@ustk Thank so much you for the snippet!
and the comments are really helpful

@Christoph-Hart awesome! I was in the same situation so 👍

@document-cat Full guide here: https://audiodevschool.com/courses/hise-bootcamp/

@David-Healey Thanks, just getting the new error when I built the latest version. Never happened before. Good to know!

@Christoph-Hart how can i do this with opencode? (get it to always check the code rather than me going round in circles with the ai) i have opencode installed on my commandline.

@David-Healey i originally mad the project on my old laptop that i sold, then i moved to a windows laptop, did the ritual of installing hise (MUCH easier on windows) and vs code. it just exported out of the box, and that was what i uploaded as my first vst. then when i installed kubuntu on that laptop, and downloaded the linux vst i made, it wouldn't play sounds (but my other audio effect plugin worked fine) also, i don't know why this laptop misses my keystrokes so much.

@ulrik Thanks

Ok it's no bug... I have READ_ONLY_FACTORY_PRESETS=1 and I assumed, naively, that I could prepare a User folder in advance. But since it's shipped with the binary it is treated as factory... Shame...
So in plugin, if I create a new Folder in the first column as a user would do, it's working...

gclfo.gif