@Christoph-Hart said in Export Setup Wizard Problems:

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

So I've been thinking and this doesn't make the process any simpler for a newcomer, it actually makes it more complicated and harder to solve when the AI screws up.

I have a much better solution. A simple bash/batch script. This is what I've been using for years for automated builds.

All a new user would need to do is run install_hise.sh. It could even detect an existing install and prompt to update instead.

@griffinboy Hello?

@JulesV
I've never worked with it before. If it doesn't work right away, you could maybe use a broadcaster for it. But @David-Healey probably knows more about that! :-)

If there are any problems, it definitely makes sense to compile HISE as a plug-in and then load the project directly into the DAW to try it out.

@pcs800 Looks like I may have found my own answer.
File.writeAudioFile(var audioData, double sampleRate, int bitDepth)

@Christoph-Hart Got a weird one...
Changing the target from the dropdown, the modulation stays on the previous target.
The dragger appears on the new one but the modulation is still heard on the first target...

zrg.gif

@David-Healey sweet, I'll give that a shot. Thanks again for the help!

@David-Healey
Hey David,
That's a very kind offer! Thank you very much. I still have to fix three errors in the project, and then I'll send you a download link via message next week.

I'll take a look at the video.

I'll get back to you with the data next week.

Thank you very much! :-)

@David-Healey Yeah very true, that came from a mod I've made for audio inputs that couldn't be shared with other projects, but that's a different matter...

@GUJIAN You could try an earlier commit

@Christoph-Hart I understand, thanks for the helpful advice.

@David-Healey

I had to make a slight tweak to the above, to fix some parameter 0 errors in the console:

inline function savePresetAs() { FileSystem.browse(FileSystem.getFolder(FileSystem.UserPresets), true, "*.preset", function (f) { var filePath = f.toString(f.FullPath); var parentDirectory = f.getParentDirectory().toString(f.FullPath); var userPresetsDirectory = FileSystem.getFolder(FileSystem.UserPresets).toString(f.FullPath); if (parentDirectory == userPresetsDirectory) return Engine.showMessageBox("Invalid Location", "Please choose a sub folder to store the preset.", 0); if (!filePath.contains(userPresetsDirectory)) return Engine.showMessageBox("Invalid Location", "Please save the preset within the User Presets folder.", 0); Engine.saveUserPreset(f.toString(f.FullPath).replace(".preset")); }); }

This seems to work now. Maybe a HISE version issue, as this thread is quite old now.

@ustk Ah I see. I have a working algorythm in Pure Data, is there a way to implement that in HISE as script och c++ code? In PlugData (a flavor of PD), you can export C++ code.

Still broken

Aha mystery solved, I broke it myself in my fork when I commented out these lines to temporarily fix another problem :p

https://github.com/davidhealey/HISE/commit/21eb98a5c364d7333ee5babaf2a783b408121547

@Yannrog you need XCode to do compilations on MacOS

@Ben-Catman If I understand what you mean, I'm pretty sure you'd need duplicate effects on each output. If you want them all controlled by a single set of UI knobs/buttons you'd need to script the connections.

@David-Healey Gotcha. Somehow my brain didn't translate virtual instrument in to VI 😂

@JulesV Yep it's broken, make a bug report. I suspect this is related to all the recent mod matrix changes.

@paper_lung @JulesV You shouldn't really be copying any files by hand. Too much room for human error.

Let git do the work with the command in David's original post:

git submodule update --init --recursive