Acoustica
Cherry Audio

Installation

Using the Dashboard Products Product List View Create A New Product Team Analytics Sales Reports Reviews Submissions Settings

INSTALLATION TAB

This tab is used to set up installation instructions. Use this to deliver software or content directly to the user. There are several variables that can be set and sent to Mixcraft 10.

Instructions

Fill out the instructions for your product. Once the user adds the product to their account, do they need to do anything else? These instructions will be emailed to them, but they will also be shown in the Mixcraft in-app store, as well as in the profile area of their account.

There are several variables that will customize the experience.

  • %name%
    This is the user's name. It is their first and last name. IE: "Thank you %name% for your purchase!"

  • %email%
    Use this if your registration system requires them to enter their email. For example, "On step 2, enter your email address '%email%' in the edit box."

  • %download_url%
    This is the download link. If you have provided a download in the Media tab, this will be a direct link to that download. Alternatively, if you have an external download in the installation instructions, this will reflect that download. For example, "Please download our plugin from %download_url%".

  • %serial_code%
    If your product takes a serial code from the Serial Code tab, this variable will be replaced with the user's serial code. For example, "Please enter your serial code in the edit box. Your serial code is %serial_code%"

Custom Installation Settings

These are instructions to assist in installing your product directly into the user's computer.

  • External Download URL
    If your product has an external download URL that does not require user intervention and you wish to have Mixcraft install your product, please enter it here.

  • Sound Fonts
    If you are installing sound fonts, choose this option to have them automatically extracted from the compressed SF2 format.

  • Song Kit Mode
    If installing a song kit or collection of sounds, choose this option. You need to choose between "Song Kit" or "Sound Folder". Song kits show up in the loop library. You need to prepare an MLDB10 database file for song kits. If installing a sound folder, you just need to provide a zip file with your sounds. (You must choose this option if the product type is a sound collection.)

  • Extra uninstall items
    If your installer creates extra files, you will add them here so that when your product is uninstalled it cleans up nicely.

  • Source Folder In Zip
    If your zip file contains a folder at the root, instead of all the files being at the root, you can specify that here. IE: If you have myfiles.zip > files > {the stuff you want to install}, just add "files" for this. In this way, you do not have to make a new zip file if you already have your content set up. It will install everything from within the files subfolder. The end result is that you will not

  • Executable
    Enter the filename of the executable. This is relative to the source folder in the zip. Enter any optional command line parameters and an optional installer success result.

  • Custom
    Reserved for future use.

  • Custom Installation Folder
    If this is not set, the product will be installed by default into %programdata%\Acoustica\Mixcraft\installations\{productID} where productID is the ID of your product. Otherwise, you can specify specific variables.

    %FOLDER_VST%
    This is the user's VST folder.

    %FOLDER_VST3%
    This is the user's VST3 folder.

    %LOOP_FOLDER%
    This is where the user's loops are stored. IE: %programdata%\Acoustica\Mixcraft\loops\

    %FOLDER_TEMP%
    This is the user's temporary folder. (There should be a really good reason to put something here.)

    %FOLDER_TEMPLATES%
    This is where any Mixcraft templates will go.

    %FOLDER_PROGRAM_DATA%
    %programdata%\Acoustica\Mixcraft\ (There should be a really good reason to put something here.)

    %FOLDER_DESKTOP%
    This is the user's desktop. (There should be a really good reason to put something here.)

    %FOLDER_DOCUMENTS%
    This is the user's My Documents folder. (There should be a really good reason to put something here.)

    %FOLDER_PUBLIC_DOCUMENTS%
    This is the public document folder. (There should be a really good reason to put something here.)

    %PROGRAM_FILES%
    This is where programs are normally installed. This is like C:\Program Files

    %PROGRAM_FILES_86%
    This is the 32-bit folder where programs are normally installed. This is like C:\Program Files (x86)

  • Plugin Check
    For third-party plugins, you can add checks to ensure that the plugin is installed properly. Using the registry, file checks, or direct plugin checks, you can verify the installed version. If the user already has installed the software, this will ensure that they do not have to download and install it again. There are four ways to verify if the plugin is installed. > Ensure that the Release Build field is filled in on the Information tab!! <

    BUILD: This simply checks to see if you've downloaded it already. If so, it assumes Mixcraft is up to date.

    VST Version: This will check the loaded plugin version information. If not found or the version is out of date, Mixcraft will download the plugin. Supply a comma-deliminated list of plugin GUIDS. The plugin's GUID looks like {37326531-0000-0000-0000-000000000000} and can be found in the Mixcraft log file. Simply run Mixcraft and load your plugin. Then search the log file for your plugin's name. Find the GUID and paste it into the text field for VST Version. If there is more than one GUID add a comma and the other code.

    File Version: This will check the version on the actual files. Use the variables listed above in the Custom Installation Folder section. For example, this line is used to check the VST2 and VST3 of FilterStep: %FOLDER_VST%\Filterstep_64.dll , %FOLDER_VST3%\Filterstep_64.vst3

    Registry: This is the name of the registry key to read the version info out of. For example, if your product had a key at HKEY_LOCAL_MACHINE\\SOFTWARE\MyPlugin\version , you can use this option to read the version which should be a string in the registry. Make sure to have to backslashes after the HKEY_LOCAL_MACHINE. You can also use the other registry sections such as HKEY_CLASSES_ROOT, HKEY_CURRENT_USER, HKEY_USERS, or HKEY_CURRENT_CONFIG. Just make sure to use the double backslash.

  • Uninstall
    This option can be used to remove a product that was added via a third-party installer. You can use the variables from the Custom Installation Folder. For example, if I wanted to uninstall a product called "my-plugin" and the uninstall command was "C:\Program Files\my-plugin\uninstall.exe", I could add "%PROGRAM_FILES%\my-plugin\uninstall.exe" to remove it.