I knew there had been a couple of updates, so I finally got around to trying it out again (had given up on Opsix completely as it was so broken on my system). Well, initially surprised and pleased to discover that when I play it, it works beautifully, finally. Normal cpu usage and perfectly usable. Then as soon as I press stop it shoots up to 100% usage. It used to to go to 50% or maybe a bit more, now it maxes out the system, worse than ever. It really looks like the old denormal thingy. How did they make it even worse than before? There was an issue with Opsix and specific CPUs, obvs I have one of them and seems like it's never going to be fixed...until I get a new laptop.
I'm still a bit of a Korg fanboi, love their hw and bought shitloads over the years, but man, their sw side of things stinks. I never really tried out MultiPoly native though it piqued my interest. Was wary because of Opsix failure, now it's on the proscribed list for me. Not going near it. I never got really f**ked off about it because I got the hw owner discount, but I'd be livid if it had been full price.
So it's just me, or others still have Opsix failure?
Opsix native still broken for other users?
-
- KVRAF
- 9844 posts since 15 Sep, 2005 from East Coast of the USA
I just installed it again (haven't had it reinstalled yet since reinstalling Windows 11) and it's working fine here. I didn't see any huge jumps in the CPU like you described.
-
- KVRAF
- Topic Starter
- 8675 posts since 24 May, 2002 from Tutukaka, New Zealand
Ah well. Seems to be specific chips - mine's a 3 yr old mid range i7 HP, so it's not anything unusual. I was tempted to just throw my toys out of the cot and delete it forever, but I'm probably going to update my laptop end of this year or early next year, so I should probably wait and see. Hopefully it'll work on a new laptop. I quite like the GUI and for sure the native version is easier to program than the hw version. It still puts me off ever going for Korg sw again though.
-
- KVRAF
- 5149 posts since 13 Jul, 2004 from Earth
I had similar issues with the korg native vsts and some other vst's when i used Cubase where i played a few notes and waited a few seconds and saw the cpu usage go bezerk.kritikon wrote: Fri Jul 25, 2025 11:22 pm Ah well. Seems to be specific chips - mine's a 3 yr old mid range i7 HP, so it's not anything unusual. I was tempted to just throw my toys out of the cot and delete it forever, but I'm probably going to update my laptop end of this year or early next year, so I should probably wait and see. Hopefully it'll work on a new laptop. I quite like the GUI and for sure the native version is easier to program than the hw version. It still puts me off ever going for Korg sw again though.
The plugins i had issues with work fine in Studio one and Bitwig without any issues.
-
- KVRAF
- Topic Starter
- 8675 posts since 24 May, 2002 from Tutukaka, New Zealand
So, it might be Cubase as well my laptop...unfortunately, Opsix will lose out, I'm not going to change my DAW. You'd think Korg could code plugins that work with one of the established DAWs. Whatever the cause, it's sloppy coding on Korg's behalf. When they try to fix it, they break it even more.
-
- KVRist
- 280 posts since 13 May, 2004 from Italy
Hi, Opsix and Cubase are working fine here. Win 10, intel i9 12900k cpu, Amd video card. Don’t know what could be your issue, no spikes here, cpu usage ok
-
- KVRAF
- 2756 posts since 24 Nov, 2023
No issues with the Korg Opsix plugin on any of my PCs in Cubase. On Windows 10 and 11, and on i7 and i9 laptops and desktopskritikon wrote: Sat Jul 26, 2025 7:14 pm So, it might be Cubase as well my laptop...unfortunately, Opsix will lose out, I'm not going to change my DAW. You'd think Korg could code plugins that work with one of the established DAWs. Whatever the cause, it's sloppy coding on Korg's behalf. When they try to fix it, they break it even more.
-
- KVRAF
- 5149 posts since 13 Jul, 2004 from Earth
Weird. I saw the same issues that kritikon have and it happened on my Intel 13500 and 12700K but it worked fine with my AMD Ryzen 5700X setup.
This was on Cubase 11 and 12 and this was before windows and cubase was fully optimized for the P and E Core arcitecture and i never tested it on V13 since i upgraded Cubase to V13 and sold it since i use Bitwig these days but it did work fine in Studio one and Bitwig back then.
Maybe it is more of a chipset or motherboard or graphic card issue than cpu related.
This was on Cubase 11 and 12 and this was before windows and cubase was fully optimized for the P and E Core arcitecture and i never tested it on V13 since i upgraded Cubase to V13 and sold it since i use Bitwig these days but it did work fine in Studio one and Bitwig back then.
Maybe it is more of a chipset or motherboard or graphic card issue than cpu related.
-
- KVRAF
- 3041 posts since 23 Jun, 2006 from Hungary
If multypoly goes down to 99 in BF discount ithat would be cool...
Youtube channel: https://youtube.com/@SoftSynthPortal
-
- KVRAF
- 9144 posts since 7 Oct, 2005
It is working fine here with Cubase 14 (Ryzen 5800X, Win 11).
Using: Cubase Pro 15, Reason 13, Tascam US-4x4HR, MODX6, DM12D, LaunchKey 49, Yamaha guitar(Pacifica 612v) and bass (BB234) and some virtual instruments and synths.
-
- KVRist
- 237 posts since 21 Feb, 2012
The latest Opsix Native update 1.3.1 fixed all bugs and non-working functionalities.
I know because I reported the most for Korg and reviewed the fixes.
Doubt they will spend more dev time on optimizing its performance, but now this is finally useable. What I really miss is the flexible modulation system of Wavestate / Modwave / MultiPoly... for whatever reason they stick to the old and limited modulation matrix concept.
I know because I reported the most for Korg and reviewed the fixes.
Doubt they will spend more dev time on optimizing its performance, but now this is finally useable. What I really miss is the flexible modulation system of Wavestate / Modwave / MultiPoly... for whatever reason they stick to the old and limited modulation matrix concept.
-
- KVRAF
- 24404 posts since 7 Jan, 2009 from Croatia
This is because Opsix was the only odd one out developed by Korg Japan, whereas the other three were all based on the same framework developed in Korg USA. So the UI and UX is not consistent unfortunately.
-
- KVRAF
- Topic Starter
- 8675 posts since 24 May, 2002 from Tutukaka, New Zealand
I can categorically state that it didn't - 100% CPU when idling is not a fix. Anyhow, I guess it's good to know it'll work when I get a new laptop maybe end of this year. Can still use the hw version in the meantime. I still don't understand why Korg can't communicate with itself. Korg US managed to fix wavestete native, and Opsix has the same bug. Translators can't cost that much, surely?tripleflows wrote: Sun Jul 27, 2025 1:38 pm The latest Opsix Native update 1.3.1 fixed all bugs and non-working functionalities.
I know because I reported the most for Korg and reviewed the fixes.
-
- KVRist
- 237 posts since 21 Feb, 2012
There seems to be a complete lack of communication between the development teams at Korg USA and Japan.
Although the interface design is linked to the same German company for Modwave and Opsix native, for some reason they accepted completely different quality standards. The US team put in the work to refine it to the extreme, while the Japenes Opsix dev team accepted a version that should not have been accepted. They made some improvements by now, but unfortunately, the modulation handling cannot be mentioned on the same page.
If you have a fast machine, using Opsix Native should not be a problem. I can run dozens of instances on an i7 12700K within a single Cubase project, with 4-5 instances playing smoothly at the same time. The VST3 version does not consume much CPU time when idle, but I do remember when consumption was more of a problem for me with an earlier version. It's still not perfect in this regard, but I think you have to learn to live with it, as it makes up for it with the sound and possibilities of the instrument.
Although the interface design is linked to the same German company for Modwave and Opsix native, for some reason they accepted completely different quality standards. The US team put in the work to refine it to the extreme, while the Japenes Opsix dev team accepted a version that should not have been accepted. They made some improvements by now, but unfortunately, the modulation handling cannot be mentioned on the same page.
If you have a fast machine, using Opsix Native should not be a problem. I can run dozens of instances on an i7 12700K within a single Cubase project, with 4-5 instances playing smoothly at the same time. The VST3 version does not consume much CPU time when idle, but I do remember when consumption was more of a problem for me with an earlier version. It's still not perfect in this regard, but I think you have to learn to live with it, as it makes up for it with the sound and possibilities of the instrument.
-
- KVRAF
- Topic Starter
- 8675 posts since 24 May, 2002 from Tutukaka, New Zealand
I can't learn to live with 100% CPU idling, as it leaves no room for anything else if I'm doing ITB stuff. Ultimately, until I buy a new laptop Opsix is unusable, even more so than it used to be. For me, each Opsix update seems to make it worse. Maybe I should go back to v1.0 and have it only half cripple my DAW instead of fully crippling it. 