Waldorf Largo 2

[Jac459]

The funny thing is, now that I upgraded I get a message on the Waldorf website that says that I don’t own Largo 1. Luckily I still have the JRR Shop receipt.

I just checked my account, and it shows both Largo (1) and Largo 2 Upgrade in the License Keys section. You should contact them and let them know. Hopefully they will sort you out.

Update: Waldorf’s customer service says, “no record of me owning Largo 1,” despite the fact that I forwarded the receipt to them. What a sh!tshow Waldorf is. What do I have to do? Mail them my elicenser?

Mmm it really feels that they are taking the software business very seriously ...

At least your experience is useful to help other decide...

[Doggo]

Largo has a sound that some associate with cold. But much warmth can be extracted if you know what you are doing.

[hcv242]

Using in Logic and when I edit a preset it automatically saves the changes. Even after I click out of the bank and back again. Anyone else have this problem or know what could be wrong? Waldorf says it's not the program, but must be something in my DAW.

It is like that by design. All synths that use FXB bank presets work like that (sylenth and many others come to mind). You are editing the whole bank at the same time and every change affects the bank. Only way to go back to original preset after making changes is to reload the FXB bank file or reload the synth.

[hcv242]

It's now been about 4 months since they said they would fix the issues.

What are the current issues ?

[jrnyfn]

Using in Logic and when I edit a preset it automatically saves the changes. Even after I click out of the bank and back again. Anyone else have this problem or know what could be wrong? Waldorf says it's not the program, but must be something in my DAW.

It is like that by design. All synths that use FXB bank presets work like that (sylenth and many others come to mind). You are editing the whole bank at the same time and every change affects the bank. Only way to go back to original preset after making changes is to reload the FXB bank file or reload the synth.

Ah, thank you so much. Odd that Waldorf said this doesn't happen, though. Not that I'm doubting you as that's exactly what happens as I reloaded the bank.

[zerocrossing]

The funny thing is, now that I upgraded I get a message on the Waldorf website that says that I don’t own Largo 1. Luckily I still have the JRR Shop receipt.

I just checked my account, and it shows both Largo (1) and Largo 2 Upgrade in the License Keys section. You should contact them and let them know. Hopefully they will sort you out.

Update: Waldorf’s customer service says, “no record of me owning Largo 1,” despite the fact that I forwarded the receipt to them. What a sh!tshow Waldorf is. What do I have to do? Mail them my elicenser?

wtf? that is outrageous. i really hate to hear this because i really like waldorf products. but this cannot be right. how can they justify that you have a valid UPGRADE license but you don't have a valid license that you upgraded FROM??????

It took 4 days of back-and-forth emails including a video of me opening my eLicenser app, showing the Largo 1 license, starting Bitwig and loading Largo 1, but they finally conceded to putting my Largo 1 license in my account so I can use the v2 update.

[JamminFool]

It took 4 days of back-and-forth emails including a video of me opening my eLicenser app, showing the Largo 1 license, starting Bitwig and loading Largo 1, but they finally conceded to putting my Largo 1 license in my account so I can use the v2 update.

glad they got you sorted.

[felis]

....What are the current issues ?

One of them for me is - in the older vst2 version, release velocity works fine. When they updated it to vst3, they broke it. I tried the new version and it's still broken. So if I use it at all now, I only use the old vst2 version.

[hcv242]

....What are the current issues ?

One of them for me is - in the older vst2 version, release velocity works fine. When they updated it to vst3, they broke it. I tried the new version and it's still broken. So if I use it at all now, I only use the old vst2 version.

I always use vst2 version of plugs, since ableton live has a problem with program change and VST3 (it simply does not work). Also i have seen people who code plugins sayng that VST3 is a half baked format. Also, I don't see sequencers dropping vst 2.4 support for the next 30 years. Is there any reason why i should use VST3 ? please tell me about it.

[felis]

... pIs there any reason why i should use VST3 ? please tell me about it.

Of the hundreds of vsti's I've got, about 98% are vst3 with no problems.
I find it easier to manage and keep track of them too. YMMV

[digitalboytn]

... pIs there any reason why i should use VST3 ? please tell me about it.

I find it easier to manage and keep track of them too. YMMV

This....

One folder for all presets that can be backed up in a heartbeat...

Simple,efficient and organised....

Perfect

[felis]

Got an email from JRR Shop that Largo 2 update is on sale for $22.
I tried the demo when they first announced Largo 2 and didn't get it because I found some stuff broken.
I thought I'd try the demo again and see if they fixed it yet. Demo says 'expired'.

[hurricaneaudiolab]

It's still at V1. Last week they said they "are still working on it" when I asked for an update on the issues I reported back in February:

Issues

1. GUI size will not stick when opening a new instance. Always defaults to original size.
2. Saving a patch as Default in Logic's plugin browser, always resets the filter envelope's release to zero and it doesn't save the GUI size.
3. Still a little laggy when switching banks and clicking on that first preset. I know you "reduced" lag, but how about getting rid of it altogether? Like in the first Largo.
4. AU presets won't load from Logic's library browser or the internal plugin browser.
5. The worst one though is after saving a project, opening it resets all the filter envelope releases to ZERO across every Largo instance.

Their response to these issues (again, back in February):

"we had another meeting yesterday and among others we went thru the points you sent us.
The issues can be confirmed and will be solved in the next update.
I'll let you know when the update will be available."
-Waldorf

[dayjob]

It's still at V1. Last week they said they "are still working on it" when I asked for an update on the issues I reported back in February:

Issues

1. GUI size will not stick when opening a new instance. Always defaults to original size.
2. Saving a patch as Default in Logic's plugin browser, always resets the filter envelope's release to zero and it doesn't save the GUI size.
3. Still a little laggy when switching banks and clicking on that first preset. I know you "reduced" lag, but how about getting rid of it altogether? Like in the first Largo.
4. AU presets won't load from Logic's library browser or the internal plugin browser.
5. The worst one though is after saving a project, opening it resets all the filter envelope releases to ZERO across every Largo instance.

Their response to these issues (again, back in February):

"we had another meeting yesterday and among others we went thru the points you sent us.
The issues can be confirmed and will be solved in the next update.
I'll let you know when the update will be available."
-Waldorf

So next summer at best

[electro]

Any sign of a PPG 3.V update?