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

[Ingonator]

As a fan of the Wavestation who owns both the hardware and the plugin since more than 10 years the new GUI update for the plugin is simply awesome. Almsost feels like a new instrument with that.

[Ingonator]

how hard can it be to include1 init preset in every synth...

You mean like this one ?

Korg 042120.png

And in Wavestation?

There is an INIT for All Rams but to be fair the individual patches aren't really INIT.


Korg 042220.png

The Init patches in those 3 RAM banks use a single oscillator with a waveform called "InitWav" which is a wave sequence with 4 steps (with 4 EP samples) and not a single waveform and/or sample.

[PatchAdamz]

As a fan of the Wavestation who owns both the hardware and the plugin since more than 10 years the new GUI update for the plugin is simply awesome. Almsost feels like a new instrument with that.

Yes, also working with the hardware for years and now, can clearly see the software (finally).
Now they should release some of the other great Roland synths..

[kmonkey]

Is it just me or demo limitation or what?

Wavestation - Studio one. First load fine. Adding second instance - boom crash. There is some message about graphic issues.
Monopoly - Reason 11 - not recalling presets. I select some preset. Save session. Reopen it. Preset is back to default.

It's interesting because M1 behave normally. Works fine in both host, preset recalled, no GUI issues.

Did anyone had weird glitches?

Other then that this is friggin awesome. Wavestation (when it's working) and M1 with huge screens are awesome to work with and there's galaxy of sound there..

[EvilDragon]

No crash with Wavestation in S1 doing what you describe. Loaded a dozen instances and all good. Ditto chosen preset in Mono/Poly recalls just fine in Reason 11 over here...

[kmonkey]

No crash with Wavestation in S1 doing what you describe. Loaded a dozen instances and all good. Ditto chosen preset in Mono/Poly recalls just fine in Reason 11 over here...

Consider yourself lucky then.

I just found more of similar issues posted by other user in another host.

viewtopic.php?p=7737569#p7737569

Also pretty sure yesterday i saw another user experiencing 100% same issue with Wavestation and S1. But that was most likely on Gearslutz and now i can't find link.

My point is - there are some problems and it's not user error. I am using VSTs for 15 years. Everything is working normally with other VSTs and i have more then 100 synths (not using all of them of course but that's not the point).

Here is what i do.

1. Run Reason 11.
2. Load Polysix.
3. Load patch called Hit/Chord - m9 Deep Chord - save session. Close Reason.
4. Open Reason. Polysix sound is not m9 Deep chord. Sound is different and preset name is called some weird number.

Also i just noticed that in Monopoly if tooltips are enabled then GUI is kinda changing when you move mouse over it. It's hard to describe it's not that GUI is wrecked just it changes subtly. Like moving few pixels up or down or left-right. If i disable tooltips GUI is fine.


EDIT: i am thinking about that idea: Perhaps Korg synths have some init thing fired up on MIDI and some of my DAWs are sending midi messages or something on start. Does anyone know maybe that's the case with recalling issue?

[beltrom]

Here is what i do.

1. Run Reason 11.
2. Load Polysix.
3. Load patch called Hit/Chord - m9 Deep Chord - save session. Close Reason.
4. Open Reason. Polysix sound is not m9 Deep chord. Sound is different and preset name is called some weird number.

I can repeat it in Reason Intro 11, it seems to reset to first preset ("00100001").
But it doesn't behave like this in Cubase Pro 10.5.

[mholloway]

I bought Odyssey and it's absolutely awesome

I agree (and I've had it for a while). I honestly don't have any other synths that sound quite like it. It has this gnarly unique character. And things go really wild when you turn on the Unison mode, the sound is enormous. My favorite trick with the Odyssey is having the S&H triggered by keyboard rather than LFO, so each press of a key triggers the next 'sample' for modulation. Some really dynamic results come from that -- more interesting and less 'rote' than standard LFO-based cyclic modulations.

The addition of the Sequencer really pushes it over the top.

The only thing that continues to mystify me about it is why the 2nd and 3rd filters are so drastically quieter than the first.

-M

[LoveEnigma18]

Is Odyssey GUI scalable like others?

[EvilDragon]

Is Odyssey GUI scalable like others?

No.

Also i just noticed that in Monopoly if tooltips are enabled then GUI is kinda changing when you move mouse over it. It's hard to describe it's not that GUI is wrecked just it changes subtly. Like moving few pixels up or down or left-right. If i disable tooltips GUI is fine

I find similar things happening in MS-20 and Mono/Poly, but not tooltip related. In MS-20 it's just moving cables around, in M/P it's clicking on buttons to the right of the display - and this happens regardless of tooltips being enabled or not.

https://imgur.com/a/odyP6ge

1. Run Reason 11.
2. Load Polysix.
3. Load patch called Hit/Chord - m9 Deep Chord - save session. Close Reason.
4. Open Reason. Polysix sound is not m9 Deep chord. Sound is different and preset name is called some weird number.

OK this one with Polysix I can confirm in R11. But not in Reaper or S1 or Live or Maschine or FL20.

Still can't get M/P to do the same thing in Reason.

[EvilDragon]

The only thing that continues to mystify me about it is why the 2nd and 3rd filters are so drastically quieter than the first.

Let me demistify it for you. Rev 1 filter is a 2-pole biquad (close relative to state variable filter) that doesn't exhibit gain reduction with increased resonance like many 4-pole ladder designs do. Rev 2 and 3 filters are 4-pole ladders and they do exhibit that specific property. So, the plugin is emulating things correctly!

[ramseysounds]

Here is what i do.

1. Run Reason 11.
2. Load Polysix.
3. Load patch called Hit/Chord - m9 Deep Chord - save session. Close Reason.
4. Open Reason. Polysix sound is not m9 Deep chord. Sound is different and preset name is called some weird number.

I can repeat it in Reason Intro 11, it seems to reset to first preset ("00100001").
But it doesn't behave like this in Cubase Pro 10.5.

Can confirm that Cubase Pro 10.5 recalls patch as saved when reopening project. I'm still getting the issue of patches going to init when loading old projects containing Legacy synths.

[kmonkey]

Here is what i do.

1. Run Reason 11.
2. Load Polysix.
3. Load patch called Hit/Chord - m9 Deep Chord - save session. Close Reason.
4. Open Reason. Polysix sound is not m9 Deep chord. Sound is different and preset name is called some weird number.

I can repeat it in Reason Intro 11, it seems to reset to first preset ("00100001").
But it doesn't behave like this in Cubase Pro 10.5.

Awesome thanks so much man i was starting to think i am going crazy.

EvilDragon can you message developers about it ? (assuming you are connected with them )

Note: same is happening with Monopoly.

Also something is happening with Wavestation in Reason and S1 i am telling you. It may be computer related since it's not happening to everyone but adding Wavestation sometimes(randomly) to Reson or S1 - causes immediate application crash and there is some weird message about graphic.

[robotmonkey]

I'm still getting the issue of patches going to init when loading old projects containing Legacy synths.

And then people complaining not having init patches. There's your way.

[zvenx]

I'm still getting the issue of patches going to init when loading old projects containing Legacy synths.

And then people complaining not having init patches. There's your way.

Lol.

I am hoping people are reporting their bugs to Korg. They can't fix it if they don't know about it, and yes not because it happens 100% on your system means it happens 100% on every other system.
rsp