Korg Collection 3 now has VST3 and Silicon support!

[zzz00m]

On Windows, software pass thinks M1 needs updating no matter how many times I update it, and software pass. I've un-installed M1, restarted, installed new version etc. I'm up to date but software pass doesn't know it yet.

Same here. It's safe to ignore Software Pass if you have the latest version of the synth installed.

Software Pass can be a bit buggy. KORG had a similar issue with Software Pass on the previous round of synth updates, and issued version 1.1.11 (current for Windows) to fix that.

The latest can always be found here: https://id.korg.com/static_pages/3

[chk071]

Tell me again how VST3s are no more buggy or unstable than VST2s, and developers have no issues developing them...

Nice logic. Next time a VST2 is buggy, I blame VST2 as well.

It's not one buggy plugin though. Or one developer. This is a recurring theme and developers will tell you the same. VST3's just tend to be buggier for a variety of reasons

As I mentioned elsewhere, not my experience. The VST3's I usually use aren't more or less buggy than their VST2 counterparts.

On Windows, that is.

[zvenx]

The thing is some developers have little or no issue with vst3 and some do...
look at two new things announced today (kilohearts v2 and acon acusonica ara2), both have vst3, but have had vst3 for awhile. I am not aware of any vst3 issues on either and I have been using both for well over a year or two now.
rsp

[kritikon]

For any of the plugins I use there are no issues with VST3. Only one plugin crashes and that's Korg's fault not Steinberg's (and it's VST2... ) Some of them can use sidechains where they couldn't with VST2, so by definition they are better being VST3. In the same way there's an opinion Cubase users are trying to find something to defend it, there are also opinions that just slag Steinberg for VST3...because they can and want to. TBH I don't give a shit either way. My VST3 plugins do what they're supposed to. I could care less whatever the f*ck Mac users use and how it works for them, same as they could probably give whatever f*ck I use on Windows and how it works for me. And if they do care...they're fk'n eejits with too much time on their hands.

[Aloysius]

On Windows, software pass thinks M1 needs updating no matter how many times I update it, and software pass. I've un-installed M1, restarted, installed new version etc. I'm up to date but software pass doesn't know it yet.

Same here. It's safe to ignore Software Pass if you have the latest version of the synth installed.

Software Pass can be a bit buggy. KORG had a similar issue with Software Pass on the previous round of synth updates, and issued version 1.1.11 (current for Windows) to fix that.

The latest can always be found here: https://id.korg.com/static_pages/3

Thank you. I have updated both the software pass and the plugin on numerous occasions. I'm up to date. It seems KORG are not!!!

[mothra]

For any of the plugins I use there are no issues with VST3. Only one plugin crashes and that's Korg's fault not Steinberg's (and it's VST2... ) Some of them can use sidechains where they couldn't with VST2, so by definition they are better being VST3. In the same way there's an opinion Cubase users are trying to find something to defend it, there are also opinions that just slag Steinberg for VST3...because they can and want to. TBH I don't give a shit either way. My VST3 plugins do what they're supposed to. I could care less whatever the f*ck Mac users use and how it works for them, same as they could probably give whatever f*ck I use on Windows and how it works for me. And if they do care...they're fk'n eejits with too much time on their hands.

LOL as soon as I upgraded to Cubase 12 Pro I went through and wiped out all my VST2s just because I could. Only have a handful left in there and those are from a few devs that are just dragging their feet (NI and Absynth being the major one I'm hoping gets updated one day). People are really getting their panties in a bunch over the whole thing for no reason. Not a single issue with any VST3 version of a plugin here, like you they just do the job they're supposed to. If they dont, its not Steinberg's fault as many other devs seem to be able to navigate and code to the VST3 spec just fine..

[zvenx]

https://support.korguser.net/hc/en-us/s ... 0001101426

rsp

[WasteLand]

https://support.korguser.net/hc/en-us/s ... 0001101426

rsp

a fix! yeah!

[Sahul]

Finally! Just did a very quick test with the Korg M1 v2.32. It seems to be fixed now: old Cubase projects open fine and also I can load previously saved vstpresets without crashing the DAW. So kudos to Korg. They took their time, though.

[mossie23]

Just installed the latest version of the Polysix and Monopoly to get the VST3s. (I'm on OSX 10.14, Ableton 11.1). Removed the AU and VST2 files, and the VST3s aren't working anymore. Put the VST2s back, and they work again. Looking at the filesizes of the VST2 and VST3 files (>50mb vs ±700kb) makes me think the VST3 versions are just a wrapper for the VST2 plugins. Maybe that was what was causing everyone's DAW to crash.

I really hope Korg will release "real" VST3s for the legacy plugins (the OPSix is a real VST3). I want to get rid of all my VST2 plugins, not even have them on my system. Korg now needs them installed, in a specific place (the VST2 folder), and you can't specify that folder.

[Echoes in the Attic]

Just installed the latest version of the Polysix and Monopoly to get the VST3s. (I'm on OSX 10.14, Ableton 11.1). Removed the AU and VST2 files, and the VST3s aren't working anymore. Put the VST2s back, and they work again. Looking at the filesizes of the VST2 and VST3 files (>50mb vs ±700kb) makes me think the VST3 versions are just a wrapper for the VST2 plugins. Maybe that was what was causing everyone's DAW to crash.

I really hope Korg will release "real" VST3s for the legacy plugins (the OPSix is a real VST3). I want to get rid of all my VST2 plugins, not even have them on my system. Korg now needs them installed, in a specific place (the VST2 folder), and you can't specify that folder.

I had the same experience with tone2 Icarus. I removed the VST2 and the vst3 didn’t work anymore. Seems not ideal to require the vst2 version to be there.

[mothra]

Just installed the latest version of the Polysix and Monopoly to get the VST3s. (I'm on OSX 10.14, Ableton 11.1). Removed the AU and VST2 files, and the VST3s aren't working anymore. Put the VST2s back, and they work again. Looking at the filesizes of the VST2 and VST3 files (>50mb vs ±700kb) makes me think the VST3 versions are just a wrapper for the VST2 plugins. Maybe that was what was causing everyone's DAW to crash.

I really hope Korg will release "real" VST3s for the legacy plugins (the OPSix is a real VST3). I want to get rid of all my VST2 plugins, not even have them on my system. Korg now needs them installed, in a specific place (the VST2 folder), and you can't specify that folder.

Ahh crap you're right. Haven't tried to use the plugins since updating (just played with the standalone), but just fired up Live and yep, cant load any of my VST3s. Guess I have to go reinstall the damn things and not delete the VST2 now. Come on Korg get it together already. Arturia's AU's are just wrapped VSTs, but at least they had the forethought to put the damn VST inside the AU bundle.

[mossie23]

I had the same experience with tone2 Icarus. I removed the VST2 and the vst3 didn’t work anymore. Seems not ideal to require the vst2 version to be there.

I guess it's too much work for Korg to turn the legacy plugins into VST3. Fine, but then allow me to decide where I want them, or put them in a hidden folder somewhere. BTW, the AUs also seem to be wrapped VST2s. This was a quick and dirty job by Korg.

[kritikon]

Yeah, I deleted all the VST2s as well and none of the VST3s worked. I actually did it several times before I twigged the VST3s must need the VST2s to work...all the VST3s are the same tiny size. Somehow this doesn't feel like an update, more of a lick of paint to cover up the rust. Still no Odyssey VST3 either.

[Weasel-Boy]

Still no Odyssey VST3 either.

Yes, there actually is an Odyssey VST3. Version 1.4.0. There is a problem with it running on an M1 Mac.
The Arpeggiator is broken. None of the 16 Parameter sliders work. Adjust any one of them and they'll snap back to "0". You can't set any values with it. The only recourse is to remove the VST3 version from the VST3 folder so the VST2 version takes over. That version's Arpeggiator functions correctly.

Korg has been informed but no fix yet.