KVR Audio

EvilDragon · Post by **EvilDragon** » Sat Jan 24, 2026 10:51 am

I would hope they will enable that at some point, yes. Seems like it exists under the hood and they may be working on it but it's not yet ready for public. Just a guess.

Weasel-Boy · Post by **Weasel-Boy** » Sat Jan 24, 2026 8:51 pm

EvilDragon wrote: Sat Jan 24, 2026 10:51 am I would hope they will enable that at some point, yes. Seems like it exists under the hood and they may be working on it but it's not yet ready for public. Just a guess.

Considering that the original Triton was always able to deal with user samples coupled with the fact that KORG chose to ignore this functionality since the introduction of the plug-in, six years ago, my guess would be that they'll never implement it.

mi-os · Post by **mi-os** » Thu Jan 29, 2026 1:15 am

A little tip: never click "update all" in Korg Pass if you don't have all plugins installed (for which you have a license?). I made that mistake and found myself in a nightmare situation. The effing thing tries to update and install everything (but demo versions?).

c_voltage · Post by **c_voltage** » Thu Jan 29, 2026 6:58 am

mi-os wrote: Thu Jan 29, 2026 1:15 am A little tip: never click "update all" in Korg Pass if you don't have all plugins installed (for which you have a license?). I made that mistake and found myself in a nightmare situation. The effing thing tries to update and install everything (but demo versions?).

Another tip: never use Korg Pass for install\uninstall, and monitoring updates. Only can use for install demo. Will be less questions. (Installers can be downloaded from Korg account)

dune_rave · Post by **dune_rave** » Thu Jan 29, 2026 7:17 am

c_voltage wrote: Thu Jan 29, 2026 6:58 am
mi-os wrote: Thu Jan 29, 2026 1:15 am A little tip: never click "update all" in Korg Pass if you don't have all plugins installed (for which you have a license?). I made that mistake and found myself in a nightmare situation. The effing thing tries to update and install everything (but demo versions?).
Another tip: never use Korg Pass for install\uninstall, and monitoring updates. Only can use for install demo. Will be less questions. (Installers can be downloaded from Korg account)

I've just updated some from Korg Pass. I don't use custom folders so for me it seems to be OK.

c_voltage · Post by **c_voltage** » Thu Jan 29, 2026 8:12 am

dune_rave wrote: Thu Jan 29, 2026 7:17 am I've just updated some from Korg Pass. I don't use custom folders so for me it seems to be OK.

Idk With every launch i observing or mismatch in version numbering (and the offer to update resp) despite already installed latest version, or written that product not installed at all (but he installed).
And it's not because i used separate instraller - all stay the same if after installing thru manager too.
(Maybe it's just for me ? idk i did update Korg Pass many times)

EvilDragon · Post by **EvilDragon** » Fri Apr 17, 2026 9:24 pm

LuizAtKorg wrote: Mon Dec 08, 2025 6:28 amThks! Noted. "Fixed update hopefully next on."

Thank you!

It would be really great if you could also convey this feature request for Trinity plugin: being able to copy oscillator settings (like in Triton plugin!), being able to copy individual FX settings and all FX settings between programs, and to copy timbres in Combi mode (also as in Triton plugin), would be some real quality of life improvements!

jamcat · Post by **jamcat** » Sat Apr 18, 2026 6:02 pm

Are these KORG plugins still just stupid wrappers that are dependent on the obsolete VST2 versions?

tumface · Post by **tumface** » Sat Apr 18, 2026 6:09 pm

No, only the MDE-X, M1, Wavestation, and MS-20 (I think) plugins require the VST2 version. Also, there's nothing wrong with using wrapping. It saves code duplication on disk and in memory. It also doesn't limit feature availability, because you can stick as much extra stuff into the VST2 as you want, and the VST3 wrapper can tap into it and expose it in the VST3 API, even if it can't be exposed via the VST2 API.

aMUSEd · Post by **aMUSEd** » Sat Apr 18, 2026 6:11 pm

The original ones still do - so MS20, Polysix, MonoPoly, Wavestation, M1 and Legacy Cell - but the rest don't

jamcat · Post by **jamcat** » Sat Apr 18, 2026 11:32 pm

tumface wrote: Sat Apr 18, 2026 6:09 pm there's nothing wrong with using wrapping. It saves code duplication on disk and in memory.

Who installs every plugin format? Especially one that is obsolete, like VST2?
I only install VST3, so being forced to install VST2 is a deal breaker for me.

jamcat · Post by **jamcat** » Sat Apr 18, 2026 11:34 pm

aMUSEd wrote: Sat Apr 18, 2026 6:11 pm The original ones still do - so MS20, Polysix, MonoPoly, Wavestation, M1 and Legacy Cell - but the rest don't

So the ones I'm interested in do, but not the ones that I don't care about.

tumface · Post by **tumface** » Sun Apr 19, 2026 5:08 am

jamcat wrote: Sat Apr 18, 2026 11:32 pm
tumface wrote: Sat Apr 18, 2026 6:09 pm there's nothing wrong with using wrapping. It saves code duplication on disk and in memory.
Who installs every plugin format? Especially one that is obsolete, like VST2?
I only install VST3, so being forced to install VST2 is a deal breaker for me.

VST2 is just a .dll with a different file extension. The VST3 loads the VST2 and uses it. It's the same thing that a lot of plugin makers do (Kilohearts, Plogue, etc.) except the supporting .dll is also the VST2 version, instead of something buried in %LOCALAPPDATA%\MyPluginCompany\SupportLibs or whatever. If you aren't using VST2 plugins, as you say, it has no effect on the DAW. I guess I don't understand the problem.

EvilDragon · Post by **EvilDragon** » Sun Apr 19, 2026 5:56 am

jamcat wrote: Sat Apr 18, 2026 6:02 pm Are these KORG plugins still just stupid wrappers that are dependent on the obsolete VST2 versions?

Well considering they are all built with JUCE, then yes, it's all like that. Even the newer plugins that don't even offer VST2 to install. But older ones keep VST2 for DAW project compatibility (Korg didn't implement VST3 plugin migration).

PAK · Post by **PAK** » Sun Apr 19, 2026 5:08 pm

jamcat wrote: Sat Apr 18, 2026 11:32 pm
tumface wrote: Sat Apr 18, 2026 6:09 pm there's nothing wrong with using wrapping. It saves code duplication on disk and in memory.
Who installs every plugin format? Especially one that is obsolete, like VST2?
I only install VST3, so being forced to install VST2 is a deal breaker for me.

I understand some reluctance to use a VST3 which points at a VST2 binary. Wrapped VST’s do appear more “problematic” with Cubase (at least on Mac.. ) EG Rob Papen’s wrapped VST3’s (Which require the VST2) seem to cause Cubase to crash on exit.

That said; wrapping can also work fine. You’re already using a bunch of wrapped stuff anyway - if you weren’t aware. Go to '/Library/Application Support/Universal Audio/Plug-Ins’. Was ist das? That’s the Lunacomponents Universal Audio point their VST3 plugins at, thus why they’re all around 20MB in size. Likewise, '/Library/Application Support/Softube/SSX/‘. That’s the SSX binaries Softube point their VST3’s at.

So companies are commonly "wrapping" stuff anyway (depending on how you define it). Steinberg also don’t have much room to complain considering they themselves wrap their AU plugins to point to the VST3, thus making AU users keep the VST3 version installed

Korg Collection 6 with PS-3300, Trinity and SGX-2 Piano