Aura Plugins Access Virus Editor v24.10.22 WiN MAC Incl Keygen-sneakz

I wonder if this GUI can be incorporated into the Usual Suspects emulators somehow.

Changelog and Known issues:

i love u for that

I don't understand why the file size is so big...?

Access itself recommends using this software.

https://ibb.co/5F25xJ9

Thank you

Noob question! Can this be used as a soft synth or does it require hardware to work? Thanks in advance

I love you sneakz

I bought this plugin, when the first version of the DSP56300 was released without a GUI.
It works :)

but it´s really a lot of work, and i can´t recommend this worflow today.
The GUI Version is the way to do.
The Problem ist, that the Aura Editor has no recall function for the DSP out of the box.
You need to save the UI Data and reload it.

Buuuuut: ITS SUPER COOOOOOL
You interact with the DSP like the real Hardware.
I had the Original Virus C and TI before many years.

So for this you need:
LoopMidi (Google, Free Software)
You create virtual midi channels ---) 2 Channels you need

Then you need to "fiddle" a bit.
The Output from the Aura, needs to be the input from the DSP
The Output from the DSP needs to be the Input from the Aura.
They just communicate for the patches.

Luckily i saved a txt file for myself. A Howto. --) He is the detailed tutorial:


Install LoopMIDI
https://www.tobias-erichsen.de/software/loopmidi.html

Create 2 Ports!
Make them "invisible" or "unusable" in Cubase Midi Connections

Load 1 instances of Ostirus (better try with one first)
Switch to Multi Mode!!
Connect the Editor to the Ostirus Instances via the new created virtual Midi Ports.
You need Out from DSP to IN to Editor. Out from Editor to IN to DSP

Load the Patches from the Ostirus Preset Browser and tweak them there. I loaded up some Patches via VirusHC and the patches sound weak.
So i think the Informations of the patches are not well translated via the Virus Editor.

MultiOutput:
In the Ostirus Plugin Windows you can activate All Outputs (Its on the top of the Plugin window from Cubase, not in the Ostirus settings)
Then you can separate the Patches in Ostirus to the Multiple different Cubase Audio Tracks (OUT1 LR, OUT2 LR, OUT3 LR, USB1 LR, USB2 LR, USB3 LR)
Insert multiple Empty Midi Tracks in Cubase and route them to the different Midi Input Channels from OSTirus. Voila
Multitrack Ostirus Setup finished.

IMPORTANT NOW:
Ostirus doesnt remember anything after closing and reloading the project.
You need to Sync DATA from HW from the Virus Editor now. So the Editor gets every Settings you made from the Virus.
Now you can save the state to the UI Data in the Editor in a file.
Now you can save your Cubase Project.

Loading a Project:
Ostirus Instances need to be set to MULTI again. Ostirus Midi in and out needs to be set in Ostirus (Common) to match with the Editor.
When the connection is established you can PUSH DATA TO HW from the Virus Editor. All Patches, settings and Audio Routing will be pushed to the EMU and
the project is loaded. Multi Patches, Multi Output etc.

I tested this with 2 Ostirus Instances, and with a bit of work it runs well.

But i would suggest to use 1 instance and when you are happy with your patches, use render in place.

But for now, its like using the Hardware TI2.
SO GOOOOOOOD!!!

Thanks everybody :)

quote by marcellixHi @Swatch
I feel the instructions in your 'tutorial' are a little misleading, particularly for those new to the software. I'm not saying they are not appreciated, but a little scary.
It also appears to be geared more towards Cubase users than other applications.
Also, you mention VirusHC, which is a bit confusing.
Again It's a bit confusing when you talk about the HW, 'cause here we're talking about Aura plugins and Usual Suspects emulators.
Finally, when you say "But for now, it's like using TI2 Hardware", I'm not sure I understand what you mean, since Ostirus already provides the same functionality as the hardware anyway.
I'd make the tutorial much simpler and less intimidating.

To get Aura working with TheUsualSuspect emulator, you need:
1- Osirus (this applies to others too)
2- LoopMidi
3- configure midi-in and midi-out preferences in the Osirus and Aura settings to LoopMidi Port 1 (I included an example image for Xenia in my previous comment).
That's it!

Hey hey. Thanks for your feedback. And yes, you're right. The long tutorial is very detailed. And long.
I wrote it for myself because I sat for hours to understand it and get it to run when the first version of the DSP was released. I think the editor had a rebrand and a other name this time. But not 100% sure.
Also to this time the DSP didn't had a store function. So the presets were not saved.
You always need to transfer the patches to the DSP. Like the real hardware. When you turned the virus off, you need to reload the patches. 🙂

Thanks for your easier tutorial. With the actual DSP there's really no need for a editor. 🙂🍻