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

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

[virtuscapeaudio]

@d-healey Ahh ok...I'm after negating the user doing anything with any file. With such a small file size I assumed it was possible to ship the instrument with everything done for them. Onward!

[d.healey]

@virtuscapeaudio The samples aren't embedded in the plugin, so they have to go somewhere on the user's system, and the user should be the one to choose where that is.

[virtuscapeaudio]

@d-healey Yes sir, understood! thanks for the clarification

[DanH]

@virtuscapeaudio I think with a product of that size you can forget about letting the user choose a sample location. I do and have never had any complaints. It will certainly make your life easier!

[virtuscapeaudio]

@DanH Yes! I just have no idea where to begin to do that at this point..any tips?

[DanH]

@virtuscapeaudio So you'll need to get your head around making installers. Whitebox Packages for OSX and InnoSetup for Windows will create these for you. Have you searched the forum yet? There are scripts and explanations available for both IIRC.

Essentially you create an installer that installs the plug-in files and the samples. If you know where the samples are going to be on each system then you can simply install the Link file which contains the location of the samples (and not have to worry about making scripts to handle creating links files in the installers themselves).

[virtuscapeaudio]

@DanH Yes I currently use Packages. So with the LinkFile I can place everything in the users HOME/Library/Appplication supp.., etc, folder instead of their USER folder? Seems simple enough. I'll give it a go

[DanH]

@virtuscapeaudio well yes but because your plug-in’s system files are in the system library rather than the user library you’ll need a shell script which copies the files from the user library to the system library post-install, as packages can’t actually install files there directly. I think this has been covered in the forum as well.

Have you got an apple developer account?

[virtuscapeaudio]

@DanH ChatGPT helped me cook this up based on the Lunacy Audio CUBE (would love to meet the dev here! ;) ) script which I modified..does this look right?

#!/bin/sh
// Write sample location selected by user to LinkOSX for HISE

//Specify the username
username="your_username"

// First, remove LinkOSX file if it exists
instrumentname="Rhodecase88"
devname="Virtuscape Audio"

FILE="~${username}/Library/Application Support/${devname}/${instrumentname}/LinkOSX"
if [ -e "$FILE" ]; then
rm -R "$FILE"
fi

cp -R "$HOME/Library/Application Support/${devname}/${instrumentname}" "/Library/Application Support/${devname}/"

// Second, use the environment variable from WhiteBox Packages to write the destination to a file
destfile="~${username}/Library/Application Support/${devname}/${instrumentname}/LinkOSX"
printf "%s/Lunacy Audio/CUBE/Samples" "$DSTROOT" > "$destfile"

[d.healey]

@virtuscapeaudio As far as I know // doesn't create comments in a bash script.

[virtuscapeaudio]

@d-healey gotcha! i changed the comments from # to // because when i submit the forum post they were HUGE and underlined fonts lol and my adhd said...I need symmetry

[DanH]

@virtuscapeaudio this script is for making the link file which I just said you don’t need to do .

But you could just let users choose where to store the samples and use this script after all.

Better you try and understand what the scripts doing and how it works - it’s not too tricky.

Did you find any other scripts for packages on the forum?

[virtuscapeaudio]

@DanH OOOohhhh... my mistake.. so If im understanding this correctly, the process goes:

Packages project:

1. place plug-in files and ch1 files

2. Include a LinkOSX file and place it ... where exactly?