No. FULL installer will overwrite the DEMO version in your harddrive.

We are writing User Manuals as we proceed with the version xx.xx.xx updates.

All manuals will be available in https://auraplugins.com/kb/ once the product update is wrapped up.

If for some reason the installer fails to run, try opening the installer with right click -> open.

This usually solves the problem. Our Editors only interact with the hardware unit, so they’re safe to use.

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.

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.

No. Our Editors are designed to control the real hardware unit from your favorite DAW or with the Standalone Application.