I'm sure you guys know the situation... creating software for different platforms requires multiple computers. Not only do you need a Mac and PC, but you need multiple versions to test different operating systems and software updates. A few years back, I got tired of switching between multiple computers to get the job done, so I created triple boot PC/Hack/Linux machine. It works well. No complaints. Then I decided to upgrade my GPU to an RTX3090 for faster 3D rendering. It's quite a beast! The issue is MacOS does not work with Nvidia chips, so every time I wanted to boot up macos, I had to unplug my GPU. I also started to get annoyed by not being able to use multiple OS at one time. Powering down MacOS to use Windows can quickly get old.
Since I'm relying heavily on virtualization to run my mini datacenter, I took a shot at creating a virtualized workstation. The result?

One computer that simultaneously runs Monterey, BigSur, Win10, Win11, Linux desktop and Ubuntu server!
I'm still in the testing stages, but it's working wonderfully. I've successfully exported plugins from HISE on each platform.
The system is running on Proxmox. Not to be confused with things like VirtualBox or Parallels (which are type 2 hypervisors that run on top of an existing OS), Proxmox is a type 1 hypervisor. That means that your computer's actual hardware is divided up and given to each virtual machine.
Since the allocation of hardware is sectioned off and given to a Virtual Machine, that means you need a computer with a bit of horsepower to use multiple operating systems at the same time, but you may already have what you need. Or worst case, You only run 1 OS at a time with full resources.
By using some utilities like VirtualHere (share usb over ethernet) and Barriers (use one mouse/keyboard to control multiple computers) I'm able to use one set of hardware resources (usb sound card, dongles, etc) and share them with each computer. Each system sees the devices as if they are actually attached to the computer. No layer in between. The only downfall is since it's "directly attached", you can't share your sound card with multiple machines simultaneously.... I'm mean, that sounds like a nightmare anyway! hahahh
Right now, the Mac virtual machines feel like they have a little bit of lag, so I'm going to have to install a GPU for those machines to use.
If you guys are interested, I can post some details on building a machine like this.

It looks like you're trying to hook up a gain reduction meter to a dynamics module.
here ya go! in 13 easy steps
I'm using "right click" auto complete as much as possible.

#1 - Add Dynamics module

#2 - Create a reference to the module

#3 - Create a slider and add reference

#4 - create a timer

#5 - Create function for timer

#6 - create variable to hold a reference of gain reduction

#7 - convert reduction to dB

#8 - set value of slider to gain reduction

#9 - set slider mode to decibel

#10 - Start Timer

#11 - test that reduction meter is working

#12 - set slider image to your strip

#13 - test that strip is working

I would love to have SideChain inputs available in the bus routing.

https://docs.juce.com/master/tutorial_audio_bus_layouts.html

Merry merry everyone!

I just ran into this when opening older projects on my new rig. Images and binary are way below 50mb.
Did a little searching and found that this may happen if Visual Studio doesn't use the 64 bit toolset. I think it's some kind of global change between VS2017 and 2019.
Manually setting the architecture in Environmental Variables fixed the problem for me.
https://phoenixnap.com/kb/windows-set-environment-variable

This would be very useful to me as I'm currently designing a downloader app for my products.

Found some useful info to retain attributes for AAX in Inno
https://www.kvraudio.com/forum/viewtopic.php?t=489036

Yes, you have to be careful when "recreating" the AAX. It's all about flags. Definitely works.

We do this:

[Dirs]
Name: "{code:GetAAXDir_64}\{#MyBinaryName}.aaxplugin"; Check: Is64BitInstallMode; Components:aax_64; Attribs: system;

[Files]

; AAX
Source: "{#MyBinaryName}.aaxplugin\*"; DestDir: "{code:GetAAXDir_64}\{#MyBinaryName}.aaxplugin"; Flags:ignoreversion createallsubdirs recursesubdirs; Check: Is64BitInstallMode; Components:aax_64;
Source: "{#MyBinaryName}.aaxplugin\desktop.ini"; DestDir: "{code:GetAAXDir_64}\{#MyBinaryName}.aaxplugin"; Flags:ignoreversion; Attribs: hidden system; Check: Is64BitInstallMode; Components:aax_64;
Source: "{#MyBinaryName}.aaxplugin\PlugIn.ico"; DestDir: "{code:GetAAXDir_64}\{#MyBinaryName}.aaxplugin"; Flags:ignoreversion; Attribs: hidden system; Check: Is64BitInstallMode; Components:aax_64;

@d-healey Back to square one... Inno seems to strip this property when the file is installed, so the icon disappears again
EDIT:
The installer actually appears to ignore hidden files? Plugin.ico and Desktop.ini are missing after inno install.

Also just noticed there's a script in the AAX sdk that changes all attributes for you.

AAX\Utilities\CreatePackage.bat

IF EXIST %OutDir% GOTO OUTDIR_EXISTS
mkdir %OutDir%
:OUTDIR_EXISTS

IF EXIST %OutDir%\..\Win32 GOTO Win32_EXISTS
mkdir %OutDir%\..\Win32
:Win32_EXISTS

IF EXIST %OutDir%\..\x64 GOTO X64_EXISTS
mkdir %OutDir%\..\x64
:X64_EXISTS

IF EXIST %OutDir%\..\Resources GOTO RESOURCES_EXISTS
mkdir %OutDir%\..\Resources
:RESOURCES_EXISTS

echo Set Folder Icon

IF EXIST %OutDir%\..\..\PlugIn.ico GOTO ICON_EXISTS
copy /Y %IconSource% %OutDir%\..\..\PlugIn.ico > NUL
:ICON_EXISTS

attrib -r %OutDir%\..\..
attrib -h -r -s %OutDir%\..\..\desktop.ini
echo [.ShellClassInfo] > %OutDir%\..\..\desktop.ini 
echo IconResource=PlugIn.ico,0 >> %OutDir%\..\..\desktop.ini 
echo ;For compatibility with Windows XP >> %OutDir%\..\..\desktop.ini 
echo IconFile=PlugIn.ico >> %OutDir%\..\..\desktop.ini 
echo IconIndex=0 >> %OutDir%\..\..\desktop.ini 
attrib +h +r +s %OutDir%\..\..\PlugIn.ico
attrib +h +r +s %OutDir%\..\..\desktop.ini
attrib %OutDir%\..\..

@d-healey Command Prompt

https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/attrib

@orange said in Installers:

By the way if anyone know how to add aax icons to the installation files or how to create folders with aax icons, it would be good to share from here.

Circling back to this one. To get the AAX icon to appear on your plugin in Windows you have to run the following command:

attrib +s "MyPluginName.aaxplugin"

@Christoph-Hart is it possible to have the Export function automatically set this file attribute?

@lindon Is it possible that the function is being called in a script that initializes before the modulator is defined?

@nesta99 said in correct naming:

giving me naming errors even after trying following the naming rule

I had the same thing happen. It ended up being something silly for me. I was filling in the company.product part, but keeping the prefilled com.
Deleteing the whole line and typing it in solved the issue for me

post a snip. Are you using scriptnode to create the delay?

@christoph-hart Thank you!

cannot convert 'this' pointer from 'T'

@Christoph-Hart It looks like and issue the parameter data from the snex nodes. Anything I can do to remedy this?

Edit:
Just did a quick text. It appears to only affect the snex_shaper node. I was able to successfully compile the snex_node.