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

[suthnear]

- 4 oscillators naturally suggest vector mixing

Can't you use the Kaoss Pad for that? Or just Assign the mixer to CCs and then a controller?

You can get close but all those involve linear curves so it's hard to maintain equal volume across the quadrants. And the pad is shared by all 4 layers so it eliminates it for use by the others

[vscorpio]

After update 1.0.3 I get windows 11 system crash (blue death screen) whenever I try to set the audio driver to ASIO (all other plugins including all Korg Collection's ones still works perfectly)...any suggestion what is causing that issue?

[IvyBirds]

- 4 oscillators naturally suggest vector mixing

Can't you use the Kaoss Pad for that? Or just Assign the mixer to CCs and then a controller?

You can get close but all those involve linear curves so it's hard to maintain equal volume across the quadrants. And the pad is shared by all 4 layers so it eliminates it for use by the others

FWIW you can convert pretty much any synth with layers and a mixer control visible to a DAW (which is pretty much all of them) into a vector synth using Voltage Modular by Cherry Audio. You just host Voltage Modular into an instrument track and then host your VST inside of VM. Your Synth is now a virtual polyphonic 'Eurorack Module". Everything visible to a DAW is now fully controllable via virtual CV

So you use the utility modules to convert an incoming MIDI CC to a virtual CV, plug two virtual CV cables into that utility run one directly into Mixer Channel 1, run the other into an inverter utility and then into mixer channel 2. Assign whatever you are using as a vector controller for up and down to whatever CC you want and assign that into the utility. Now when ever you move that control up and down Channel 1 on the mixer will get louder and channel 2 will get quieter, you then repeat the process for the left/right controls

I do this all the time and find the upper range to be to high to I use another attenuator to reduce the high values

Making any synth a vector synth is really cool, and of course you can do this with anything visible to a DAW not just levels on a mixer, and of course many sequencers and DAWs can sequence CCs. Inside of VM you can also use LFOs for this purpose and have the LFO generate the CV. The entire world of crazy modular CV is available to do this

You can also do this with VCV rack, but I find VM to use less CPU than VCV rack when using it just to host plugins

[danatkorg]

There doesn't seem to be a ping pong delay option. What am I missing?

L/C/R Delay, Multiband Mod Delay, Tape Echo, and Stereo/Cross Delay will all do ping-pong effects. Stereo/Cross Delay and Tape Echo offer the most instant gratification; I just made a few presets with very simple, evenly-spaced left-right delays, which I've enclosed below.

[danatkorg]

After update 1.0.3 I get windows 11 system crash (blue death screen) whenever I try to set the audio driver to ASIO (all other plugins including all Korg Collection's ones still works perfectly)...any suggestion what is causing that issue?

I'm sorry that you're having difficulties. We have tested with ASIO and Windows 11, but there may be differences depending on the specific ASIO hardware.

It might be helpful to delete the preferences, in:
C:\Users\<username>\AppData\Roaming\KORG\multipoly native

I have a few questions, which might help us in troubleshooting:

I assume that this is in the standalone version; does the plug-in work OK in your DAW host?

What version of multi/poly were you using previously?

[vitocorleone123]

I’d buy this instead of Serum2 if it had MPE. Instead, it’s going to be the other way around.

[sheeepsss]

Is it normal to have a 2 seconds lag when opening the GUI or when changing presets?

Same happened to me with Triton Vst but only when opening Gui and not when changing presets.

I use Live 12 and I don't have any midi controller enabled.

Great great sound but it's a no for me if it's so laggy.

CPU skyrocketing on certain presets also.

I understand that this is a very demanding synth but with a 5-note long chord Ableton CPU meter is over 52% with preset "Boundary Pad", for example, with polyphony set to 5 notes on both layers.

If I increase polyphony to 8, CPU meter goes to 75% and if I leave it at the default "dynamic" setting, retriggering a chord with release of previous notes still going (10 voices I presume) it reads more than 110%.

This is with Win 11, i5 9600k CPU, internal Intel graphics, RME FF800 at 48k/256 buffer. Not the newest of CPUs I know but still very high readings.

EDIT: with Reaper the lag is still there but reduce to approximately slightly less than 1 second both when opening GUI and changing preset so Ableton seems to be involved in this but even Reaper is not snappy as all other VSTis that I use.

Anyone with the same problem?
Anyone with a fix for this?

[BBFG#]

Disable Windows Telemetry Compatibility.

[sheeepsss]

Disable Windows Telemetry Compatibility.

Thanks but it didn't change anything

[hcv242]

Is it normal to have a 2 seconds lag when opening the GUI or when changing presets?

Same happened to me with Triton Vst but only when opening Gui and not when changing presets.

I use Live 12 and I don't have any midi controller enabled.

Great great sound but it's a no for me if it's so laggy.

CPU skyrocketing on certain presets also.

I understand that this is a very demanding synth but with a 5-note long chord Ableton CPU meter is over 52% with preset "Boundary Pad", for example, with polyphony set to 5 notes on both layers.

If I increase polyphony to 8, CPU meter goes to 75% and if I leave it at the default "dynamic" setting, retriggering a chord with release of previous notes still going (10 voices I presume) it reads more than 110%.

This is with Win 11, i5 9600k CPU, internal Intel graphics, RME FF800 at 48k/256 buffer. Not the newest of CPUs I know but still very high readings.

EDIT: with Reaper the lag is still there but reduce to approximately slightly less than 1 second both when opening GUI and changing preset so Ableton seems to be involved in this but even Reaper is not snappy as all other VSTis that I use.

Anyone with the same problem?
Anyone with a fix for this?

same here.

next ableton live release will have some gpu acceleration for graphics or something alike, maybe it will help.

[db3]

Try Korg's Ableton workaround for slow preset changing. From my experience the lag was brief but frustrating when I used a Novation LaunchKey, but long and unusable when I used an Arturia KeyLab.

https://support.korguser.net/hc/en-us/a ... leton-Live

[frag]

Is it normal to have a 2 seconds lag when opening the GUI or when changing presets?

Same happened to me with Triton Vst but only when opening Gui and not when changing presets.

I use Live 12 and I don't have any midi controller enabled.

Great great sound but it's a no for me if it's so laggy.

CPU skyrocketing on certain presets also.

I understand that this is a very demanding synth but with a 5-note long chord Ableton CPU meter is over 52% with preset "Boundary Pad", for example, with polyphony set to 5 notes on both layers.

If I increase polyphony to 8, CPU meter goes to 75% and if I leave it at the default "dynamic" setting, retriggering a chord with release of previous notes still going (10 voices I presume) it reads more than 110%.

This is with Win 11, i5 9600k CPU, internal Intel graphics, RME FF800 at 48k/256 buffer. Not the newest of CPUs I know but still very high readings.

EDIT: with Reaper the lag is still there but reduce to approximately slightly less than 1 second both when opening GUI and changing preset so Ableton seems to be involved in this but even Reaper is not snappy as all other VSTis that I use.

Anyone with the same problem?
Anyone with a fix for this?

Your CPU is very good.
Audio software companies refuse to implement multithreading because of numerous "CPU energy saving" options which users must disable in BIOS/Win.
You can use ProcessLasso to temporarily disable Windows Core parking while DAW is running, this makes multithreading smooth.

I've got 24 threads and I'm forced to run Multipoly on a single thread, like it's 1999.
This is outrageous and quite primitive.
Basically, we cannot use equipment we paid for because of software hacks.
VST3 and single thread in 2025?
32bit VST2 with multithreading blows away any VST3 single thread synth in terms of performance and sound quality.

[Gam456]

I've got 24 threads and I'm forced to run Multipoly on a single thread, like it's 1999.
This is outrageous and quite primitive.
Basically, we cannot use equipment we paid for because of software hacks.
VST3 and single thread in 2025?
32bit VST2 with multithreading blows away any VST3 single thread synth in terms of performance and sound quality.

Modern DAW are multithreaded like Repear, Cubase
It's simple Diva, Pigments run way more smoothly with their own mulithread off

[frag]

I've got 24 threads and I'm forced to run Multipoly on a single thread, like it's 1999.
This is outrageous and quite primitive.
Basically, we cannot use equipment we paid for because of software hacks.
VST3 and single thread in 2025?
32bit VST2 with multithreading blows away any VST3 single thread synth in terms of performance and sound quality.

Modern DAW are multithreaded like Repear, Cubase
It's simple Diva, Pigments run way more smoothly with their own mulithread off

That's complete BS.

1) Turn off Core parking in Win and energy saving in BIOS.

2) Turn on mutlicore in Diva, and multithreading in DAW.

It runs perfectly - you get full polyphony in divine quality even on 15 year old CPUs.

[zvenx]

What does vst3 have to do with single vs multithread?

So you know Diva doesn't work great in multthread in all situations, which is why u-he (and quite a few other developers who do allow multi-thread) have it as an option.. On my apple mac silicon for instance, Diva works better with it off whether I am using one instance or several.. on my intel pc and my previous intel macbook pro, it ran fine with it on for a few instances, but if you have a project with say 6 instances, it worked better with it off.
rsp