How to avoid users having to unpack an hr1 file on first run of an instrument

[pcs800]

@d-healey said in How to avoid users having to unpack an hr1 file on first run of an instrument:

You include the samples with inno setup and it puts them in the location you choose. You need to write a script for innosetup to run after installation to create the link file - or you could write a script in your plugin to make it create the link file on first load.

If i write the script in innosetup, how do I know where it should place the linkwindows file?
Or if I put the script in the plugin itself to create the link file on first run, where dos the file get placed?
Should I ask chatgpt to write it for me, or is someone here going to get more specific?

[d.healey]

@pcs800 said in How to avoid users having to unpack an hr1 file on first run of an instrument:

how do I know where it should place the linkwindows file?

In the plugin's app data folder, that's the same on all systems. You'll need to create the sub-folder tree if it doesn't already exist.

@pcs800 said in How to avoid users having to unpack an hr1 file on first run of an instrument:

Should I ask chatgpt to write it for me,

You can try, but I wouldn't run the code unless you know what it does. Scripts that mess with files can cause problems if not written correctly.

[pcs800]

@Lindon Actually I am extremelmly familiar wth Windows IS,s. I am a retired IT pro and dealt with windows xp on up thorugh win10, and every server version in between. VN's and Linux as well.
I have yet to see an OS hard drive so small, that nothing can be installed on it. In fact, isn't the vst3 standard that all vst3 plugins are placed at OS drive\Program Files\Common Files\VST3?

As far as mac, maybe I will create those later, but for now,since I am new, I would like to create windows vst3's only.

I do not know how to create a script that allows the user to set the samples location. SO assuming I put them in say [userdocs}\company name\product name\samples
Couldn't I just include this linkwindows file with that path already defined?

[d.healey]

@pcs800 said in How to avoid users having to unpack an hr1 file on first run of an instrument:

I do not know how to create a script that allows the user to set the samples location.

This is what the hr installer does already.

@pcs800 said in How to avoid users having to unpack an hr1 file on first run of an instrument:

Couldn't I just include this linkwindows file with that path already defined?

I didn't even think of that but yeah, actually I think that would work since it's the same location on both systems. The only issue I see is how do you get it in the app data folder on the user's system because they will have a different username to you. It's possible Innosetup provides a wildcard for the username though, I can't remember, so check the documentation.

[pcs800]

@d-healey inno actually does provide a wildcard for that. I think it's something like {userprof}\etc\etc
So, where exactly do I put this linkwindows file?

[d.healey]

@pcs800 said in How to avoid users having to unpack an hr1 file on first run of an instrument:

where exactly do I put this linkwindows file?

https://forum.hise.audio/topic/12517/how-to-avoid-users-having-to-unpack-an-hr1-file-on-first-run-of-an-instrument/8?_=1745943229818

[pcs800]

@d-healey So I have inno put it in {userProf}\AppData\Roaming\company name\Product name\LinkWindows ?

[bendurso]

@pcs800 said in How to avoid users having to unpack an hr1 file on first run of an instrument:

Couldn't I just include this linkwindows file with that path already defined?

I made a post about that a long time ago:

https://forum.hise.audio/topic/7832/automatic-installer-for-windows-inno-setup-script

[d.healey]

@pcs800 I think so, try it and report back

[pcs800]

@d-healey I just did it manually (not in inno) and it worked.
I put the LinkWindows file at C:\Users\pcs80\AppData\Roaming\company name\product name\LinkWindows
Which would be {userProf}\AppData\company name\product name\LinkWindows

Inside the file I specified the location of the samples, and it worked.