Korg Collection (V2.0 released, GUI update!)

[fmr]

Korg support is aware of the blacklisting issue and also seems they are on holiday in japan.
Golden Week .

I am thinking there will be an update to polysix before i can make heads or tails of it.

Over here, Polysix was blacklisted too, but I went to Plug-In Manager and activated it manually. It was rescanned and everything went OK. It is active now

[djboomstick]

Mine is both working and blacklisted at the same time .

The working part is a new development as of today. Still shows as blacklisted . But also its working


That is to say , up until today , rescanning hasn’t worked .
It lead only to crashes .
Today i did not rescan , i just opened a perviously crashed project that contained a rescanned polysix.
And it work .
Its also still blacklisted in the same project .

[djboomstick]

I found a bug in Wavestation on v 2.0. Was there an update at any point? How would I get it if so?

The bug is when selecting the dance kit from CARD 4, pressing apply and OK. It crashes my DAW.

Otherwise, does this mean I would have to send an email to Korg about it?

Thanks

My wavestation is 2.0.0 , with Cubase 10.5 on windows

I dont have apply or ok button when selecting card 4 , 1 dance kit.

Just highlighting it in the wavestation’s browser applies it to the track . For me with Cubase 10.5 on windows

[yul]

Hi I checked again and it still crashes here. There is an apply and OK button..see screenshot.

Wavestation error snip.jpg

[WatchTheGuitar]

Are you sure that's Wavestation V2.0.0?

Mine looks very different, doesn't have the same presets in Card 4 and none of the patch numbers have that preceding zero.

What version is stated when you go to Utility >>> About WAVESTATION?

never mind - see below

[zvenx]

It isn't a preset he is selecting (I thought so at first till the screen shot), he is selecting a Wave Sequence called Dance Kit.

(That doesn't crash my system though, either Cubase or Standalone)
rsp

[WatchTheGuitar]

It isn't a preset he is selecting (I thought so at first till the screen shot), he is selecting a Wave Sequence called Dance Kit.
rsp

Ah that makes more sense. I've just tried it on my Windows 10 PC running Bitwig 3.1.3 (don't have Cubase as I refuse to deal with hardware dongles in the 21st century) and it seems to work fine - no crashes/issues at all.

[zvenx]

Don't think he is using Cubendo either. Looks more like FL or whatever it is called these days.
Either way, he should report it to Korg.
rsp

[WatchTheGuitar]

I'd never delved into the patch building stuff in Wavestation before because the screens were too small for me to read, but holey moley it looks like I've only used about 5 per cent of what's possible with this soft synth before!

[c_voltage]

Installation \ scan \ loading had been without problems (Win10), but found that the all parameters of the new FX sections (incl. in\out sliders) can't be automated. Except those instruments where this FX section was already before (MonoPoly) - here fx's parameters can be automated as before.
Bad a bit.

M/P was the only plugin in which you could automate FX. Well ok, and ARP Odyssey too.

I suppose since it's the same MDE-X added to MS-20 and Polysix as it is in M/P, maybe they could add automation if enough people request it. Or you could, you know, just load MDE-X separately and automate the hell out of it.

Well, not a big problem ofcourse, but, since they added this anyway, why can't be done the same thing as in MP. But ok.
Though, i'm not exclude that it can be like some issue, because when we turning any fx parameter (in MS20 for example) we see response in form of unique ID in automation info field (i use S1 v4) called like "Parameter 194" etc, but what strange, we don't see this axis in list of parameters.
While in MonoPoly we see it as "Unknown" parameter, which can be captured nevertheless.

Upd But frankly i liked new UIs

In next build will added properly automation for new fx sections parameters (ms20 \ polysix).

[LoveEnigma18]

Great news for FL Studio users: I received the beta versions of MS-20, Polysix and MonoPoly on my ticket regarding the preset recall failure in FL Studio and they are working fine now. I have tested and responded to them.

Hopefully the updates will be available in Korg Software Pass soon.

[fmr]

Great news for FL Studio users: I received the beta versions of MS-20, Polysix and MonoPoly on my ticket regarding the preset recall failure in FL Studio and they are working fine now. I have tested and responded to them.

Hopefully the updates will be available in Korg Software Pass soon.

The past reports together with what happened with Triton at launch, seem to point to the fact that Korg doesn't have (and desperately needs) a good team of beta testers.

[LoveEnigma18]

Great news for FL Studio users: I received the beta versions of MS-20, Polysix and MonoPoly on my ticket regarding the preset recall failure in FL Studio and they are working fine now. I have tested and responded to them.

Hopefully the updates will be available in Korg Software Pass soon.

The past reports together with what happened with Triton at launch, seem to point to the fact that Korg doesn't have (and desperately needs) a good team of beta testers.

Yeah. Somehow the user community and fans of these synths are helping them with unofficial testing. I don't mind helping, especially when a synth is not really usable (preset recall failure makes the synth practically unusable).

I hope things improve later on for them.

[yul]

Hi I checked again and it still crashes here. There is an apply and OK button..see screenshot.

Wavestation error snip.jpg

Yes I was selecting PCM sounds to create a patch.

So I checked on another host and it works fine. What am I supposed to do here? Should I still contact Korg? Thanks,

[zvenx]

Yes..... Let them know...
Plugins sometimes have host specific issues.
rsp