Korg multi/poly native - reimagined Mono/Poly Synthesizer plugin

[sacer]

it's alsoi not working in ableton 12 like most other new Korg Plugins like Modwave.
Ableton has a VST3 bug on Windows, where some vst3 synths display every single parameter change on controllers like Push and takes some seconds to load next preset. Especially if you map the 4 macros and Kaos Pad a preset change takes some seconds.
Other like Parawave and minimal Audio have fixed this behaviour in their VST3 Plugins and now run fluent in ableton with smooth preset change.
I wrote Korg since the release of Modwave and they are aware of it, but they won't fix it, so it's up to Ableton, to fix this bug after more than 3 YEARS

[tumface]

Heads up -- the Windows installer is misconfigured. After it finishes copying files, the installer will immediately attempt to kill all of your running programs and restart your computer. It will show a prompt asking if you want to restart AFTER it has already killed everything and tried to initiate a Windows restart. So, the installer starts, runs for a few seconds, then all of your running programs quit, and the installer shows you a window that says "Do you want to restart now, or later?" for a split second before your computer restarts. It's not even necessary. It works fine without restarting, like everything does since 2006. They must have misconfigured their installer settings when packaging it. Ouch!

[tumface]

Getting an unexpected clicking noise on note-ons when the VCA type is set to anything but Linear. Anyone else?

[EvilDragon]

Not over here.

[tumface]

Hmm. Definitely happening here.

Some other stuff: running through my standard tests for a synth and it sounds pretty good! Some things I've noticed so far (I've never used the multi/poly hardware):

* No oscillator reset.

* UI behaves a bit oddly sometimes when dialogs open up.

edit: I take it back. It sounds excellent, not just pretty good.

[Hanz Meyzer]

I wonder about the synthesis quality... At which sample rate is the hardware running? Is the oversampling option adaptive to the set sample rate? So will 96kHz sound the same as 48kHz?

[kritikon]

I'll try it next couple of days or so if I get the chance. Anyone having those denormal-type issues with ridiculous CPU usage like what happened with Wavestate and Opsix, or have they released a working version this time?

[tumface]

I wonder about the synthesis quality... At which sample rate is the hardware running? Is the oversampling option adaptive to the set sample rate? So will 96kHz sound the same as 48kHz?

It has a few samples of latency at default settings, so I'm assuming it runs at its own sample rate internally regardless of the host, and resamples to whatever the host is running at (hence the PDC.)

It sounds excellent, regardless of what specific rates they're running the various parts of the synth at. There's also an option to increase the oversampling.

[tumface]

I'll try it next couple of days or so if I get the chance. Anyone having those denormal-type issues with ridiculous CPU usage like what happened with Wavestate and Opsix, or have they released a working version this time?

No CPU spikes so far.

[EvilDragon]

It runs at 96k at Standard setting and 192k at Extreme setting. And this is adjusted separately per layer A/B/C/D.

* No oscillator reset.

I think that's very intentional.

[EvilDragon]

I'll try it next couple of days or so if I get the chance. Anyone having those denormal-type issues with ridiculous CPU usage like what happened with Wavestate and Opsix, or have they released a working version this time?

The issue with Wavestate/Opsix wasn't related to denormals, it was down to threading strategy.

[tumface]

It runs at 96k at Standard setting and 192k at Extreme setting. And this is adjusted separately per layer A/B/C/D.

* No oscillator reset.

I think that's very intentional.

Yeah. I would still like to have it as an option, but I know that sort of thing isn't the focus of this type of synth.

And, as expected (yay) the state of the voices is correctly maintained between notes, instead of using randomization for deallocated/reallocated voices.

[twolegstoneworks]

Demo runs fine on my Mac M3, but in Ableton Live 12 it lags a lot when browsing presets. It takes 3-4 seconds for each preset to load. If I open the plugin in Bitwig 5, the loading of presets is instant. Strange.

[HydrogenHuman]

Demo runs fine on my Mac M3, but in Ableton Live 12 it lags a lot when browsing presets. It takes 3-4 seconds for each preset to load. If I open the plugin in Bitwig 5, the loading of presets is instant. Strange.

Same slow preset loading for me too in Ableton 12.

[tumface]

The slow preset change when there are a lot of parameters thing is a flaw in Ableton, not the plugin. Plugins have to add workarounds to deal with it in Ableton. I don't blame a plugin maker if they don't do it.