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 :)

@JamesC Have you checked the macOS Deployment Target in the Projucer file? Check under the Release section (or 'Release with Faust' if you're using it).

It should be set to 10.13, but it looks like you have it set to 10.09

Wavetable Export ignores residual noise setting · Issue #761 · christophhart/HISE

Description When exporting with the “Convert Samplemaps to Wavetable” tool, the Residual Noise setting is ignored. All other settings appear to be applied correctly. Steps to Reproduce Load a samplemap and select a Loris mode (Zero, Stat...

GitHub (github.com)

Wavetable Export – Residual Noise ignored
Preview applies residual noise correctly, but the exported HWT file bypasses it. All other settings are passed as expected.

Is anyone else experiencing this? I even tried the exported version 4.0.0 of HISE and ran into the same issue. I tested on Windows as well, same problem.

I also tested with the 3.6.2 release, with Loris installed in the HISE app data folder, and got the same issue. That’s strange.. maybe I'm doing something wrong?

This are my settings when trying to export:

I’ve noticed that the Loris wavetable converter (Zero, Static, and Dynamic) doesn’t seem to export correctly. Regardless of which residual noise option I choose (Mute, Mix, or Solo), the exported HWT always sounds the same.

In preview mode, everything works as expected—you can clearly hear the difference between the residual noise options.

Preview Mode - Dynamic Phase / Residual Noise: Mute

Preview Mode - Dynamic Phase / Residual Noise: Solo

However, once exported to HWT and loaded into the wavetable synth:

Dynamic Phase / Residual Noise: Mute

Dynamic Phase / Residual Noise: Solo

Both exports sound identical to the “Mute” version.

The same thing happens in the zero phase mode and static phase mode.

I’m on Mac and using one of HISE’s latest commits. I also tried an earlier commit from before the wavetable synthesizer rewrite (a86dd6e), but the same issue occurs. So I’m not sure how long ago this broke. I do know that about a year ago I created a wavetable-based instrument and it worked fine.

@modularsamples Nice, thanks for the details.

I think I’m going to get a decent Intel computer to compile for Windows and Linux x86—it’ll be easier, hehe.

@d-healey thanks I will check it :)
@modularsamples Thanks, sounds good. I ended up using UTM in emulation mode, but yeah… it’s really slow. I actually have an old Mac running Mint that feels faster than this emulation.

This virtualization with Rosetta sounds promising. But it’s really important that all the libraries and dependencies are installed for x86_64, right? Because if we build HISE using some ARM libraries, then the resulting plugin wouldn’t work correctly on x86_64 machines I think.

@d-healey Oh nice, but if I do it on my computer is free hehe
The proxmox server is a paid subscription right? Or there is a free version?

@d-healey said in OS for compiling in Linux?:

Great, thanks! I also just found something called QEMU, which allows you to emulate (rather than virtualize) any operating system on Silicon Macs. That means I could run Mint on my Mac M4. I’m going to give it a try.

@d-healey This is a bit old, but.. I’m now trying to use Linux on a Silicon Mac. I understand that Mint doesn’t work with ARM processors. If I use Ubuntu 20.04 Focal (ARM version), will the plugins I export work on non‑ARM computers? If not.. is there another alternative?

@VirtualVirgin Like this:

(right click on the container)