Korg Forums

First let me say that Opsix Native does not installed its vst3 to the normal /Common/VST3 folder but in /VstPlugins where it was not discovered by Cubase 12. I had to copy the .vst3 to the correct VST3 folder.

Then I created an instrument track with it, but it does not react to midi notes I send to it ???
I installed a midi monitor and verified that midi notes were correctly arriving to the instrument, tried various midi channels, but no success.

The Wavestate native, used in same conditions correctly plays the incoming midi notes.
Am I the only one ?
Any idea of what I missed ?
Bug ?

I had the same problem re installation location and also had to move it manually, which seems a bit of a "school boy error"

It was working OK for me me in Cantabile (my live host), as was Wavestate native, but happy to check it later in Cubase and report back.

Derek Cook wrote:I had the same problem re installation location and also had to move it manually, which seems a bit of a "school boy error"

It was working OK for me me in Cantabile (my live host), as was Wavestate native, but happy to check it later in Cubase and report back.

Thanks Derek.

Derek Cook wrote: but happy to check it later in Cubase and report back.

Hey Derek, have you checked ?

It finally appears that Opsx native is exclusively listening for midi notes on channel number 1...and that the setting to select a global channel, as built on the 'real' opsix, has been trashed or forgotten from its settings...
For midi PC commands nothing works ok, the vst3 handling of midi PC is not included (only in the doc !!!) as for its brother Wavestate Native...
I hope that Korg will fix this very soon.
I also regret the set list feature which is missing, it was an easy way to change current playing performance, even if its conception was less interesting than the ones on Wavestate and Modewave.

Today appeared the 1.0.3 version, but no fix for vst not handling midi PC to change preset. And no way to select a global channel.
Furthermore reading the doc I see that there are now 128 PC values corresponding to presets, which is very different from what was going on for the real Opsix where presets are organized in several banks of 100 presets (just as the waldorf Pulse2) ?
No information on banks of presets ?

And still impossible to change current preset in VST by sending a PC, I tested every channel.

This part of Opsix Native is a real pity. a nightmare for those like me who believed that it would react to same midi commands as the physical Opsix.

No progress on this ?

Still not fixed with september 2022's 1.0.4 version

And not fixed with 1.0.5 version ...

CSURIEUX wrote:And not fixed with 1.0.5 version ...

The recent Modwave Native and the update on Wavestate Native have fixed the midi PC problem in VST3 with Cubase.
Mainly by using the last Juce library version.
Now waiting for the Opsix native to be fixed.

CSURIEUX wrote: Now waiting for the Opsix native to be fixed.

Still not fixed in 1.0.7 version, feb 2023...

Did anyone contact Korg support about this? As long as they're not aware of the issue (or it didn't get enough 'upvotes' by the number of complaints), it is highly unlikely a dev will be addressing it and have it fixed in some update.

edgraaff wrote:Did anyone contact Korg support about this? As long as they're not aware of the issue (or it didn't get enough 'upvotes' by the number of complaints), it is highly unlikely a dev will be addressing it and have it fixed in some update.

Certainly, many times but no answer.
It is a hell to contact them from France : Korg User asks to contact local dealer and local dealer says he is not in charge of support for software.
I even have an exchange on FB with Dan Philipps, product manager for the two other 'native' and he said Opsix is not depending from Korg US.
There seems to be some communication problem in this comapny.
Total support hell.

It appears Korg has finally fixed the VST3 midi PC handling in version 1.08.
To be tested.