Yeah, I had that too (Cubase Artist 10.5.2). Specifically only the Polysix. I ended up downloading it again and reinstalling, but I didn't actually have to - turned out it was the correct version. I just unblacklisted it and it worked fully next time up. Strange little glitch, but doesn't seem to stop you using it.BassMasterK wrote: Sat Jun 13, 2020 8:49 pm I am using Cubase 10, and for some reason, Cubase has blacklisted my Polysix vsti. It is 64 bit so that isn't the issue. Any other users out there having this problem? It was recently updated. I'm wondering if there was something in the first release that Cubase didn't like. I'm tempted to just move it out of the blacklist area but wanted to check in and see if anyone else is also experiencing this.
Korg Collection (V2.0 released, GUI update!)
-
- KVRAF
- 8677 posts since 24 May, 2002 from Tutukaka, New Zealand
-
- KVRist
- 131 posts since 11 Apr, 2004
Hi, I'm not able to make my own controller mapping permanent with the KORG plugins.
When I change the CC-assignment in Polysix (and the other KORG plugins), chose the menu item "Make Current Controller Map Default" and reload the plugin, I have the standard CC-assignment from before saving my own.
It's only the case with the plugin versions, the standalone versions save my own CC-map as default (but don't "transfer" them to the plugins).
I'm using Logic Pro X 10.5.1 (macOS Catalina) and the newest KORG plugins (Collection 2).
Any ideas?
Thanks,
Florian
When I change the CC-assignment in Polysix (and the other KORG plugins), chose the menu item "Make Current Controller Map Default" and reload the plugin, I have the standard CC-assignment from before saving my own.
It's only the case with the plugin versions, the standalone versions save my own CC-map as default (but don't "transfer" them to the plugins).
I'm using Logic Pro X 10.5.1 (macOS Catalina) and the newest KORG plugins (Collection 2).
Any ideas?
Thanks,
Florian
Mac Studio M2 Ultra, Sonoma, Logic X, Orion 32+, mioXL, V-Synth XT, JD-990, MC-909, OB-X8, NINA, KK61 mkII
- KVRAF
- 14436 posts since 16 Feb, 2005 from Planet Earth, Somewhere
Hi, you are running the latest ones right?
I had that issue with i think two or three of them on mac and pc......but I think updates have fixed them in both. I do remembered it happened for me in polysix and at least one if not two others,(either ms20 or monopoly) but never happened in all of them.
rsp
I had that issue with i think two or three of them on mac and pc......but I think updates have fixed them in both. I do remembered it happened for me in polysix and at least one if not two others,(either ms20 or monopoly) but never happened in all of them.
rsp
sound sculptist
-
- KVRist
- 131 posts since 11 Apr, 2004
I have the newest one, right.
I have this same problem on MacBook and MacPro, both had the older versions installed before...
I have this same problem on MacBook and MacPro, both had the older versions installed before...
Mac Studio M2 Ultra, Sonoma, Logic X, Orion 32+, mioXL, V-Synth XT, JD-990, MC-909, OB-X8, NINA, KK61 mkII
- KVRAF
- 14436 posts since 16 Feb, 2005 from Planet Earth, Somewhere
Sorry, I don't use AU. A possible workaround.
Does Logic allow you to save a plug in in a 'default' state? In Cubendo we can save a default preset for each plugin which usually means every new instance starts out in whatever configuration the default preset is setup as.
rsp
Does Logic allow you to save a plug in in a 'default' state? In Cubendo we can save a default preset for each plugin which usually means every new instance starts out in whatever configuration the default preset is setup as.
rsp
sound sculptist
-
- KVRist
- 131 posts since 11 Apr, 2004
Yes, there is such an option in Logic but it doesn't solve the problem.
It seams that the default CC-map had to be sevd "within" the plugin itself not "only" in the Logic preset of the plugin.
I just unistalled Polysix and reinstalled it (2.0.6) - same problem...
It seams that the default CC-map had to be sevd "within" the plugin itself not "only" in the Logic preset of the plugin.
I just unistalled Polysix and reinstalled it (2.0.6) - same problem...
Mac Studio M2 Ultra, Sonoma, Logic X, Orion 32+, mioXL, V-Synth XT, JD-990, MC-909, OB-X8, NINA, KK61 mkII
-
- KVRist
- 97 posts since 3 Mar, 2003 from Tampere, Finland
Yay for the updated GUIs!
But... Now when I load an old project in Cubase and it loads the v.2.0 plugins in place of the old versions, the settings for them are not recalled.
This is for projects that were saved with v.1.x plugins and at least Monopoly and MS-20 do not recall their settings. This is on macOS 10.15.6 and Cubase 10.0.60.
Anyone else seeing this?
But... Now when I load an old project in Cubase and it loads the v.2.0 plugins in place of the old versions, the settings for them are not recalled.
This is for projects that were saved with v.1.x plugins and at least Monopoly and MS-20 do not recall their settings. This is on macOS 10.15.6 and Cubase 10.0.60.
Anyone else seeing this?
- KVRer
- 26 posts since 11 Nov, 2017 from Stargard
I had pretty bad crashes with new Polysix and my Cubase 10.5.20 (Win 10 Pro x64). Maybe it's too early for
but everything seems to be fine after doing some updates of Windows and MS Visual C++ executables (see attached picture).
You do not have the required permissions to view the files attached to this post.
also Protracker 3.62 @ Amiga 1200 / WinUAE
- KVRAF
- 14436 posts since 16 Feb, 2005 from Planet Earth, Somewhere
They still have not fixed the incompatibility with poly 6 and cubase.
It is as you know blacklisted and I guess you might have forced it off that list.
So odd that it is the only one that is, and it is taking them so long to fix it. At least once a month I remind them, and they say they are still working on it.
rsp
It is as you know blacklisted and I guess you might have forced it off that list.
So odd that it is the only one that is, and it is taking them so long to fix it. At least once a month I remind them, and they say they are still working on it.
rsp
sound sculptist
-
- KVRist
- 111 posts since 13 Sep, 2013 from Berlin, Germany
After announcing, it took them many many years to update the GUI. I fear it will take some more years to fix the blacklisting
Luckily, it runs fine here after just forcing it off of the list. Didn't use it extensively, though.
-
- KVRist
- 30 posts since 14 Feb, 2019
Does anybody have any idea how I can download the Korg collection 2 demo, please?
I downloaded their app, logged in with my my Korg ID, then the app tells me it wants authorization to view my profile info, after clicking OK, it gives me a 'this webpage cannot be displayed' error... I can actually bypass that and get to the shop by clicking the 'terms and conditions' link, but I can't the demo versions of the products.
Thanks.
I downloaded their app, logged in with my my Korg ID, then the app tells me it wants authorization to view my profile info, after clicking OK, it gives me a 'this webpage cannot be displayed' error... I can actually bypass that and get to the shop by clicking the 'terms and conditions' link, but I can't the demo versions of the products.
Thanks.
- KVRer
- 26 posts since 11 Nov, 2017 from Stargard
Yeah... it was too early for the
... it was 'workable' as the P6 was not crashing during the job anymore (e.g. when closing plugin's GUI) but everytime on exiting from Cubase ("Cubase stopped working..." and seeyah...).
Now I use Polysix through (paid) tool called jBridger (sure you guys know this little one).
No trouble (so far...).
Now I use Polysix through (paid) tool called jBridger (sure you guys know this little one).
No trouble (so far...).
also Protracker 3.62 @ Amiga 1200 / WinUAE
- KVRAF
- 14436 posts since 16 Feb, 2005 from Planet Earth, Somewhere
You can always go back to the pre GUI updated Polysix I believe. Apart from it being very small, I don't recall Cubendo blacklisting it.
rsp
rsp
sound sculptist
- KVRAF
- 37383 posts since 14 Sep, 2002 from In teh net
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.
