Korg Collection (V2.0 released, GUI update!)
-
- KVRian
- 1073 posts since 24 Apr, 2008 from USA
I don’t understand why Korg won’t add more effects into MDE-X. Like the chorus from triton. should be easy to do especially now that they have triton VSTi out
Main Computer Specs: MacBook M1 Max, 32GB, 4TB, Cubase 13.
-
mountainmaster mountainmaster https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=153531
- KVRian
- 620 posts since 10 Jun, 2007 from Netherlands
Thanks. The Windows version is still at version 2.0.5 though. So these fixes must be Mac only.aMUSEd wrote: Sun Aug 23, 2020 10:19 pm There is an update according to the Korg Software Pass eg Polysix
So might include a fix for some of these issues?Changes in Version 2.0.7
- Stability improvements
- Some of the parameters were not listed as automation parameters in AudioUnit version. This has been fixed.
Was the Cubase blacklisting issue fixed in 2.0.7? If it was, I guess us Windows folks would have gotten this update as well.
- KVRAF
- 24406 posts since 7 Jan, 2009 from Croatia
Because it's a 1:1 representation of their hardware MDE effects chip with algorithms it had.TS-12 wrote: Sun Aug 23, 2020 11:50 pm I don’t understand why Korg won’t add more effects into MDE-X. Like the chorus from triton. should be easy to do especially now that they have triton VSTi out
- KVRAF
- 14436 posts since 16 Feb, 2005 from Planet Earth, Somewhere
Same thing I discovered alas, 2.0.5 on pc still.mountainmaster wrote: Tue Aug 25, 2020 11:02 amThanks. The Windows version is still at version 2.0.5 though. So these fixes must be Mac only.aMUSEd wrote: Sun Aug 23, 2020 10:19 pm There is an update according to the Korg Software Pass eg Polysix
So might include a fix for some of these issues?Changes in Version 2.0.7
- Stability improvements
- Some of the parameters were not listed as automation parameters in AudioUnit version. This has been fixed.
Was the Cubase blacklisting issue fixed in 2.0.7? If it was, I guess us Windows folks would have gotten this update as well.
no the blacklisting was only on PC, never on mac.
rsp
sound sculptist
-
Funkybot's Evil Twin Funkybot's Evil Twin https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=116627
- KVRAF
- 12442 posts since 16 Aug, 2006
Does anyone know if Odyssey is getting the 2.0 treatment? Is that the only one that got left out?
- Banned
- 7624 posts since 13 Nov, 2015 from Norway
Do you now ig Korg Legacy is resizeable? My eyes isnt what they used to beEvilDragon wrote: Tue Aug 25, 2020 8:37 pmBecause it's a 1:1 representation of their hardware MDE effects chip with algorithms it had.TS-12 wrote: Sun Aug 23, 2020 11:50 pm I don’t understand why Korg won’t add more effects into MDE-X. Like the chorus from triton. should be easy to do especially now that they have triton VSTi out
EnergyXT3 - LMMS - FL Studio | Roland SH201 - Waldorf Rocket | SoundCloud - Bandcamp
-
- KVRian
- 1073 posts since 24 Apr, 2008 from USA
In that case I don’t understand why Korg don’t wanna make a vst effects processor with Triton effects engine. Or make Triton also act as vst affects pluginEvilDragon wrote: Tue Aug 25, 2020 8:37 pmBecause it's a 1:1 representation of their hardware MDE effects chip with algorithms it had.TS-12 wrote: Sun Aug 23, 2020 11:50 pm I don’t understand why Korg won’t add more effects into MDE-X. Like the chorus from triton. should be easy to do especially now that they have triton VSTi out
Main Computer Specs: MacBook M1 Max, 32GB, 4TB, Cubase 13.
- KVRAF
- 24406 posts since 7 Jan, 2009 from Croatia
It is now.Halonmusic wrote: Tue Aug 25, 2020 9:14 pmDo you now ig Korg Legacy is resizeable? My eyes isnt what they used to beEvilDragon wrote: Tue Aug 25, 2020 8:37 pmBecause it's a 1:1 representation of their hardware MDE effects chip with algorithms it had.TS-12 wrote: Sun Aug 23, 2020 11:50 pm I don’t understand why Korg won’t add more effects into MDE-X. Like the chorus from triton. should be easy to do especially now that they have triton VSTi out![]()
- Banned
- 7624 posts since 13 Nov, 2015 from Norway
Thank you.EvilDragon wrote: Tue Aug 25, 2020 10:44 pmIt is now.Halonmusic wrote: Tue Aug 25, 2020 9:14 pmDo you now ig Korg Legacy is resizeable? My eyes isnt what they used to beEvilDragon wrote: Tue Aug 25, 2020 8:37 pmBecause it's a 1:1 representation of their hardware MDE effects chip with algorithms it had.TS-12 wrote: Sun Aug 23, 2020 11:50 pm I don’t understand why Korg won’t add more effects into MDE-X. Like the chorus from triton. should be easy to do especially now that they have triton VSTi out![]()
EnergyXT3 - LMMS - FL Studio | Roland SH201 - Waldorf Rocket | SoundCloud - Bandcamp
-
- KVRer
- 14 posts since 29 Apr, 2013
I will never buy any Korg plugin again.
I don't think they care about their customers. Polysix Win 10, Cubase - is pretty unstable, blacklisted and the presets are incompatible with the old version.
When loading a preset with the daw-project where the old version (with the old gui) was inserted - the sound is not the same with new version.
The only thing which is working is by loading the project with the old polysix version, saving the preset as file and afterwards loading the file into the new version - pretty lame. Also pretty lame that you can't use the old and the new side by side because internally the plugin is called the same - pretty lame.
Also, I think, the reason why it's blacklisted in Cubase is pretty simple, Polysix starting with 2.0.0 is not stable, it crashes serveral times and when digging into eventviewer the reason for the crash is polysix.dll - pretty lame, unusable - a showstopper...
Also the latest fix version of polysix (2.0.5) didn't fix any major issues and they stuck at 2.0.5 (May) where mac os x 2.0.8 (from some days ago) fixing minor issues compared to show stopper issues they have...
Also, when talking to support asking for the lastest old gui polysix version to continue the projects also describing the issues, you didn't get an answer - just a formal email answer that you will get an answer shortly - tried it several times, checked junk - finally no answer. By luck I found an older version of polysix on my storage. The biggest spoof, if looking in their kb they are describing the issue as a new issue since 1.0.5. May update and that a fix should be ready very soon (entry was from may I think)...
Btw. the reason why I didn't save it on my side is pretty simple, when buying the collection several years ago, I got an email with links for the downloads - they were working over the years also with the latest maintenance releases - so I didn't see a reason to make backups on my side - that was a big mistake. With 2.0 release the links were not working anymore and under my web user account I only get the new versions.
The interesting thing, all other plugins from the collection are working great and don't have issues, I don't know what they have made wrong with polysix.
For me Korg plugins are out of scope now because the market is so big, with so many many good plugins - so there is really no need to make business with a company which doesn''t really care about their customers.
I really have never seen such a bad behavior from a big company support wise, also the product itself is not working months after its release. Korg is not a small company, were this maybe can be excused.
BYE, BYE I really liked Polysix, was one of my favorites. RIP
I don't think they care about their customers. Polysix Win 10, Cubase - is pretty unstable, blacklisted and the presets are incompatible with the old version.
When loading a preset with the daw-project where the old version (with the old gui) was inserted - the sound is not the same with new version.
The only thing which is working is by loading the project with the old polysix version, saving the preset as file and afterwards loading the file into the new version - pretty lame. Also pretty lame that you can't use the old and the new side by side because internally the plugin is called the same - pretty lame.
Also, I think, the reason why it's blacklisted in Cubase is pretty simple, Polysix starting with 2.0.0 is not stable, it crashes serveral times and when digging into eventviewer the reason for the crash is polysix.dll - pretty lame, unusable - a showstopper...
Also the latest fix version of polysix (2.0.5) didn't fix any major issues and they stuck at 2.0.5 (May) where mac os x 2.0.8 (from some days ago) fixing minor issues compared to show stopper issues they have...
Also, when talking to support asking for the lastest old gui polysix version to continue the projects also describing the issues, you didn't get an answer - just a formal email answer that you will get an answer shortly - tried it several times, checked junk - finally no answer. By luck I found an older version of polysix on my storage. The biggest spoof, if looking in their kb they are describing the issue as a new issue since 1.0.5. May update and that a fix should be ready very soon (entry was from may I think)...
Btw. the reason why I didn't save it on my side is pretty simple, when buying the collection several years ago, I got an email with links for the downloads - they were working over the years also with the latest maintenance releases - so I didn't see a reason to make backups on my side - that was a big mistake. With 2.0 release the links were not working anymore and under my web user account I only get the new versions.
The interesting thing, all other plugins from the collection are working great and don't have issues, I don't know what they have made wrong with polysix.
For me Korg plugins are out of scope now because the market is so big, with so many many good plugins - so there is really no need to make business with a company which doesn''t really care about their customers.
I really have never seen such a bad behavior from a big company support wise, also the product itself is not working months after its release. Korg is not a small company, were this maybe can be excused.
BYE, BYE I really liked Polysix, was one of my favorites. RIP
-
WatchTheGuitar WatchTheGuitar https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=440193
- KVRAF
- 13256 posts since 30 Apr, 2019
Don’t let the DAW hit you on the way out.
- KVRian
- 1276 posts since 30 Apr, 2004 from Louisville, KY
Hadn't heard that one before.
바보
-
WatchTheGuitar WatchTheGuitar https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=440193
- KVRAF
- 13256 posts since 30 Apr, 2019
I think I may have had an original thought. Now I definitely need to lie down.
- KVRAF
- 43918 posts since 11 Aug, 2008 from clown world
+1
Anyone who can make you believe absurdities can make you commit atrocities.
-
- KVRist
- 33 posts since 27 Jul, 2018
Hi, I have strange problem with standalone versions of KC. I bought Roland Go:keys and using this keyboard as midi master keyboard. I can see Roland Go:keys in audio/midi settings but standalone versions dont responds midi informations from go:keys. Another midi master keyboards works. KC vst versions in Cubase works. Standalone versions of Arturia works, Dexed standalone works, only KC standalone no
.
I try two PCs.
Can anybody try go:keys with standalone KC?
Thanks
I try two PCs.
Can anybody try go:keys with standalone KC?
Thanks
