Setting(flag) to not have the plugin start the sample install process when the link file is missing

[DabDab]

@Lindon said in Setting(flag) to not have the plugin start the sample install process when the link file is missing:

HISE_DEACTIVATE_OVERLAY=1

What does HISE_DEACTIVATE_OVERLAY=1 do ?

[Lindon]

@DanH said in Setting(flag) to not have the plugin start the sample install process when the link file is missing:

@Lindon can you not just script that?

script what? The plugin wakes up - trys to read the link file - finds its not there and starts the "standard" sample install dialog...

• So I dont want that to happen, instead-

The plugin wakes up and looks for the link file, finds its not there and does nothing... meanwhile in init I look for the link file - find its not there and start the custom install process we use for samples and all the other stuff we use - meta files, audio files , presets etc. etc. So yeah this bit is all scripted...

[Lindon]

@DabDab said in Setting(flag) to not have the plugin start the sample install process when the link file is missing:

@Lindon said in Setting(flag) to not have the plugin start the sample install process when the link file is missing:

HISE_DEACTIVATE_OVERLAY=1

What does HISE_DEACTIVATE_OVERLAY=1 do ?

"If enabled, this will deactivate the dark overlay that shows error messages so you can define your own thing."

[d.healey]

There is no script method to start the internal installation process.

HISE_DEACTIVATE_OVERLAY=1 will disable ALL overlays, including the built in installer and find samples popups.

[Lindon]

@d-healey said in Setting(flag) to not have the plugin start the sample install process when the link file is missing:

There is no script method to start the internal installation process.

HISE_DEACTIVATE_OVERLAY=1 will disable ALL overlays, including the built in installer and find samples popups.

Ok well thats pretty much what I want I think.

[DabDab]

@Lindon Ok. Understood.

[DanH]

@Lindon script your plugin to look for the link file. And if it doesn’t find it proceed to the install process. I’m pretty certain you’ve made an installer that deals with link files so this sounds completely doable. It’s what my installer does.

[Lindon]

@DanH said in Setting(flag) to not have the plugin start the sample install process when the link file is missing:

@Lindon script your plugin to look for the link file. And if it doesn’t find it proceed to the install process. I’m pretty certain you’ve made an installer that deals with link files so this sounds completely doable. It’s what my installer does.

yeah - sadly our entire install process just got a lot worse - based around the vendors download manager - better called: a download-fail-to-manager...

@d-healey - I may well be looking to your advice on how to do downloads inside the plugin...

[DanH]

@Lindon well give me a shout if you need help. It’s not that complicated.

[Lindon]

@DanH thanks mate - feeling pretty low at the moment so this is a great help.

[DanH]

@Lindon haha. Hold tight. I’ll fire over my proj when home. Hopefully you can make some sense of it

[d.healey]

Would it help if we had a script API call to trigger the built in installer?

[Lindon]

@d-healey said in Setting(flag) to not have the plugin start the sample install process when the link file is missing:

Would it help if we had a script API call to trigger the built in installer?

No sorry - our custom installer installs a lot more than Samples and linkFiles - it does presets, metadata files, audio Files etc. etc. the list and locations are long - 16 different types of thing in Horizen.

I built an installer that gracefully handles all this - given it is provided with all the zip files it needs (called .sfc files) , but their download manager refuses to call it - well they refuse to let it... and their download manager even refuses to download the 16 sfc files, so I may be back to using innosetup and whitebox packages - the only thing their download manager supports - to install the plugin then get the plugin to do the remaining downloads and the install from inside the plugin - yes yes I know its benightedly stupid design.... but I can see little other choice.

[d.healey]

@Lindon They don't even support zip files with the standard extension?

[Lindon]

@d-healey of course they do,...partly: they pass the zip off to the OS to deal with it - so on MacOS it gets unzipped into the download folder - bad for us, because now everything is in the wrong place, and on Windows it gets "shown to the user" in the download folder - not great for the user...who has little or no idea what to do with it at this point...

[d.healey]

@Lindon Ah that's a pain

[virtuscapeaudio]

@d-healey my project is just under 300MB and I also would love to know how to go about bypassing default system so the user has to do nothing but open the plug-in...I'm watching your FileSystem videos on youtube but still scratching my head on this one

[d.healey]

@virtuscapeaudio

Use HISE_DEACTIVATE_OVERLAY=1 to bypass the default system

[virtuscapeaudio]

@d-healey Thanks! So would I now just need write a script that tells the plugin that the files are already found/linked? I see the GeneralSettings.xml which has SAMPLES_FOUND_"1"...Am I thinking about this all wrong?

[d.healey]

@virtuscapeaudio You still need to let the user choose where they want to put the files. Then you need to populate the "Link" file with that location.