@Christoph-Hart haha, absolute madness from Apple, no one could have expected such an unnecessary change
thank you for the quick fix, that was indeed the solution - now the export runs just fine! you saved me from downgrading my OS again^^

Lets see when I will encounter my next bug with this new macOS update...

Re: ERROR: Cycle inside a single target

Hello everyone,

as I already upgraded to macOS Tahoe recently I was hoping to be able to go through the compilation process of my VSTi plugin as I have been before. Unfortunately I'm getting the same error as mentioned in the referenced thread..

️ Building targets in manual order is deprecated - check "Parallelize build for command-line builds" in the project editor, or set DISABLE_MANUAL_TARGET_ORDER_BUILD_WARNING in any of the targets in the current build to suppress this warning
note: Target dependency graph (3 targets)
error: Cycle inside a single target; building could produce unreliable results.
** BUILD FAILED **

Standalone Export goes through just fine...

@Christoph-Hart One thing I noticed in the previous thread was a message from Christoph implementing a fix regarding the Copy Step - he then committed a fix, which should hold until macOS 20
Now we made the jump to macOS 26^^ so this is the reminder haha

I'm on the latest commit of the development branch and already tried downgrading to xcode 16.4, both unfortunately not working...

Any help is greatly appreciated!

@d-healey I also saw this old post from you, where you build some sort of factory preset system: https://forum.hise.audio/topic/324/factory-preset-creator

Do you feel that such an approach would still be suitable for the current state of HISE?

@d-healey Is an UI component like a sliderpack mandatory in order to save the state of an effect? My preference would be that I do not have to link the effect/modulations to UI as users will never be able to configure these on their own.

Hello guys,

I'm looking to create a sample-based VST which should include 20 factory presets. Therefore I would like to create lots of user presets with all kinds of effects, modulations and more. Currently my problem is, that changing settings within an effect doesn't get saved with the user preset when saving, as no UI component is linked to the corresponding effect/modulation. As the factory presets will go through lots of processing and different effect chains, I want to avoid creating a second interface with linked UI controls just to be able to save the effect chain in the user preset.

Is there any best practice in HISE for saving effects/modulations within an user preset?
I saw the Engine.addModuleStateToUserPreset(var moduleId) function in the Documentation, but actually hoped there would be an easier way such as the SaveInPreset Property of the UI components but for every FX/Modulation/MidiProcessor.

Would highly appreciate some help here! :)