KVR Audio

c_voltage · Post by **c_voltage** » Sat Jun 27, 2026 3:39 pm

Trialed thing today finally (not tried v1 before), cpu eating is pretty big unfortunately (13% in idle no sound state), this is even with no appeal to new "voice cards".
For example, preset "Touch of String" eat 57%, even with no sound. Then if add release (Vol Env) to max, and clone setting to rest parts (Multi\Clone to all), will does up to 100% \ cpu clipping.
In rest not a bad synth though. But desire to grab is greatly minimised with such optimization yet.

temporubato · Post by **temporubato** » Sat Jun 27, 2026 8:16 pm

Wait for update Monday or PM me for beta.

geronimo · Post by **geronimo** » Sat Jun 27, 2026 9:28 pm

c_voltage wrote: Sat Jun 27, 2026 3:39 pm For example, preset "Touch of String" eat 57%, even with no sound.

Not a preset, it's a Multi _
But I confirm the high CPU mobilisation .

c_voltage · Post by **c_voltage** » Sat Jun 27, 2026 11:10 pm

geronimo wrote: Sat Jun 27, 2026 9:28 pm
c_voltage wrote: Sat Jun 27, 2026 3:39 pm For example, preset "Touch of String" eat 57%, even with no sound.
Not a preset, it's a Multi _
But I confirm the high CPU mobilisation .

Just, featurewise (or by sound' exhaust) i'm not exactly hear what can require such calculations. Maybe such amount of envelopes idk. Worh mention that Largo eating is near to zero in most cases, and it;s still beast.

I tried an experiment with Largo: set global voices amount to 64 (256 is max though, but ok won't be impudent yet lol), set Multi mode to Layer, and enabled all 4 parts (1 part is default). Then enabled all 3 osc in each of 4 parts (1 osc per part is default). Then enabled Unisono to max 6 voices inside each of 4 parts. And set envelope release to max in each part.
So finally i walked forth and back over the bunch octaves roll with a mouse lol. And you know what, even with that i could'nt catch eating more than 12-13%. (equaling the idle state for Microwave)
That astonish.
I even twisted each of 4 part in solo to make sure they worked and sounded separate. And yes, they do sound separate lol ie independently.
(And ok, 46% with 256 voices)

Of course, these comparisons may be inrelevant without a good understanding of the voices distribution in both synths. Honestly, I didn't dig into detail about differences \ benefits in Microwave, perhaps I'm missing some importnt nuances idk.

Upd BTW, do Microwave has unisono per some of his part (osc\ osc section\ layer\ per "instrument" etc), or globally ? Or it suppose to replicate thru multiplying the same parts and then detune knob in eah of such part manually ?

Flogs · Post by **Flogs** » Sat Jun 27, 2026 11:59 pm

Same high CPU usage with version 2. Uninstalled the v2 demo within 30 minutes and went back to v1, v1 uses next to no CPU. I hope the issues are ironed out in v2 as I would like to upgrade to it but not at the cost of extra CPU with identical patches.
I also have quite high CPU cost with Attack 3 as well which surprised me as Largo 2 and Blofeld (and original Microwave v1) are very CPU friendly.

db3 · Post by **db3** » Sun Jun 28, 2026 12:32 am

@Rolf has the demo period been reset with the V2 release?

Tj Shredder · Post by **Tj Shredder** » Sun Jun 28, 2026 5:00 am

It could benefit from MPE, or maybe easier to implement voice per channel mode… (or a way to load the same sound to all layers at once)

temporubato · Post by **temporubato** » Sun Jun 28, 2026 6:28 am

db3 wrote: Sun Jun 28, 2026 12:32 am @Rolf has the demo period been reset with the V2 release?

Yes, V2 has a new demo period such you can check out V2 if you own V1.

temporubato · Post by **temporubato** » Sun Jun 28, 2026 6:28 am

Flogs wrote: Sat Jun 27, 2026 11:59 pm Same high CPU usage with version 2. Uninstalled the v2 demo within 30 minutes and went back to v1, v1 uses next to no CPU. I hope the issues are ironed out in v2 as I would like to upgrade to it but not at the cost of extra CPU with identical patches.
I also have quite high CPU cost with Attack 3 as well which surprised me as Largo 2 and Blofeld (and original Microwave v1) are very CPU friendly.

There will be an update on Monday when I am back in office.

Caine123 · Post by **Caine123** » Sun Jun 28, 2026 9:33 am

quite interested in this plugin but the BAD reputation for Waldorf's update history (Largo`anyone?) makes me think twice.... of course this wont be commented here I guess

.

EvilDragon · Post by **EvilDragon** » Sun Jun 28, 2026 9:35 am

Well this plugin had quite a nice slew of updates since release...

Caine123 · Post by **Caine123** » Sun Jun 28, 2026 9:43 am

EvilDragon wrote: Sun Jun 28, 2026 9:35 am Well this plugin had quite a nice slew of updates since release...

good to know, it shouldnt be the case that one gets well updated and other(s) not. u-he for example care for their plugins and dont stay dead silent. i think it is important to post this here too knowing someone from Waldorf is reading this.

EvilDragon · Post by **EvilDragon** » Sun Jun 28, 2026 9:47 am

u-he also has long periods of time when some plugins just aren't the focus. It's normal once your portfolio grows to a certain size.

stimresp · Post by **stimresp** » Sun Jun 28, 2026 1:10 pm

I am really enjoying the new features of V2 but think I have found a bug with voice allocation:

I wanted to create a mono lead patch. I understand that you must go into multi mode to do this, set up a single instrument, click on the settings button, and change the Voices selection.

However, none of the Voices options seem to work correctly - the patch is always polyphonic no matter which trigger/retrigger option I choose. Even if set up glide options the patch is never monophonic. In global settings the voice cards is set to 1.

Can someone verify this behaviour or tell me where I am going wrong?

IvyBirds · Post by **IvyBirds** » Sun Jun 28, 2026 2:13 pm

Caine123 wrote: Sun Jun 28, 2026 9:33 am quite interested in this plugin but the BAD reputation for Waldorf's update history (Largo`anyone?) makes me think twice.... of course this wont be commented here I guess .

Waldorf over the past few years seems to have really turned the corner regarding supporting software. Especially with the Blofeld and the Microwave both of which sound fantastic and have received many updates and bug fixes

They used to have a clear Hardware Bias where software felt like it was always not the priority compared with hardware, but that doesn't seem. To be the case now

Waldorf microwave 1 Version 2