PACKAGE CONTENTS

----------------------
WINDOWS package:
----------------------

1. BlueARP_Win_VST2
   - BlueARP.dll: VST2.4, 64 bit
3. BlueARP_Win_VST3
   - BlueARP.vst3: VST3, 64 bit

IMPORTANT: VST3 format has some limitations regarding MIDI functionality. If you need MIDI CC passThru to thr synth,
it is more reliable to use VST2 version of BlueARP

----------------------
OSX package:
----------------------

1. BlueARP_OSX_VST2
   - BlueARP.vst: VST2.4, 64 bit, Intel & Apple M1 (universal binary)
3. BlueARP_OSX_VST3
   - BlueARP.vst3: VST3, 64 bit, Intel & Apple M1 (universal binary)
4. BlueARP_OSX_MFX
   - BlueARP.component: MIDI-FX audio unit to use in Logic Pro X, MainStage, GarageBand, 64 bit, Intel & Apple M1 (universal binary)

----------------------
HOW TO INSTALL BlueARP
----------------------

Before installing newer version of BlueARP, it is recommended to remove the existing version first, unless
you want to use both older and newer version (refer to the next chapter «How to remove BlueARP»).

Windows VST2 version

Step 1. Unzip the package, copy "BlueARP_Win_VST2_vXXX" folder to your VST plugins directory.
Normally it will be:
- C:\Program Files\Steinberg\Vstplugins\ or
- C:\Program Files (x86)\Steinberg\Vstplugins\ (for 32-bit plug-ins on Windows 64-bit)
Step 2. In you DAW (Cubase, FL Studio or whatever you use), re-scan VST plugins folder (refer to the
respective manual on how to do this). «BlueARP» or «BlueARP.x64» (64-bit version) should appear in plugin
list and it is now ready to use.

Windows VST3 version

Step 1. Unzip the package, copy "BlueARP_Win_VST3_vXXX" folder to your VST3 plugins directory.
Normally it will be:
- C:\Program Files\Common Files\VST3\ or
- C:\Program Files (x86)\Common Files\VST3\ (for 32-bit plug-ins on Windows 64-bit)
Step 2. In you DAW (Cubase, FL Studio or whatever you use), re-scan VST plugins folder (refer to the
respective manual on how to do this). «BlueARP» should appear in plugin list and it is now ready to use.
PS. Some DAW applications may combine VST2 and VST3 version of the plugin, in some cases VST3 version
may have priority over VST2 version. FL Studio, for example, has a setting "Combine VST2 and VST3
versions of the plugin".

Mac OSX VST2 version

Step 1. Unzip the package, copy «BlueARP_OSX_VST2_vXXX» folder to your VST plugins directory.
It should be one of the following:
 Hard disk/Library/Audio/Plug-Ins/VST (for all users)
 Hard disk/Users/<username>/Library/Audio/Plug-Ins/VST (for <username> only)
Step 2. In you DAW (Cubase, FL Studio or whatever you use), re-scan VST plugins folder. BlueARP should
appear in plugin list and it is now ready to use.

Mac OSX VST3 version

Step 1. Unzip the package, copy "BlueARP_OSX_VST2_vXXX" folder to your VST3 plugins directory.
It should be one of the following:
 Hard disk/Library/Audio/Plug-Ins/VST3 (for all users)
 Hard disk/Users/<username>/Library/Audio/Plug-Ins/VST3 (for <username> only)
Step 2. In you DAW (Cubase, FL Studio or whatever you use), re-scan VST plugins folder. BlueARP should
appear in plugin list and it is now ready to use.

Mac OSX MIDI-FX version (for Logic Pro X)

Step 1. 
Unzip the package, copy "BlueARP.component" to your Audio Units directory.
IMPORTANT: just take "BlueARP.component", don't copy the entire "BlueARP_OSX_MFX_vXXX" folder,
           otherwise LogicPro might not recognize the plugin.
Audio Units directory should be one of the following:
- Hard disk/Library/Audio/Plug-Ins/Components (for all users)
- Hard disk/Users/<username>/Library/Audio/Plug-Ins/Components (for <username> only)
Step 2.
Restart! OSX caches AU plugins and you won't see your new plugins until you restart.
If it doesn't help, try to:
1. Clearing the folder /Users/graywolf2004/Library/Caches/AudioUnitCache
2. Run in terminal:
   killall -9 AudioComponentRegistrar
3. Remove the quarantine flag by running in terminal
   sudo xattr -rd com.apple.quarantine <your components path>/BlueARP.component
4. After you start Logic, check your system -> Security page, sometimes you might see a warning there about
   the unverified developer/app, so you can choose 'install anyway'.
   (this was relevant for the earlier OSX versions, not sure about the latest ones)

