MAC preset and locations changes NIGHTMARE!

[mwplugs]

so...i had been using a scriptnode version from about 9 months ago or before and everything worked great. over the last 3 years i had made probably 700 presets for a product im working on...no less than 5000 hours put in total

so i update to a recent hise develop build as suggested by everyone to mac things compatible with new mac stuff

i get that completely working and compiling great. so i compile with my presets baked in assume everything will go smooth...nope

there are multiple levels to why the changes made to HISE user preset system is a MAJOR problem

first off....as hise saves file paths for user presets made within hise with a {PROJECT_FOLDER} wildcard for file loaction...nope that doesnt actually work in compiled VST or AU plugins. it does not load anything with that.

so i do further testing and assume its the old replace {PROJECT_FOLDER} with {AUDIO_FILES} which is the only way Windows presets work for whatever reason...in my head im thinking why isnt hise saving the paths so they will actually recall properly? anyways i digress

so i do batch replace on the nearly 1000 presets ive made all pointing to the AudioFiles folder within hise as im using loop players. that doesnt work either...

so i make a test patch in hise on the MAC and it creates a preset and i examine it compared to what has worked for years...

first off hise has changed fileName=" to data=" thats cool no biggie i batch replace that...nope doesnt work

ok so i now created a user preset within my plugin and viola...i find that it is now using static directories...meaning the actual file path..no wildcard...in fact wildcards for loading audio files DOES NOT WORK AT ALL ON MAC. no {PROJECT_FOLDER} not {AUDIO_FILES} nothing it does not actually work in compiled plugins only in hise itself. well that sucks...but there is more

compiled VST/AU plugins made with hise basically expand the user presets within your hise project upon first launch. this is a cool thing. it has always went to Library/Application Support/Your Company/Your Product etc this has always been the root Library folder directly from the Macintosh HD/Library but heres the terrible part...all of those things...i finally figured out a loose solution...batch replace with static locations replace fileName with data etc. they load finally yayyyy..not so fast my friend

compiled hise plugins for whatever reason...just to make my life helll. are now expanding all the baked in files to Username/Library/Application Support/ etc not the root library...the variable user directory...why was this changed? also why is hise placing plugins in the user library plugins folders and not the main root ones like every other plugin ive ever seen?

it has taken me a long time to get to this point...why were all of these changes made to MAC? on PC the preset structure, the file paths are all the same. Plain and simple i dont even know how to install to a variable username library smh. thats among my many reasons for being frustrated, but i just wish i didnt have to spend the last 20 hours troubleshooting something that was changed, but wasnt broken in any way. almost just making changes to make things difficult.

i would appreciate if you could make a hise commit that properly reads legacy user presets properly, and most of all expands compiled plugins to the root library and not the user one like it did before. if there is a solution for all of this let me know because im at my wits end and have been very close to just burning my rig lol

[d.healey]

@mwplugs

first off....as hise saves file paths for user presets made within hise with a {PROJECT_FOLDER} wildcard for file loaction...nope that doesnt actually work in compiled VST or AU plugins. it does not load anything with that.

Did you build my test project?

Most of the problems you're describing seem to be unique to you and your project. I haven't experienced these issues and no-one else is reporting them. You need to provide individual minimal test projects of these problems so that we can verify they exist and then find solutions for them.

[Matt_SF]

@mwplugs I can confirm : No problem here with presets/audio files loading either. I'm on Catalina with one of the latest commit.