@David-Healey yeah that would be a problem. But A hise project folder with hise in the name will not be deleted, that would be nuts. It looks for all HISE Standalone.jucer files and walks the folder hierarchy up to the HISE root.

@ustk said in Export Setup Wizard Problems:

If it's an option yes, otherwise it's not very sexy for keeping different versions intentionnaly

If you're at the level of keeping multiple versions INTENTIONALLY, then you won't need that feature. That's really just a tool so that we can tell noobs to NUKE that stuff and try again fresh.

@dannytaurus said in Export Setup Wizard Problems:

Definitely, although it won't help users who have multiple copies of the source on their machine.

Actually, yes it creates a script that searches THE ENTIRE FILESYSTEM for every copy of the HISE source code and then deletes everything.

I also add the ability of removing HISE plugin binaries and standalone binaries that aren't in the HISE folder.

@ustk I think the issue is that you're using the matrix modulator system in an FX context which basically forces monophonic envelope behaviour and I haven't tested this too much. Can you make a simple test project that demonstrates the issue?

Alright, new features coming in:

• automatic update check. There's a new tool in HISE at Help -> Update HISE. This copies a string with the current HISE stats into the clipboard. Go to the web app/update, paste that buddy and it checks if a new PASSING build is available, then creates the script that pulls the changes and recompiles HISE. It checks against the CI build output so if I fuck up an intermediate commit, it won't be shown there as an update.
• I've also added a ZIP2GIT migration system: if the user doesn't use git, but has copied the zip file, it will migrate the system to use git (install git, delete the HISE folder, initialise it back as git repository and then pull & update). It currently preserves the Faust libraries on macOS, as this is the only thing that is added to the HISE source by the user, but am I missing something here?

I'm also thinking about a "Nuke HISE" tool, that creates a script that clears everything related to HISE (app data settings, HISE repo, PATH variables), etc. This might be helpful when users mess up the installation to get back to a clean slate.

Good points.

Maybe the script should know if we're building open or closed source projects?

Why? It's only building HISE, not your projects.

@David-Healey said in Export Setup Wizard Problems:

proxmox

no, still honking around on VirtualBox, from a scale from 1 to Boomer how deprecated is that?

• Missing FFTW on Windows and Linux.
• Missing IPP on Linux

Ah ok. Is FFTW optional on Linux? I thought this is the standard. I'll add IPP on Linux too, I think FFTW for Windows is a bit of a nerd option, no?

It's trying to install dependencies on Linux that aren't needed.

Which ones? I tried to grep all the build instructions from the HISE readme but they might be outdated.

Just make some issues over there, I'll chew through them.

This tooltip is confusing, check the box if you've already cloned the repo - it's a button not a checkbox and the logic is inverted as the "box" is already checked.

Yeah I've been going back and forth with this UX. So basically what I want is to let the user tick which components he has already installed so that the script can skip that, but that is exactly the other way how you would expect a installer to behave... any idea?

Alright, guys I present to you: The HISE Installation Wizard.

https://hise-install-wizard.vercel.app/

(once this stabilizes, we'll port it over to https://setup.hise.dev, but for now let's enjoy that random 3rd party hoster).

Repo:

https://github.com/christophhart/hise_install_wizard

I think this is the best approach so far. It queries information from the user, then creates a build script which can be executed which should setup the system correctly to export plugins. It even checks the CI build status if I fuck up a commit and then resorts to the last working one. I will add a "AI Agent" mode soon that will spit out a prompt instead of a script so you can have your favorite robot hold your hand during that process if you want, but first let's confirm that the actual scripts work on each system. I did a test run on my mac and windows systems, but I'm so bad at setting up VMs it's not even funny anymore, so I still haven't tested a fully vanilla system yet.

Feel free to add issues in this repo with build issues or feedback regarding the UX.

@dannytaurus yup it's a single path, you can just decide whether you want a robot to hold your hands or not. There will be no one solution that suits everybody, some people have experience with AI agents, some have experience with command line scripts, some prefer manual installation of everything.

@David-Healey We could also provide a "static" build script, but this still has a few advantages. It basically behaves like a build script but is able to interpret error messages and try other stuff while the build script just fails and we'll get a new forum topic where we need to explain how to extract a zip file.

For example the current version on windows tries to download IPP / Faust using a Powershell command, which somehow failed in my VM, no idea why, don't care. The Agent realized this and switched to another method (curl / wget), then validated the files after downloading.

Currently I'm fighting against some issues where the compilation of HISE chokes at the memory but I can't say whether this is an issue of my limited VM resources or something the agent does wrong.

But once the process goes through we can just tell the agent to create a bash script / bat file that performs all those steps, then everybody can choose whether to run the script or use the agent.

@David-Healey the free one from opencode should be fine too (Big Pickle).

@David-Healey yeah a 6gb local model won‘t get you too far. I tried it with Opus 4.5 and it even fixed a compile error I introduced in the last commit…

@David-Healey yes I also noticed the faust config already. Which model are you using? If there are any wrong dependencies it should figure this out but we can of course improve the script I oneshotted it in 30 minutes.

@David-Healey yup you can set it to test mode amd then it just prints out what it would do. It‘s of limited use but I‘ll keep it in until this has stabilized.

All the hours we spend with this subject and now it‘s just „let the robot do that lol“…

@Christoph-Hart alright, there's a hise-setup.md file that contains instructions. Now the steps to install HISE are:

• open your AI agent tool, make sure it has the ability to perform bash stuff
• paste in the prompt "Download and execute https://raw.githubusercontent.com/christophhart/HISE/develop/hise-setup.md as an AI agent to set up HISE on this computer."
• follow the instructions.

Some models will refuse to do this for very reasonable security concerns, but some models will raw dog the content and directly execute it as if there is no evil in this world, so if you get some response like "mimii can't execute sudo mimimi", just pick another one.

I've checked it here on my Macbook and it kind of worked, but I haven't run it on a vanilla system, so whoever wants to be the brave pioneer to test this on a clean system will help out a lot.

@JulesV A fake mouse click won't solve your problem. If you rely on that, then something else is broken. If you need some part of the mouse callback to be executed on initialization, you need to break this out of the function and call it explicitly in onInit.

@dannytaurus no joke. Just run Claude code / Opencode with this agent and tell it to install everything so you can use HISE. Let's embrace the future, rofl.

Yeah let‘s ditch that stuff. I‘d rather experiment with AI agents helping with the setup.

@tomekslesicki yes, if you keep the value range the same, you should be able to switch to comboboxes for named plugin parameters without backwards compatibility issues. The plugin APIs do not store the text value in the DAW project, but the index and the text is a simple text lookup requested by the plugin API.

You might want to test this though as I can't guarantee that there are no glitches with this. Also watch out for off-by-one issues - zero in a combobox usually means not a value so the first item starts with 1.

yes, that's the idea.