- This topic has 1 reply, 2 voices, and was last updated 2 weeks, 1 day ago by .
I’m using the Demo version in hopes of buying the full license. I’m having some issues that are not a part of the demo limitations.
I will give my rig setup at the bottom of this post.
Issue 1: CPU spike when focusing on multimode part. My CPU spikes to 200%+ for a moment, which breaks the audio, every single time that I click on the number of a part in order to start managing the sounds of that part.
Issue 2: Envelope/Filter/LFO settings get ‘stuck’ when trialing multiple patches rapidly. I have encountered an issue whereby my simple sequence starts getting into a very repetitive setting (sounds like perhaps an envelope is stuck with it’s setting, or an LFO, or a filter setting) whereby, when I then switch to other patches, they all retain the same setting (stutter attack with a very short sustain and no release sound, but the envelopes look right when i move them around).
Issue 3: GUI actions don’t get sent to my unit. I have the editor working fine most of the time, but occasionally, i will change something and it will not be enacted. This happens the most when changing envelope types (ADSR to ADSD2S2r, for instance), and I then have to reboot the plug-in. Since I’m on the demo version, I lose all of my settings.
* What system you are using and OS version.
Macbook Pro (2018) 2.9Ghz corei9 Mac OS10.14.6
* What DAW you are using.
Ableton Live 10.1.2 – using the plug-in as an AU.
* What audio interface you are using.
Antelope Audio Orion 32+ on 96Khz (I also sometimes run Waves Sound Grid Server, so the driver is installed, but I’ve not run it with this plug-in active, as yet)
* What MIDI interface you are using.
* What did you do to find the bug / issue?
I was replacing soft synths from imported songs (from bandmates) with microQ sounds.
* How we can re-create the issue in our end to fix it.
I’m not sure.
I really love the look and feel of the plugin, and would love to purchase a working version, but these issues would be a no-go for me (predominantly the CPU spike which cuts audio, as I play live shows and cannot sacrifice stability for something like this.
- You must be logged in to reply to this topic.