Installers
-
@Christoph-Hart said in Installers:
Be aware that the AAX plugins have to be at the global /Library/Application Support/Avid/Audio/Plug-Ins folder and not the user ~/Library/... path. This is a problem if you are using the current user's home domain by ticking the last checkbox in the advanced settings:
I'm having a slightly different problem I can't seem to access the user ~/Library (which is where the VST3 folder is located.
I've triedchflags unhidden ./Library/
from Terminal, but get access denied. Yay!!
-
I was able to create a shortcut for the user library and access thru there
My next issue involves confusion over the source and destination. When you add a folder to your list, what is that actually selecting?? I went thru and added my plug, and it automatically selects the Source and Destination. In Inno Setup, I could script the source file, and it's destination. This just makes me scratch my head. -
I think I got it sorted. Add folders and sub folders (case sensitive) to your destination, then right click and "add files".
-
Or in this case, just use "Absolute Reference"...
-
@dustbro These examples are very useful, you can easily modify them. there are templates for Whitebox Packages and Inno setup ;)
https://github.com/olilarkin/wdl-ol/tree/master/IPlugExamples/IPlugEffect/installer
-
@orange Thank you!
-
@orange @Christoph-Hart When I use the installer I made with Inno, the AAX plugins install as folders instead of plugins and aren't recognized in ProTools. Any experience with this?
-
For some reason the AAX plugins end up in a wrong folder structure so I have this beautiful gem in my build script:
xcopy "build\AAX\%plugin_name% x86.aaxplugin\Contents\Win32\%plugin_name% x86.aaxplugin" "build\AAX\%plugin_name% x64.aaxplugin\Contents\Win32\" ren "build\AAX\%plugin_name% x64.aaxplugin\Contents\Win32\%plugin_name% x86.aaxplugin" "%plugin_name%.aaxplugin" ren "build\AAX\%plugin_name% x64.aaxplugin\Contents\x64\%plugin_name% x64.aaxplugin" "%plugin_name%.aaxplugin" ren "build\AAX\%plugin_name% x64.aaxplugin" "%plugin_name%.aaxplugin" rmdir /Q /S "build\AAX\%plugin_name% x86.aaxplugin"
-
@Christoph-Hart Inno script? or HISE command line?
-
@dustbro That looks like batch scripting to me
-
I made this template for Inno Setup. It works for VST2 / VST3 / AAX...
Also it is compatible with 32 & 64 bit installations with checkbox. It also checks 32/64 bit versions, if the system is x86, it won't allow to install 64 bit plugins.
Just modify the necessary sections with line by line for you.
Cheers ;)
-
@orange the script is almost exactly like what I have.
It turns out to be a PACE signing issue. Although the plugin shows as being a folder instead of the AAX plugin icon, it's working. Good enough for me! -
@dustbro Good to see it is working.
Actually I couldn't managed to add the AAX icon to the aax plugin folders, but aax plugins work without any issues ;)
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.
-
@orange I just noticed this at the end of compiling AAX:
Maybe we can set the folder Icon with the installer as well?
-
@dustbro Hise creates plugin AAX folders with the icons. but I couldn't managed to add this icons to installers. It would be cool that if somebody can share how do it :)
-
@orange mac or pc? With inno, I was able to add my own custom icon to the exe
-
@dustbro In Inno only. Can you send the magic code for the icon?
-
@orange I used the script wizard to get started. It's one of the setup options.
-
@dustbro Thanks mate, I will check it out ;)
-
This post is deleted!