Hello!

I thought that maybe for some this Inno Setup script could be useful. It installs the plugin + samples automatically on the user's computer.

It does the following:

1. Asks the user where they have their VST3 plugins folder. {commoncf}\VST3 is selected by default, but the user can change it.
2. It then asks where you want to install the samples.
3. And finally it creates the LinkWindows file with the chosen location of the samples.

(In this case I also added the file "AudioResources.dat" so that it is automatically installed in the userappdata folder)

In this way, the user simply opens the plugin and already has everything configured.

Paying attention to the * symbol at the end of the source file location because it includes the folders inside the selected folder. For example, inside the "D:\Downtown Grand Piano\Samples Folder*" location I have the folder called Downtown Grand Piano Samples. Inno Setup will include the folder inside “Samples Folder”, which is "Downtown Grand Piano Samples" (You can check the Inno Setup documentation if you need to understand this better.)
Then the linkWindows file is autogenerated with the location chosen by the user + \Downtown Grand Piano Samples at the end.

(I received help from GPT to automatically generate the linkWindows file, although it took me some time to make it work properly)

[Files]
Source: "D:\Downtown Grand Piano\AudioResources.dat"; DestDir: "{userappdata}\ZAK Sound\Downtown Grand Piano"; 
Source: "D:\Downtown Grand Piano\VST3 File\*"; DestDir: "{code:GetVst3Directory}"; Flags: recursesubdirs
Source: "D:\Downtown Grand Piano\Samples Folder\*"; DestDir: "{code:GetSampleDirectory}"; Flags: recursesubdirs createallsubdirs

[Code]
var
  Vst3DirectoryPage: TInputDirWizardPage;
  SampleDirectoryPage: TInputDirWizardPage;

procedure InitializeWizard;
begin
    SampleDirectoryPage := CreateInputDirPage(wpSelectDir, 'Select Samples Directory', 'Where would you like to install the samples?', 'Select the location where you want to install the samples (2.58GB). You can use an external drive if you have one.', False, '');
    SampleDirectoryPage.Add('');
    SampleDirectoryPage.Values[0] := ExpandConstant('{commoncf}\VST3\Downtown Grand Piano');
    
    Vst3DirectoryPage := CreateInputDirPage(wpSelectDir, 'Select VST3 Directory', 'Where would you like to install the VST3 file?', 'Select the default location of your VST3 plugins. In most cases, there is no need to make any changes.', False, 'Size: 29MB');
    Vst3DirectoryPage.Add('');
    Vst3DirectoryPage.Values[0] := ExpandConstant('{commoncf}\VST3');

 end;

function GetVst3Directory(Param: String): String;
begin
  Result := Vst3DirectoryPage.Values[0];
end;

function GetSampleDirectory(Param: String): String;
begin
  Result := SampleDirectoryPage.Values[0];
end;


procedure CurStepChanged(CurStep: TSetupStep);
var
  LinkWindowsFilePath: string;
  LinkWindowsFileContent: string;
  SampleDirectory: string;
  BaseDirectory: string;
begin
  if CurStep = ssInstall then
  begin
    BaseDirectory := ExpandConstant('{userappdata}\ZAK Sound\Downtown Grand Piano');
    ForceDirectories(BaseDirectory);

    LinkWindowsFilePath := BaseDirectory + '\LinkWindows';
    if FileExists(LinkWindowsFilePath) then
      DeleteFile(LinkWindowsFilePath);

    SampleDirectory := GetSampleDirectory('');

    LinkWindowsFileContent := SampleDirectory + '\Downtown Grand Piano Samples';

    SaveStringToFile(LinkWindowsFilePath, LinkWindowsFileContent, False);

@bendurso Well, I just made my own svg paths for the waveforms. If someone needs them, here it goes:

Sine
110,109,0,0,0,0,0,0,72,66,98,0,0,200,65,0,0,0,0,0,0,150,66,0,0,200,66,0,0,200,66,0,0,72,66,101,0,0

Saw
110,109,0,0,200,66,0,0,72,66,108,0,0,200,66,0,0,0,0,108,0,0,72,67,0,0,200,66,108,0,0,72,67,0,0,72,66,99,101,0,0

Square
110,109,0,0,0,0,0,0,200,66,108,0,0,0,0,0,0,72,66,108,0,0,72,66,0,0,72,66,108,0,0,72,66,0,0,200,66,99,109,0,0,72,66,0,0,0,0,108,0,0,72,66,0,0,72,66,108,0,0,200,66,0,0,72,66,108,0,0,200,66,0,0,0,0,99,101,0,0

Triangle
110,109,0,0,0,0,0,0,72,66,108,0,0,72,66,0,0,0,0,108,0,0,200,66,0,0,72,66,108,0,0,22,67,0,0,200,66,108,0,0,72,67,0,0,72,66,101,0,0

Random
110,109,0,0,0,0,0,0,72,66,108,0,0,160,65,0,0,72,66,108,0,0,160,65,0,0,240,65,108,0,0,32,66,0,0,240,65,108,0,0,32,66,0,0,160,66,108,0,0,112,66,0,0,160,66,108,0,0,112,66,0,0,160,65,108,0,0,160,66,0,0,160,65,108,0,0,160,66,0,0,112,66,108,0,0,200,66,0,0,
112,66,108,0,0,200,66,0,0,32,65,108,0,0,240,66,0,0,32,65,108,0,0,240,66,0,0,180,66,108,0,0,12,67,0,0,180,66,108,0,0,12,67,0,0,32,66,108,0,0,32,67,0,0,32,66,108,0,0,32,67,0,0,140,66,108,0,0,52,67,0,0,140,66,108,0,0,52,67,0,0,72,66,108,0,0,72,67,0,0,72,
66,101,0,0

They're SVG paths. So you can customize them within a panel :)

@oskarsh Another friendly bump.

I want to use it to move panels down/up.

@d-healey oh, I found the solution on this post: https://forum.hise.audio/topic/4355/changing-impulses-in-scriptnode/15

@d-healey It works on mine, and it's a M2. I didn't receive any complaints either.

@d-healey said in Compiling macOS Components and VST3 Doesn't Put Them in the Project Folder:

In a recent commit of HISE Christoph removed the copy step so it should no longer be moving the plugin files automatically (although this might only apply on the latest MacOS version I'm not sure).

I can confirm. I'm using Sonoma 14.3.1, and the compiled plugins are now located inside the project folder. That was a good surprise :)

@ThinkTank You have to add this:

const var ParametriqEQ1 = Synth.getEffect("Parametriq EQ1");
Engine.addModuleStateToUserPreset("Parametriq EQ1");

(Replace ParametriqEQ1 with your real EQ name)

@alfaholic This is how to copy/paste components: https://forum.hise.audio/topic/4408/copy-paste-component-following-feature-requests-thread?_=1696542841615

@bendurso I just realized that setting the Source Length to the same sample length (2048, I was using Automatic mode before) and enabling FLAC compression does the trick to obtain the same file as the example.

Beautiful page. I think the commercial license prices and FAQ are very useful for new potential users who want to use Hise :)

@Lindon I was referring to a toggle option, like "Use strings instead of numeric values." So instead of looking for numbers, it would look for and save string values instead. This would only work when it’s enabled, so it won’t break any existing plugins.
But it was just an idea; maybe it doesn’t really make sense.

@obolig Are you using convolution reverb? Do you have IPP activated on Windows?

@Lindon @d-healey Thanks guys. Yeah, saving it into a combobox or panel looks like a bad idea. Using a label to remember the selection worked for me.

I don't know if it makes sense to make a request in Hise to store Strings as an option in comboboxes or panels, in adittion to numbers.

@d-healey I want to include samplemaps from other expansions, and is possible :)

@d-healey I want to store the selected expansion. And I don't know how many expansions have the user installed, so the number value won't work.

I want to save the selected item’s string (name) in a preset rather than its numeric index value from a panel’s popup menu. How can I achieve this?

@d-healey Mm just doesn't make the call. Inside Hise it works ok. Maybe it's just something of my computer. Maybe you could try the exported plugin on your computer? :)

@d-healey Weird. I tried Reaper and the standalone version.

It works fine inside HISE, but after exporting the plugin, Server.callWithGET doesn't work. Is there a flag or setting I need to include? The issue only occurs on Linux—Mac and Windows work correctly.

@d-healey said in Compiling HISE with Faust on Linux:

sudo apt update
sudo apt install faust

This worked for me, thanks!

@d-healey said in Compiling HISE with Faust on Linux:

I published on Patreon today a video showing how to compile HISE on Linux with Faust?

Oh yes, I did see the video—thanks! I was also having an issue with IPP after the "Linking HISE Standalone" process. After watching the IPP section in the video, I thought that maybe the order of the IPP paths mattered. So I arranged them in the same order you did, and the error disappeared.