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

[db3]

Does that standalone also take that long or only when you use it as a plugin, in whatever host you are using?
So you know on my mac and pc both standalone and vst3 (in Cubendo) are instantaneous for me.
rsp

Standalone's fine. It seems to be the 'Ableton' issue. Although, not sure why other plugs don't exhibit this. Makes it unusable.

[EvilDragon]

Sure certain other plugin that explose a lot of parameters to host also exhibit this issue. Certain GForce plugins are also affected.

Again, Ableton are aware of the issue. For quite some time now. They just aren't prioritizing fixing it because "not a lot of people are affected by it". So you need to yell louder.

[danatkorg]

multi/poly native version 1.0.3 is now available; if you have "check for updates" enabled, you'll see a prompt the next time you run the plug-in.

Changes include:
Version 1.0.2 introduced a degrade in which turning knobs with the mouse while playing notes could cause CPU overs. This has now been fixed.
"Enter chord from MIDI" now turns off automatically when Chord or the Layer are turned off, when the Performance or Program are changed, when the UI is closed or switched away from the Setup & Chord page, or after a 1 minute timeout.
Previously, the envelope graphics always displayed curvature based on the Custom settings, ignoring Presets. This has now been fixed.
The About box colors now provide improved contrast.
Windows only: previously, when a Waveshaper Oscillator was set to the "Berkeley" shape and Gain was set to maximum, the synth would go silent. This has now been fixed.

Thanks again to everyone who provided information on the mouse knob movement & waveshaper gain issues!

[danatkorg]

Ok ok, so question to all:

How can I use the motion sequencer and having a release time on each of the pitches/notes?

The motion sequencer is a per-voice modulator, like an LFO or an envelope. It modulates pitch, and can trigger envelopes, but it does not trigger notes. So, no release times are possible for individual steps.

[Funkybot's Evil Twin]

multi/poly native version 1.0.3 is now available; if you have "check for updates" enabled, you'll see a prompt the next time you run the plug-in.

Changes include:
Version 1.0.2 introduced a degrade in which turning knobs with the mouse while playing notes could cause CPU overs. This has now been fixed.
"Enter chord from MIDI" now turns off automatically when Chord or the Layer are turned off, when the Performance or Program are changed, when the UI is closed or switched away from the Setup & Chord page, or after a 1 minute timeout.
Previously, the envelope graphics always displayed curvature based on the Custom settings, ignoring Presets. This has now been fixed.
The About box colors now provide improved contrast.
Windows only: previously, when a Waveshaper Oscillator was set to the "Berkeley" shape and Gain was set to maximum, the synth would go silent. This has now been fixed.

Thanks again to everyone who provided information on the mouse knob movement & waveshaper gain issues!

Hi Dan,

Any chance of a full-blown MIDI Learn? Even just mapping a few dozen of the hundred parameters would be great.

[Hanz Meyzer]

Any chance of a full-blown MIDI Learn? Even just mapping a few dozen of the hundred parameters would be great.

Also a full remote control with the hardware would be very nice. Currently the hardware is not sending any midi ccs while turning cutoff etc. I think using the opsix hardware, you actually can even control the software in detail, at least that's what I remember.

Any chance to add multi output, too?

sum -> output 1/2 (just like now)
layer 1 -> output 3/4 (master eq disabled, "use individual outputs" activated)
layer 2 -> output 5/6 (master eq disabled, "use individual outputs" activated)
layer 3 -> output 7/8 (master eq disabled, "use individual outputs" activated)
layer 4 -> output 9/10 (master eq disabled, "use individual outputs" activated)
global reverb wet -> output 11/12 (master eq disabled, "use individual outputs" activated)

And last request what about a comb filter?

[Gam456]

multi/poly native version 1.0.3 is now available; if you have "check for updates" enabled, you'll see a prompt the next time you run the plug-in.

Changes include:
Version 1.0.2 introduced a degrade in which turning knobs with the mouse while playing notes could cause CPU overs. This has now been fixed.
"Enter chord from MIDI" now turns off automatically when Chord or the Layer are turned off, when the Performance or Program are changed, when the UI is closed or switched away from the Setup & Chord page, or after a 1 minute timeout.
Previously, the envelope graphics always displayed curvature based on the Custom settings, ignoring Presets. This has now been fixed.
The About box colors now provide improved contrast.
Windows only: previously, when a Waveshaper Oscillator was set to the "Berkeley" shape and Gain was set to maximum, the synth would go silent. This has now been fixed.

Thanks again to everyone who provided information on the mouse knob movement & waveshaper gain issues!

Thank You so much

[Hanz Meyzer]

What is strange about the plugins GUI that it draws faster in OpenGL mode on a fast ARM Mac / macos 14 than with CoreGraphics mode...

I assume that you have to update your GUI (is it JUCE) to enable GPU acceleration properly, e.g. update to JUCE 7. Obviously currently there is no GPU acceleration in CoreGraphics mode, you can see it best, if the GUI is upscaled to 150% or so.

You might also have a look into this dev info about enabling GPU acceleration, maybe it still is a thing:
https://forum.juce.com/t/slow-frame-rat ... s/35813/23

[D-Fusion]

Hi Dan
I still got some issues with Multipoly V1.0.3 on my Windows 11 PC in Bitwig and Reason 13.
If i select init Performance and load the preset 3Syncpercussion or the 4 Osc Lead in Layer A I get no sound.
The 90s trance Bass B is also giving me a click sound similar to a short kickdrum instead of a Bass sound when loaded into Layer A in init performance mode.

Hope you can look into this for me

[Gam456]

Hi Dan
I still got some issues with Multipoly V1.0.3 on my Windows 11 PC in Bitwig and Reason 13.
If i select init Performance and load the preset 3Syncpercussion or the 4 Osc Lead in Layer A I get no sound.

3Syncpercussion --> vcf output is set to 0
4 Osc Lead in Layer A ---> volume of each OSC is set to 0
90s trance Bass B --> nothing anormal, both vcf and vca envelope are short, you can increase the vcf env amount.

[D-Fusion]

Hi Dan
I still got some issues with Multipoly V1.0.3 on my Windows 11 PC in Bitwig and Reason 13.
If i select init Performance and load the preset 3Syncpercussion or the 4 Osc Lead in Layer A I get no sound.

3Syncpercussion --> vcf output is set to 0
4 Osc Lead in Layer A ---> volume of each OSC is set to 0
90s trance Bass B --> nothing anormal, both vcf and vca envelope are short, you can increase the vcf env amount.

That must be a bug in the preset system or they saved the wrong preset since i have a hard time believing that it was like this when the preset creator made them so it is fixable from Korgs side

I am very happy with the sound of the Multipoly and I bought it as soon as it was released to complete my Korg Collection

[theoryzero]

Does that standalone also take that long or only when you use it as a plugin, in whatever host you are using?
So you know on my mac and pc both standalone and vst3 (in Cubendo) are instantaneous for me.
rsp

Standalone's fine. It seems to be the 'Ableton' issue. Although, not sure why other plugs don't exhibit this. Makes it unusable.

I mapped all 128 device parameters as described here and saved it as my default configuration. That solved the issue completely for me, presets are loading in less than a second now when they were taking minutes before. You do not have to map all of these device parameters to your midi controller, you only need to add them to the device panel in Ableton to fix the problem.

Edit: I've also noticed that the plugins that do not exhibit this problem for me either have a very small amount of mappable device parameters or the device parameters seem to be already populated. For example, Softube synth plugins I own such as Model 82, 84, 72 already have device parameters mapped in Ableton the first time I start them up. I suspect Korg isn't doing this because plugins like Multipoly have more than 128 parameters to choose from. Naturally the user should choose which they want to use. The downside is this odd slowdown behavior that frustrates users.

[tumface]

I've also noticed that the plugins that do not exhibit this problem for me either have a very small amount of mappable device parameters or the device parameters seem to be already populated. For example, Softube synth plugins I own such as Model 82, 84, 72 already have device parameters mapped in Ableton the first time I start them up. I suspect Korg isn't doing this because plugins like Multipoly have more than 128 parameters to choose from.

I think the automatic mapping is performed by Ableton Live, and it only happens if the plugin doesn't expose too many VST parameters in total. I think the cutoff number is 25 or something like that. I could be wrong, though.

[db3]

Thanks @theoryzero that workaround worked for my KeyLab. Seems to save that config setting in the project with a demo version instance. @danatkorg anything Korg can do to permanently smooth this?

[danatkorg]

What is strange about the plugins GUI that it draws faster in OpenGL mode on a fast ARM Mac / macos 14 than with CoreGraphics mode...

I assume that you have to update your GUI (is it JUCE) to enable GPU acceleration properly, e.g. update to JUCE 7. Obviously currently there is no GPU acceleration in CoreGraphics mode, you can see it best, if the GUI is upscaled to 150% or so.

I've tested this again, and I see very different results here. I set the size to 150%, selected the Play page, and set Kaoss Physics into motion. On my Mac Studio M1 Ultra, Core Graphics mode clearly offers far superior performance, as expected. With OpenGL mode (recommended for older Intel-based Macs), CPU usage was almost twice as high, and GPU usage was almost nine times greater.

Note that you have to restart before changes to this parameter make a difference.