Waldorf Micro Q Emulator (Vavra)

[RPH]

Works very well, Windows 11 & Reaper (vst3), CPU usage barely registers. Many thanks to the team.

[inception8a]

Create Vavra folders within your plugin folders, then place the Vavra plugin files, the MicroQ system 2.23 MIDI file, and any MicroQ preset banks inside that folder.

Thank you, but this is exactly what I did. Very familiar with using their Osirus (Virus) plugin and the process. The difference here being either the plugin doesn't load at all (isn't scanned properly), crashes when trying to open or crashes the host entirely. I tried in Ableton 11.2.11 (VST2) this AM and it crashes the entire host.

I downloaded all of the files a 2nd time thinking there might have been some sort of corruption and was finally able to get the CLAP version working in BitWig. Still no luck with VST2 or VST3 in BitWig or other hosts. I'm willing to admit it's probably something unique to my system... maybe I'm missing some other runtime that's not included (just a guess).

Again, I understand it's an early beta and not complaining at all. I'm more than happy to have the CLAP version working now. I've donated to the project previously and will do so again as it's amazing to have these devices and the work team has done.

I have lastest Ableton 11 loading the Vavra VST2 and it's been working fine although I did start out with a beta where it was hanging but I think the files changed or may have been quickly updated when I looked at the time stamp of the beta downloads available. I had downloaded again after that first try based on that and it loaded just fine on next try. And seems to be behaving good ever since.

[Halonmusic]

thank you!

[BBFG#]

Enjoying this.

I do need a better approach to navigating Discord as it took me some time to find a link to the "index" page.
And the amount of folders that get extracted for placement seems more than necessary. But the effort has been worth it. Thank you.

https://futurenoize.com/dsp56300/builds/microQ/beta/
https://waldorfmusic.com/legacy-micro-q-series/

[aMUSEd]

how do I make it so my Mac doesn't keep trying to block and delete it when I scan it in a host?

[El°HYM]

how do I make it so my Mac doesn't keep trying to block and delete it when I scan it in a host?

@Mac

As a reminder, you will need to run the following xattr commands from Terminal to reference the actual path and filename of the plugin files you want to "fix" and allow as unsigned plugins to validate and work. Use the examples below (filling in the blanks of the plugin names and correct paths if yours are different):

sudo xattr -cr /Library/Audio/Plug-Ins/VST3/Vavra.vst3

sudo xattr -cr /Library/Audio/Plug-Ins/VST/Vavra.vst

sudo xattr -cr /Library/Audio/Plug-Ins/Components/Vavra.component

sudo xattr -cr /Library/Audio/Plug-Ins/CLAP/Vavra.clap

[osiris]

FL Studio gets errors loading vst2 &b vst3. It's also unsigned and wouldn't work even when I manually put in Synth in what kind of plugin it is. Got this message:
Access violation at address 00007FFD26C4C4D0 in module 'FL64.exe'. Execution of address 00007FFD26C4C4D0
Callstack:
0000000000000000:00007FFD26C4C4D0:

[tactile_coast]

Working perfectly in Bitwig VST3 and CLAP.

For reference I did it by finding three files from the sources listed above (But make sure they have been unzipped first, several are zipped multiple times): Vavra.clap, mq_2_23.mid and microq_factoryset_2000.mid

Then placed them all into a new folder called Micro Q within my CLAP folder located C:\Program Files\Common Files\CLAP

VST3 installation was near identical.

[aMUSEd]

how do I make it so my Mac doesn't keep trying to block and delete it when I scan it in a host?

@Mac

As a reminder, you will need to run the following xattr commands from Terminal to reference the actual path and filename of the plugin files you want to "fix" and allow as unsigned plugins to validate and work. Use the examples below (filling in the blanks of the plugin names and correct paths if yours are different):

sudo xattr -cr /Library/Audio/Plug-Ins/VST3/Vavra.vst3

sudo xattr -cr /Library/Audio/Plug-Ins/VST/Vavra.vst

sudo xattr -cr /Library/Audio/Plug-Ins/Components/Vavra.component

sudo xattr -cr /Library/Audio/Plug-Ins/CLAP/Vavra.clap

Thanks that worked

[osiris]

I did finally get it to work. You do have to put the 2.23 mid file with(it is in the System folder on the Waldorf site not Sounds) , so I just made separate folders and copied it into each. What a lovely retro sound. The GUI is HUGEEEE. I don't know how to resize or if that's even in the Beta. Fl only did 25% CPU playing a big chord. Many thanks and also thanks to Waldorf for keeping these files accessible.

[JamminFool]

right-click on background to get GUI sizing options.

[osiris]

Thanks. i finally realized it could be like Osirus and right clicked on the GUI. 50% is the perfect size but the lettering starts to look like a chart in an Optometrists office. I'll give FL users a tip. I made separate folders for the VST2 & VST3. I put the .dll & .mid system update in along with one soundbank. The other banks I put in their own folder inside the Vavra folders. This synth has to scan presets , which can take a minute. I found if you put all the banks in the same folder it tries to scan ALL the presets. Don't know how long that would take, but I got tired of waiting. Moving the other banks to their own folder fixed this. The Preset Browser is exactly like Osirus and after an initial Preset scan it loads other Presets very quickly. The only thing I don't like is the name. It's the last name of an American baseball player, so who knows? I didn't build it, I don't get to name it.

[Uncle E]

Vavra is a James Bond reference, like Blofeld.

[El°HYM]

From Russia with Love

[osiris]

He's either a movie buff or trying to tell us something. Here's the Wiki description of the character: Vavra, chief of a Gypsy tribe used for dirty work.