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

[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

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.

Dude
I can run 128 instance of Diva playing chords with chorus and reverb
Not even 64 with the multithread ON

[EvilDragon]

It very much depends on the DAW and the CPU, it's not a silver bullet.

[sheeepsss]

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

I'm not using any midi controller. Just clicking on next preset with mouse. I tried the workaround too but didn't change anything.

In Reaper is better but there's still a lag (slightly less than 1 second) when changing presets and opening GUI so it's not only an Ableton issue.

Do you guys can change presets without any kind of lag like when using other Vstis?

[EvilDragon]

It really depends on the plugin. Some are faster, some are slower.

[aMUSEd]

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

I'm not using any midi controller. Just clicking on next preset with mouse. I tried the workaround too but didn't change anything.

You do have to ensure all 128 param slots are filled up

[sheeepsss]

You do have to ensure all 128 param slots are filled up

That's what I did (screenshot is for the last part on the right but all 128 parameters are filled). I clicked configure, changed preset so that all 128 parameters are filled and I saved as default configuration as per workaround instructions

multipoly128.jpg

[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.

Dude
I can run 128 instance of Diva playing chords with chorus and reverb
Not even 64 with the multithread ON

Dude, it was like that for me long time ago.
Then I figured out how to setup Win & BIOS.

Audio is realtime, so yes, it's risky for multithreading. But the key is to make ALL YOUR THREADS 100% AVAILABLE ALL THE TIME.

Of course there will be crackling with tons of energy saving BS... How can plugin or DAW know when will BIOS & Win turn off a thread? And then you think "Damn I need better CPU". Apple custom chips are worse in this regard, I think they have energy saving options which you can't access/disable at all.

It's simply unbelievable that Multipoly HW is multithreaded, and software is not.
It's like we're living in 1999.

[IvyBirds]

It's simply unbelievable that Multipoly HW is multithreaded, and software is not.
It's like we're living in 1999.

The CPU in the hardware is a BCM2837 processor, that is a 64-bit ARM Cortex-A53 based quad-core processor that runs at 1.2 GHz and has a single GB of RAM available to it

A single core in any modern CPU will be more powerful and therefore faster than all four cores in the BCM2837

[hcv242]

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

i have no midi controller plugged on this macbook pro m1 and the lag is present. following the instructions of the korg support forum made it quicker, but it still lags. even the standalone lags.

[frag]

It's simply unbelievable that Multipoly HW is multithreaded, and software is not.
It's like we're living in 1999.

The CPU in the hardware is a BCM2837 processor, that is a 64-bit ARM Cortex-A53 based quad-core processor that runs at 1.2 GHz and has a single GB of RAM available to it

A single core in any modern CPU will be more powerful and therefore faster than all four cores in the BCM2837

Yet many people report crackling with multi-layer patches. Or full polyphony.
Why would we bother with MT, people will buy new PCs... Sure, I'm gonna waste 2-3 months of my life setting up completely new system from scratch, just because of couple of synths which I sometimes play for fun.
The worse thing is, some programmers don't even understand how to write multithreaded plugin.
It's 1999 all over again, it's Groundhog day

[sheeepsss]

I just noted that Massive X has the same lagginess when changing presets both in Ableton and Reaper. I think it's unacceptable to wait even just 1 second for a preset change: for me it has to be instantaneous like I'm accostumed to with even keyboards from the 80s lol.
I don't want to sound rude or anything but it kills the vibe

[IvyBirds]

It's simply unbelievable that Multipoly HW is multithreaded, and software is not.
It's like we're living in 1999.

The CPU in the hardware is a BCM2837 processor, that is a 64-bit ARM Cortex-A53 based quad-core processor that runs at 1.2 GHz and has a single GB of RAM available to it

A single core in any modern CPU will be more powerful and therefore faster than all four cores in the BCM2837

Yet many people report crackling with multi-layer patches. Or full polyphony.
Why would we bother with MT, people will buy new PCs... Sure, I'm gonna waste 2-3 months of my life setting up completely new system from scratch, just because of couple of synths which I sometimes play for fun.
The worse thing is, some programmers don't even understand how to write multithreaded plugin.
It's 1999 all over again, it's Groundhog day

No I think the worst part is end users who think it takes 2-3 months to setup a new PC and can't seem to grasp that your DAW in 2025 is the best place to manage multi threads and cores along with the OS and not individual plugins

It's not 1999 all over again as I am not rocking at Pentium at 400mHz with 500mb of RAM

I am using a processor that rocks 8 performance cores at 5.8 gHz, has 16 efficient cores, and a total of 32 total threads

I want all my plugins to run in a single core and thread and be optimized for that, and let my DAW manage that process, unlike you apparently I realize that it's 2025 and I am using a modern computer and a modern DAW

I make sure my OS is using the least amount of CPU, Cores, and Threads possible and that my overall system is tweaked for peak performance of Audio and Video Editing and rendering

As such I can run multiple instances of this plugin with zero issues, and no crackling. I can use Audiogridder to have each instance run on its own single core if I want

[sheeepsss]

It's simply unbelievable that Multipoly HW is multithreaded, and software is not.
It's like we're living in 1999.

The CPU in the hardware is a BCM2837 processor, that is a 64-bit ARM Cortex-A53 based quad-core processor that runs at 1.2 GHz and has a single GB of RAM available to it

A single core in any modern CPU will be more powerful and therefore faster than all four cores in the BCM2837

Yet many people report crackling with multi-layer patches. Or full polyphony.
Why would we bother with MT, people will buy new PCs... Sure, I'm gonna waste 2-3 months of my life setting up completely new system from scratch, just because of couple of synths which I sometimes play for fun.
The worse thing is, some programmers don't even understand how to write multithreaded plugin.
It's 1999 all over again, it's Groundhog day

No I think the worst part is end users who think it takes 2-3 months to setup a new PC and can't seem to grasp that your DAW in 2025 is the best place to manage multi threads and cores along with the OS and not individual plugins

It's not 1999 all over again as I am not rocking at Pentium at 400mHz with 500mb of RAM

I am using a processor that rocks 8 performance cores at 5.8 gHz, has 16 efficient cores, and a total of 32 total threads

I want all my plugins to run in a single core and thread and be optimized for that, and let my DAW manage that process, unlike you apparently I realize that it's 2025 and I am using a modern computer and a modern DAW

I make sure my OS is using the least amount of CPU, Cores, and Threads possible and that my overall system is tweaked for peak performance of Audio and Video Editing and rendering

As such I can run multiple instances of this plugin with zero issues, and no crackling. I can use Audiogridder to have each instance run on its own single core if I want

Do preset changing work instantly (without any perceivable lag) for you?
My system is BIOS/Win fully optimized, I know very well this stuff, but I have this lagginess that I'm not sure it depends from my system specs. Pretty much all other VST3s that I use don't have this problem

[frag]

It's simply unbelievable that Multipoly HW is multithreaded, and software is not.
It's like we're living in 1999.

The CPU in the hardware is a BCM2837 processor, that is a 64-bit ARM Cortex-A53 based quad-core processor that runs at 1.2 GHz and has a single GB of RAM available to it

A single core in any modern CPU will be more powerful and therefore faster than all four cores in the BCM2837

Yet many people report crackling with multi-layer patches. Or full polyphony.
Why would we bother with MT, people will buy new PCs... Sure, I'm gonna waste 2-3 months of my life setting up completely new system from scratch, just because of couple of synths which I sometimes play for fun.
The worse thing is, some programmers don't even understand how to write multithreaded plugin.
It's 1999 all over again, it's Groundhog day

No I think the worst part is end users who think it takes 2-3 months to setup a new PC and can't seem to grasp that your DAW in 2025 is the best place to manage multi threads and cores along with the OS and not individual plugins

It's not 1999 all over again as I am not rocking at Pentium at 400mHz with 500mb of RAM

I am using a processor that rocks 8 performance cores at 5.8 gHz, has 16 efficient cores, and a total of 32 total threads

I want all my plugins to run in a single core and thread and be optimized for that, and let my DAW manage that process, unlike you apparently I realize that it's 2025 and I am using a modern computer and a modern DAW

I make sure my OS is using the least amount of CPU, Cores, and Threads possible and that my overall system is tweaked for peak performance of Audio and Video Editing and rendering

As such I can run multiple instances of this plugin with zero issues, and no crackling. I can use Audiogridder to have each instance run on its own single core if I want

Even after 3 years, I'm still fixing stuff on newer Windows 10 machine. It's bloatware, full of ridiculous bugs. 11 is even worse, only stripped down versions make sense.

Btw, you have some magic button which installs & sets up all programs you use, in one click?

[frag]

Do preset changing work instantly (without any perceivable lag) for you?
My system is BIOS/Win fully optimized, I know very well this stuff, but I have this lagginess that I'm not sure it depends from my system specs. Pretty much all other VST3s that I use don't have this problem

There is lag, but it's older machine.