Waldorf Q, Q+ and microQ AudioUnit & VST plug-in pre-order available

5 Comments

Waldorf Q, Q+ and microQ are most definitely one of the best hardware synthesizers over time. We are happy to have microQ in our studio. Since we have a habit to make Editor & Librarian plug-ins of the gear we have in our studio at the moment, Waldorf Q-series editor was inevitable so to speak. :)

This new plug-in is called Waldorf qXr AudioUnit & VST Editor / Librarian for Waldorf Q, Q+ and microQ. It can manage all 16 parts, multi settings and global settings from within one plug-in view. Manage patches; import MIDI files, SysEx files and even Waldorf Blofeld patch banks into the plug-in and load them as you go! Waldorf Blofeld banks will not sound the same as they do on Blofeld, since Q-series has completely different engine and oscillators (on wavetable side). But they are almost the same, so why not have this feature and modify your blofeld presets to suit the Q-sound.

Users are able to store banks from Q-series to HDD and then send them to the synth from the librarian, on the part you want. More details on the product page and the link is down below. While we are announcing these news, the plug-in is already working in Logic Pro, Cubase Pro, Studio One, and all other major DAWs, but the downloads are not yet available. We want to finish our product first to deliver A-class plug-in, again!

Below you will find few screenshots of our plug-in. Pre-order today and save! Estimated release date: End of March / early April 2017.

Here is a little teaser of what will be announced soon: Waldorf bloXr …. Yes, bloXr is the black and qXr is the yellow :-)

  • http://www.soundcloud.com/deejayjorgen Jørgen

    Looking forward to use this plugin.

    • https://www.mysteryislands-music.com Jani Kervinen

      Go and get it!

  • HAppY_KrAToS

    Need to send some cash to my paypal account. Will we still be able to buy this Q editor at the pre-order /discounted price, until, let’s say, next 3 or 4 april ?

    A question regarding the virus editor. If my friend owns, say, the virus C AND the virus TI, is there a risk there might be a conflict , if he opens a project and adds an instance of your virus editor to control his C, and later, he creates/opens another project, and this time, he will be controlling his TI. Could there be a model selection detection/ conflict of some kind ?

    If someone can answer to this: are these plugins/editors ‘just’ serial-number based, or do they require that awful challenge-response/mac address copy protection used by the competition, at 3dsolar .com, that simply made me not buying it at all (with 2-3 hardware updates per year, + frequent OS/HD cloning/restore/etc, windows upgrades, etc etc, dealing with such copy protection is a nightmare, for legit users) ? We get our serial numbers/etc automatically after the checkout is successful, and we can go and register the plugin ?

    Thanks.

    I already have an editor for my Q rack (yellow), that SEES and HANDLES the memory card slot.
    Can this editor use the memory card slot ?
    The editor works flawlessly, but can’t work as a plugin, no automation, no nothing.
    It will be fun to automate my Q rack inside cubase.

    Ps. The q editor i own can ‘mutate’ sounds, parents/kids, and generate other sounds, based on the presets. Can your editor randomize sounds, or mass-generate other sounds ?

    • https://www.mysteryislands-music.com Jani Kervinen

      Hi Happy Kratos,

      The plug-in is still in “pre-order” sale, while we just unleashed beta version of the plug-in. Give it a shot and let us know what you think.
      Your questions answered: 1. midi data is being sent out from our plug-ins to the same midi ports which were active & activated inside the plugin.
      2. You can download a license.key from your account page that you can use freely within your own use. Licenses are personal and not for resale. Plug-in can be registered by opening patch browser page, bank edit menu and choose register plugin..

      Yes we can handle Q-cards too, but it’s very limited yet at this point due to the fact that I don’t have Q here in the studio to debug. I’m looking forward to get Q in house, so I can properly see how it acts under certain circumstances.

      We are also in the process of adding randomizer in the plug-in, which will purely only just randomize preset under the limits you set for the process.

  • frank

    hope to see the bloXr soon.
    If you need beta tests for this,… call me

    ;-)