Korg Modwave Native (VST3)

[zerocrossing]

The keytrack can be set to whatever one wants (within reason) with an user INIT patch.

Yeah, that’s great, but it doesn’t really answer my complaint that the default out of the box is 30%, which isn’t very intuitive.

In UX design, you always have to be mindful of precedent. I once had a boss force me to try alternative symbols to show a player that an NPC had a quest for them. The standard is an exclamation mark, and while I agreed that probably wasn’t a great symbol, it had been done so many times in so many games that to change it now would just be confusing for the player. We explored a bunch of different symbols, and guess what? We used an exclamation mark, because every other symbol gave our play testers trouble. The last thing you want a user to be doing is trying to figure out stuff that should be super straight forward, like key tracking.

[zaphod betamax]

Everyone has their crosses to bear, I guess

[zaphod betamax]

I put him on the same list as Gearspace.
So is variety.

[Big Mouth Strikes Again]

Everyone has their crosses to bear, I guess

Especially ZeroCROSSing.

Case in point: He needs to stop surrounding himself with idiots. This just leads to the delusion that he's some kind of genius. It should be obvious, but talking out of your ass doesn't mean you're a smarty pants.

[Touch The Universe]

This synth rocks the socks! genius

[zaphod betamax]

They did a much better job with the GUI on the software than the hardware editor.
Comparing my Blofeld to the Modwave, I would say they are tied.
Each with strengths and weaknesses, but for me, they are very good together.

[Big Mouth Strikes Again]

They did a much better job with the GUI on the software than the hardware editor.
Comparing my Blofeld to the Modwave, I would say they are tied.
Each with strengths and weaknesses, but for me, they are very good together.

I own a MicroWave and MicroWave II XT hardware synths. I also own several wavetable synth plugins including the Waldorf Largo, KV331 Audio SynthMaster, Tone2 Electra and Icarus, and Serum.

I was excited to check out the modwave Native plugin. It has a powerful architecture and a large set of wavetables and waveforms. My only complaint is that the modwave sounds too much like a Korg PCM synth. You can hear the Triton and Wavestation lineage in many of the patches. And the FX sound like classic Korg effects.

I suppose this isn't a bad thing. It just means that the modwave doesn't sound quite as unique as it might have.

[kaerus]

anyone know of a keyboard with a joystick which work with modwave and also has joystick cv out (for modular)?

[digitalix]

I'll only buy the modwave native if it is possible to assign x-y of the Kaoss to a regular x-y pad external controller in the simple way as one does with all the others. While playing, I hate having to use the computer to move the Kaoss pad.

[felis]

I was going to start a 'Modwave Native Wish List' thread, but I guess I'll just bump this one.

In the short time I've played around with it, I find myself looking for a note off trigger.
Maybe it's possible to use note off as a source, but I haven't figured it out yet.

[danatkorg]

Hi all! We've just updated modwave native to version 1.1.0. If you've enabled automatic checking for updates, a notice will appear the next time you open the plug-in or standalone app.
1.1.0 includes a number of fixes and improvements. There are about 20 items on the list, but most notably:

* A change in ProTools 2023.6 caused a crash when loading the AAX version of the plug-in. In collaboration with Avid, this has now been fixed. The fix should also avoid collisions with other hosts or plugins using Google protobuf.
* Audio quality is now improved when running at 44.1 kHz and 88.2 kHz sample rates. (Thanks to the users who brought this to our attention!)
* Previously, on macOS, if permissions were not correct for the modwave System folder (containing the sound database), modwave native could crash on startup. This has now been fixed.

For the full release notes, see:
https://support.korguser.net/hc/en-us/a ... ease-notes

[EnGee]

Thank you Dan

Wavestate has been updated as well

[goldenanalog]

Joy! Made my weekend, tho late to the party!

This is me:

"Previously, on Windows with Settings > System > Display -> Scale set to over 100%, the window for the standalone application might start with the title bar off of the display. This has now been fixed."

Yep: First thing that I noticed fixed when firing up 1.1.0! Comment: hardware modwave is a big-league synth in an inexpensive box - a rack version would be legit; so would a full-sized SE edition with 5 octaves, etc. fingered by a large intuitive touch screen!

[sacer]

I have demoed it on both Windows and Mac. In Windows, horrible performance especially when changing presets! Ableton Live behaves strange! The CPU jumps to 4000+% then goes down gradually when changing presets! In Cubase almost the same!

On Mac (Logic and Live) it barely reaches 12% CPU!! Changing the presets is so smooth. Great performance on Mac M1! I'm not sure of buying it because this is about NZ$ 234 which is too much especially that I've got several great Wavetable synths. If it is $99, I would consider buying it.

Ableton Live is slow with VST3 program changes, unfortunately - and not just with our products. See the FAQ article below. There will be a CPU hit when a new sound is selected, as it generates the wavetables, but that should go away quickly - and shouldn't be "4000%!" I'd be curious to know what hardware you're using.

https://support.korguser.net/hc/en-us/a ... leton-Live

Yes also avenger and rapid have extreme long preset loading times. On Korg Modewave also see all parameters changing on my push. It’s the same behaviour than avenger and rapid. Only with vst3.
Do you know if Ableton is going to eliminate this behaviour?
There is also an other strange behaviour, when I want to modify x,y pad, the both cutoffs and the 4 macro knobs on my push3, after a preset change the 8 values disappear from push3 but I still see them diplayed midi configure panel. Maybe it has something to do with the 4 macro parameters, because they change their name for every preset.
On other synths that change also the name, I don’t get the same issue. Also wavestate and opsix don’t share this behaviour

[danatkorg]

Yes also avenger and rapid have extreme long preset loading times. On Korg Modewave also see all parameters changing on my push. It’s the same behaviour than avenger and rapid. Only with vst3.
Do you know if Ableton is going to eliminate this behaviour?

We've discussed it with a developer at Ableton, who was aware of the issue. Anything more is a question for Ableton - please let them know!

There is also an other strange behaviour, when I want to modify x,y pad, the both cutoffs and the 4 macro knobs on my push3, after a preset change the 8 values disappear from push3 but I still see them diplayed midi configure panel. Maybe it has something to do with the 4 macro parameters, because they change their name for every preset.
On other synths that change also the name, I don’t get the same issue. Also wavestate and opsix don’t share this behaviour

I don't have a Push here, so I can't test this. Have you contacted Ableton?