Waldorf Largo 2

[vurt]

You know how I think this happened?

"Hey, let's do a Largo 2, with Apple Sillicon compatibility, a new, resizable GUI, some new formant filters, and some extras!"
"Ok then. Let's call Axel, he did some great synth design for us in the past."
"Hmm... but he's expensive, and, we really can't afford him for the money we take for Largo 2."
"Mmmmh... Ok then. Let the guy who ports the synth do the GUI then. He just takes a few of the GUI elements from Streichfett, and does a new GUI for Largo with that."
"Deal!"

"get intrancer, he'll do it for a bag of chips"

[chk071]

[Examigan]

This should really be a free update for existing owners given the lack of real changes,

If there is a lack of real changes, then you dont need the update and can save your money.

This.

Yep. Tone2's Markus updated several of his plugins for free (not all, but many) and Arturia updated Pigments for free also. I think UVI's Falcon updates have been free lately too.

[jobinho]

This should really be a free update for existing owners given the lack of real changes,

If there is a lack of real changes, then you dont need the update and can save your money.

Frankly sick of people who demand everything for free, i bet you dont work for free, do you.

I would agree with you if this was a version 2 of Largo, but it’s version 1.1 and a poor one at that. Charging 39 dollars for a scalable interface is a joke! How is this even a version 2, like for real, anyone?

At least make it easier to assign modulations… Very low effort release from Waldorf.

[osiris]

I don't like that UI. That looks like a Synthedit job from 2003.

[MRT]

I can't help but think of the Tantra upgrade. Surly, there are good graphic designers out there?

[felis]

I wonder if Waldorf will eventually do some of the stuff from Quantum/Iridium as straight software.

[felis]

for the v1-v2 upgrade: jrrshop - I used ‘forum’

Thanks. I never bought from jrrshop - did you get the license right away?

[Jac459]

for the v1-v2 upgrade: jrrshop - I used ‘forum’

Thanks. I never bought from jrrshop - did you get the license right away?

JRR is sure value.
Never had any issue.

[felis]

[jobinho]

Just look at those comments. Waldorf completely dropped the ball here, what were they thinking.

[aMUSEd]

I was hoping the NKS implementation might compensate for the still crappy browser, but unfortunately they have only converted the Factory patches and forgot to tag any of them.

The KK knobs are linked to none of the synth parameters on my M1 mbp.
I think the NKS was an rush job (read not finished). Maybe 1.01 will fix ?
Also the bank loaded when starting the plugin or using an NKS preset is not the factory bank.

Looks to me like they based the NKS mapping on the VST2 but incorrectly implemented migration so VST2 NKS load in the VST3 but the params don't translate. Also even with the VST2 they work, but with the wrong params. What a mess!

I have completed a 'fix' of sorts for the dreadful NKS implementation for Largo 2. It doesn't fix all the bugs of course, and there are still a couple of params that just won't map, but I have corrected the NKS assignments Waldorf messed up and also improved the layout. The original had all 4 layers mapped, even though no params were actually working or even pointing to the right param. For ease of use I have reduced it to 2 layers as it was crazy having so many user pages and most patches just use one layer, only a few even use 2. Also retagged everything and added previews

https://www.dropbox.com/s/p22n87z485vb7 ... x.zip?dl=0

You could overwrite the factory patches with these, but I expect at some point Waldorf will release an update and it is likely to overwrite anything in the factory location so I recommend putting it in User for now. Hopefully eventually Waldorf will issue their own fixes.

btw they have also not created NKS patches for any of the add-on banks, might get around to doing some of those but it will depend on the ones I like best first.



This is VST3 only - the VST2 and VST3 NKS are not 100% compatible - they seem to have made the originals with the VST2, which is one reason why the NKS params were not working in the VST3, but even in the VST2 they were not working properly because clearly they had added new automation targets but 'forgot' that this had changed all the automation IDs so every single mapped param was pointing to the wrong target. Anyway I made these with the VST3, they will not work properly with the VST2.

[D-Fusion]

Just look at those comments. Waldorf completely dropped the ball here, what were they thinking.

I hope they will fix the gui based on feedback.

[Arcvidean]

What a disaster. I tried to download the trial version and the only thing I can download is the manual pdf.

Me too.

Arcvidean

[chk071]

You may want to read the PDF.