@David-Healey said in Export Setup Wizard Problems:
Was it an Apple silicon system? That might be the difference.
Yeah, it was an M1 MacBook Air. It was a really nice machine, and everything else worked fine. I could run large Logic projects, have loads of running apps, multiple Safari windows, etc.
It was just compiling HISE where it completely fell down.
@David-Healey said in Export Setup Wizard Problems:
Something wrong there, I compile on a VM with less.
Yep, definitely something wrong. Could be the way macOS handles RAM. Could have been something else on my system.
I bought a 32GB MacBook Air and it flies now, so I don't care what was causing it.
@ustk said in Tahoe, safe to update?:
seems easy enough to get rid of the liquid glass crap and tweak a wee bit to get back to a previous look
Let us know how you get on 
@ustk said in Tahoe, safe to update?:
And what about XCode? currently running 16.2, can I update to last 26.2?
Xcode 26.1.1 on macOS Sequoia 15.7.3 working great for me here.
I won't be jumping to the eye sore that is Tahoe anytime soon.
Maybe you could just go to Sequoia?
Tahoe doesn't seem to bring much other than the horrific UI.
@DanH Amen to that! Apple didn't just drop the ball here. The dropped it, stamped on it, set it on fire and threw the ashes into a nuclear reactor.
Hopefully now Alan Dye has gone they might turn it around. Although Apple aren't know for quick turns. Might take years to get a sensible UI back on Mac.
@Christoph-Hart said in Export Setup Wizard Problems:
then everybody can choose whether to run the script or use the agent.
I thought the point of this whole endeavour is to make it a single path for beginners.
@Christoph-Hart said in Export Setup Wizard Problems:
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.
Sounds like my issues with compiling HISE on an 8GB MacBook Pro. Basically impossible.
@Christoph-Hart Genuinely don't know if you're joking or not 
@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
@David-Healey said in NI Insolvency:
live musicians playing virtual instruments
What do you mean by this? Did you mean physical instruments?
@David-Healey said in NI Insolvency:
We already have this, Suno.
Yeah, like this but for continuous music, not making single tracks.
@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
I'll add, with some amount of caution, that in my specific music niche I think there will always be a hard requirement for music made by humans, with tools made by humans, pressed onto vinyl made (supervised?) by humans, and played on arcane gramophones by humans.
What I'm referring here isn't creating plugins with AI.
Dan suggested this.
Yes, I believe this will be the intermediate stage. Where AI can help anyone make the tools they need use to create their music.
The stage after is to simply describe what kind of music (the specific parts) you want to make. That will remove the need for plugins.
Instead of downloading a bunch of different reverb plugins, you just tell the DAW exactly what type of reverb you want and it will create a custom one. Then if you make a really cool reverb you can share it with other people, heck even sell it if it's good enough. Wait... we've come full circle to selling plugins at this point!
Parallel to this is also likely the stage where the end-user just describes what music they want o listen to and it's generated on the fly.
Ahh.. but this is all supposition. Nobody really knows where this will all go.
It might all collapse in on itself and turn out to be a big disappointment. Or it might wipe out humanity entirely.
@David-Healey I think folks are hoping that AI will be integrated into HISE such that you can describe what you want and the AI will guide the build, of just build it.
If that's the case, it might be basically the same as letting AI loose with the underlying JUCE framework. Christoph mentioned this a week or so ago.
@David-Healey I think this in-between download/compile method is more harmful than helpful. Allowing folks to download a pre-compiled HISE but not keeping it up to date.
On a separate note, I'd like to see HISE get back to the master branch. It's just another source of confusion to tell new folks to use develop because master is so out of date.
@David-Healey Yeah, it was meant to be sarcastic. Too dry I suppose. Edited
Panic over? (sarcasm)
https://blog.native-instruments.com/statement-from-nick-williams-ceo-of-native-instruments/
Can't help thinking a message from the CEO would have been better before all the kerfuffle? 
@duma Best to make a new post for your filter issue.