Access Virus Editor Osc Filter Env Model C

Access Virus Editor & Librarian update!

Native Apple Silicon Support, USB MIDI support for macOS 10.12 and greater.

Native AAX, AudioUnit, VST, VST3 and Standalone App for macOS and Windows available.

Frequently Asked Questions

Store (Payment, Orders etc..)

What payment methods do you accept?

Our payments are handled via FastSpring which is one of the biggest Ecommerce payment gateways used. They have several different options from PayPal to Credit Cards and even Online Banking options for some countries.

Latest addition is Crypto Currency, if that is your thing. We do offer permanent 20% discount on Crypto Payments.

Add some products to cart and see what options you have in the checkout page!

General

What are the Editor requirements?
  1. You must have the real hardware (or DSP Emu), which the editor is made for.
  2. Version xx.xx.xx requires 64-bit AAX, Audio Unit, VST2 or VST3 host for Mac or PC.
  3. Version xx.xx.xx requires Mac with Metal supported graphics.
  4. Version 1.x and 2.x requires 32/64-bit Audio Unit / VST host for Mac or PC.
  5. MIDI interface. A good one which supports SysEx messages. ESI MIDIMATE XT is proven to work.
  6. Direct MIDI in / out connection between your hardware and the MIDI interface. No MIDI Thru connections or MIDI in only / MIDI out only connections OR direct USB connection to computer if USB is available in hardware.
  7. Audio cables from the synth to sound card or mixer in order to hear the sound.
  8. At least FULL HD resolution display.
Which functions are not available in the DEMO version?
  1. User can not save requested data from hardware to HDD.
  2. User can not store patches from librarian to hardware.
  3. Total Recall is disabled. This means, your last used Editor settings will not be sent to your hardware automatically up on loading the project.
  4. MIDI Learn is disabled. User can not map favorite CC controls to Editor parameters.
  5. Editor parameters are not visible for DAW to automate.
  6. User can not store UI DATA files (arrangements).
  7. Demo version can not be registered.

License

How do I add the license for the Editor to register?

UPDATE 2023-August-28

[ version 1.x & 2.x ] license.key needs to be located in:

[ WINDOWS ] ”login username”DocumentsMystery Islands Music”plug-in name”
[ macOS ] /Library/Audio/Presets/Mystery Islands Music/”plug-in name”/

…in order to register. Reload your project or plug-in instance in order to validate.

 

[ version “3” ie. 25.12.11 ]

Downloaded license.key must be renamed to “(plugin name).license” and placed in: Users/(your username)/Music/AURA Plugins/(plugin name)/ folder.

To make this easy, click on “register” text in the top left corner to open the file browser dialog and open the license file with it. Rest will be automated.

Why Editor says reload license after copying license to right folder?

There are usually two reasons for that:

  1. Editor has failed to read the license file. Make sure the license doesn’t have any additional extensions ie. “Access Virus Editor.license.txt”. If you see .txt appended, rename the file to “Access Virus Editor.license” and try to validate again.
  2. Editor has failed to locate the license file. Make sure the license is in the Editor data folder (versions 1.x-2.x):
Macintosh HD/Library/Audio/Presets/Mystery Islands Music/(plugin name)/license.key

Note that new version has a new location AND name for license. License should be placed in /Users/(your username)/Music/AURA Plugins/(“plug-in name”)/”plug-in name”.license

Sample below:

[macOS] ~/Music/AURA Plugins/Access Virus Editor/Access Virus Editor.license
[Windows] ~MusicAURA PluginsAccess Virus EditorAccess Virus Editor.license

Troubleshooting

Why Editor fails to connect with the hardware?

There are a few reasons why this could happen, so lets make sure everything is right:

  1. MIDI out from your hardware is connected to your MIDI interface input.
  2. MIDI out from your MIDI interface is connected to your hardware input.
  3. Hardware has Global MIDI Channel set as instructed.
  4. Hardware has Device ID set as instructed.
  5. Hardware is in Performance / Multi mode (mono timbral and FX Editors excluded).

If all of these conditions are right and the Editor still fails, check the MIDI interface specs to ensure it can handle large SysEx packages which the Editor & Hardware uses to send program data back and forth.

You can open a ticket with our Support Team if you’re stuck.

Why Editor displays DEMO version after purchasing the license?

You need to download and install FULL version of our Editor in order to register it.

Head down to https://auraplugins.com/my-account/ (login if prompted) and click Edit or Downloads.

  • Download the full installer and license.
  • Install full version.
  • Check license instructions and install license.
  • Re-open the Editor to validate the license.
  • When validation succeeds, Editor says “Registered” in the top left corner.

 

WordPress Cookie Plugin by Real Cookie Banner
Share to...