Korg Wavestate and Opsix for Win/Mac

[Biome_Digital]

Trying to program the Wavestate (without manual) feels... overwhelming. (context: I can work with the Wavestation, and most plugins don't require the manual, for me)

Yeah, I had another look at it and found it better using it like a normal sample-based synth without the wave-sequencing part of it. Just didn't like the sound much apart from "stringy pads".

My opinion of the OPSIX has changed though, it's actually pretty capable and the effects are nice too. If they sort the LAG and the price was a little cheaper, I think I would get it.

[StefVR]

Trying to program the Wavestate (without manual) feels... overwhelming. (context: I can work with the Wavestation, and most plugins don't require the manual, for me)

I checked the loopop video on the wavestate and can cant really get the point of the wavestate. It feels like a daw in the daw when using a daw.
Like having a sample wave based synth and then adding some automation lanes into the synth. Why not just use a synth and sequence and automate it in the daw?

Where are the advantages in using it in wavestate?

Is it just the other way of creative workflow or what really is the appeal of it?

[zvenx]

Dan P responded to me on gearspace. Can't speak for the future but it is currently not thought as parrt of Korg Collections.
I had no other choice at this point
And bought it.rsp

Yea I might just have to roll the dice and go for it before the intro price expires.

Did Dan address any of the other concerns at Gearspace?

Honestly, I haven't been following the thread there, he did respond to my two questions..

rsp

[zvenx]

....

The Korg collections are pretty much 'legacy' so maybe (when they bring out Modwave native) there will be a 'contemporary' collection!

As I was driving on my way home just now I thought the same thing... Bring it on I say
I think Korg is the only former Hardware Synth company and truly is on board the software wagon too.
rsp

[D-Fusion]

Wavestate seems to work ok here (Windows 10, Ryzen 7 5800X) with pretty low CPU usage, but I wish there was a way to map the joystick to my controller.

Opsix seems to peg the CPU at around 38 to 40% just by starting it but doesn't seem to change much when you actually play some of the sounds.

However, both sound excellent and are severely hampering my GAS resistance

That doesn't look right.
What daw do you use and do you use energy saving?

I have a amd ryzen 5 5600G and OPSiX uses 12-13% CPU both inn task manager and Studio one v.5 (Windows 10).

Cubase is a different story and OPSiX uses 20-22% CPU and fills 1 Quarter of the audio engine.

[T-CM11]

My opinion of the OPSIX has changed though, it's actually pretty capable and the effects are nice too. If they sort the LAG and the price was a little cheaper, I think I would get it.

You get a lot of (great sounding, imo) synth* for the money - but for me: I already have a lot of synth(s).
For FM specifically, I already have DX7V, Sytrus, Bazille.

[T-CM11]

I checked the loopop video on the wavestate and can cant really get the point of the wavestate. It feels like a daw in the daw when using a daw.
Like having a sample wave based synth and then adding some automation lanes into the synth. Why not just use a synth and sequence and automate it in the daw?

Where are the advantages in using it in wavestate?

Is it just the other way of creative workflow or what really is the appeal of it?

Why don't you try the demo and find out for yourself?

[dune_rave]

i think these new plugins will be part of collection4. they will add something to them then there will be an upgrade path.

[ZincT]

Wavestate seems to work ok here (Windows 10, Ryzen 7 5800X) with pretty low CPU usage, but I wish there was a way to map the joystick to my controller.

Opsix seems to peg the CPU at around 38 to 40% just by starting it but doesn't seem to change much when you actually play some of the sounds.

However, both sound excellent and are severely hampering my GAS resistance

That doesn't look right.
What daw do you use and do you use energy saving?

I have a amd ryzen 5 5600G and OPSiX uses 12-13% CPU both inn task manager and Studio one v.5 (Windows 10).

Cubase is a different story and OPSiX uses 20-22% CPU and fills 1 Quarter of the audio engine.

I'm not using energy saving. That was using the standalone version of OPSiX.

I just tried the plugin and got the following results:

Cakewalk 19-20%
Reaper 40-50%

I'll do some more tests but not all of my DAWs seem to have picked it up so I need to find where the installer put the VST plugin. Maybe it's only an issue with the demo IDK? Then again Wavestate runs fine and is low CPU.

[PAK]

Opsix seems to peg the CPU at around 38 to 40% just by starting it but doesn't seem to change much when you actually play some of the sounds.

That doesn't look right.
What daw do you use and do you use energy saving?

I have a amd ryzen 5 5600G and OPSiX uses 12-13% CPU both inn task manager and Studio one v.5 (Windows 10).

Windows Task Manager reports CPU utilization across all cores. Your Ryzen 5 5600 is a 6 core CPU. This means ~16.7% CPU usage in Task Manager represents the equivalent of an entire core of you CPU, and you're hitting 13%. So it's sucking down almost an entire core. Now check its usage even when playing nothing.

Cubase is a different story and OPSiX uses 20-22% CPU and fills 1 Quarter of the audio engine.

Out of curiosity, which version of Cubase?

[Teksonik]

I checked the loopop video on the wavestate and can cant really get the point of the wavestate. It feels like a daw in the daw when using a daw.
Like having a sample wave based synth and then adding some automation lanes into the synth. Why not just use a synth and sequence and automate it in the daw?
Where are the advantages in using it in wavestate?
Is it just the other way of creative workflow or what really is the appeal of it?

The power of wavesequencing for me is the ability to cycle through a series of full samples (as opposed to single cycle waveforms) to create long evolving pads and soundscapes that can be played from a keyboard just like you'd play any other synth.

Say you start with a Flute or Shaku sample then it morphs into a choir then to a string sample and so on. Then by layering up to 4 wavesequncer lanes you can build some truly incredible sounds. Then of course you can utilize the filters, effects, modulation, etc....

Of course Wavestate is capable of much more but the reason I want to add it my collection is for the wavesequencing.

It's not for everybody but WS is a very powerful form of synthesis.

[D-Fusion]

Wavestate seems to work ok here (Windows 10, Ryzen 7 5800X) with pretty low CPU usage, but I wish there was a way to map the joystick to my controller.

Opsix seems to peg the CPU at around 38 to 40% just by starting it but doesn't seem to change much when you actually play some of the sounds.

However, both sound excellent and are severely hampering my GAS resistance

That doesn't look right.
What daw do you use and do you use energy saving?

I have a amd ryzen 5 5600G and OPSiX uses 12-13% CPU both inn task manager and Studio one v.5 (Windows 10).

Cubase is a different story and OPSiX uses 20-22% CPU and fills 1 Quarter of the audio engine.

I'm not using energy saving. That was using the standalone version of OPSiX.

I just tried the plugin and got the following results:

Cakewalk 19-20%
Reaper 40-50%

I'll do some more tests but not all of my DAWs seem to have picked it up so I need to find where the installer put the VST plugin. Maybe it's only an issue with the demo IDK? Then again Wavestate runs fine and is low CPU.

Yeah. Maybe it is the 20Min Counter that is adding to the Cpu usage.

Never tried the Standalone Version but i did now and it was Drifting between 10-11.6% Cpu and went up to 12% When i started playing some notes.

I See This Release as a very early Alpha version since there are something wrong with it and the gui behaves Weirdly.

It takes a few seconds Before the Gui Start to animate like it needs to boot up before it is ready and it lags like H**l and even slows down my daws Gui.

And the User Experience are all over the place with different kind of problems from different users so they should consider to extend the Release Price until the Products are Stable.

[D-Fusion]

Opsix seems to peg the CPU at around 38 to 40% just by starting it but doesn't seem to change much when you actually play some of the sounds.

That doesn't look right.
What daw do you use and do you use energy saving?

I have a amd ryzen 5 5600G and OPSiX uses 12-13% CPU both inn task manager and Studio one v.5 (Windows 10).

Windows Task Manager reports CPU utilization across all cores. Your Ryzen 5 5600 is a 6 core CPU. This means ~16.7% CPU usage in Task Manager represents the equivalent of an entire core of you CPU, and you're hitting 13%. So it's sucking down almost an entire core. Now check its usage even when playing nothing.

Cubase is a different story and OPSiX uses 20-22% CPU and fills 1 Quarter of the audio engine.

Out of curiosity, which version of Cubase?

When i play nothing it is around 12% And goes to 13.6% While playing (Studio One).
The Version of Cubase is Cubase Elements 12.

[Teksonik]

Honestly, I haven't been following the thread there, he did respond to my two questions..

I'm not a huge fan of Gearspace so let's hope we can coax him back here to address the idle CPU concerns expressed by several people.

I'm pretty much convinced to buy Wavestate but it would be nice if the reports are acknowledged and at least an explanation if not a fix is forthcoming.

[dumbledog]

Yeah. Maybe it is the 20Min Counter that is adding to the Cpu usage.

Doubt it; I see it with the registered version of opsix, but not the demo of wavestate.

I imagine it's just a bug that can be removed in the next patch.