KVR Audio

D-Fusion · Post by **D-Fusion** » Sat Aug 20, 2016 4:15 pm

I hope we will see a blofeld 2 in the near future

D-Fusion · Post by **D-Fusion** » Sun Sep 04, 2016 3:37 pm

Did some more testing on my FM Bass patch and discovered that i had to set the phase to 180 on oscillator 1 +2 and enable bass boost then they where more correct in tone without Largo sounding muffled or boomy.

Weird thing is that i thought the Blofeld sounded more in your face until i discovered this and now i Prefer the Largo version instead

The Largo sounded more like the 90's Euro Bass i was aiming at creating.
They still have some small character differences so i would say they are a good team together

chk071 · Post by **chk071** » Sun Sep 04, 2016 7:17 pm

Good to hear.

Don't hesitate to post some sound examples, if you feel like it. Always nice to hear something from my favorite synth.

Doc Brown · Post by **Doc Brown** » Sun Sep 04, 2016 7:49 pm

I bought Largo during the nks sale and regret it. It has a show stopper issue of not remembering the state when reopening a saved project in the latest version of Reaper(latest version of Largo) . It's a longstanding issue which apparently was never addressed. To make things worse emails to Waldorf go completely ignored, I guess they figure you already bought their product so shove off.

chk071 · Post by **chk071** » Sun Sep 04, 2016 7:56 pm

Does Reaper support VST3? If so, you could try to load the VST3 of Largo, if you have that installed, and see if that loads the state properly. It works fine here (VST2) under Cubase and Studio One 2 though.

Ingonator · Post by **Ingonator** » Sun Sep 04, 2016 8:04 pm

Doc Brown wrote:I bought Largo during the nks sale and regret it. It has a show stopper issue of not remembering the state when reopening a saved project in the latest version of Reaper(latest version of Largo) . It's a longstanding issue which apparently was never addressed. To make things worse emails to Waldorf go completely ignored, I guess they figure you already bought their product so shove off.

More details would be helpful like:

- Largo version
- OS and version
- Reaper version used
- VST2 or VST3 plugin?
- used inside Komplete Kontrol plugin (= nks support) or with the "normal" plugin outside Komplete Kontrol?

FWIW i am a tester at Waldorf and got 6 hosts for testing (Live 9, Cubase 8.5, Studio One 3, Bitwig Studio, Pro Tools 12.5 and Reaper 4.78). My OS is Windows 10 64-bit.

FWIW saving and loading presets with a project seems to work with Live 9 and Cubase 8.5 which i just tested again (Largo VST2 v1.6.0). Also seems to work with the VT 2 plugin in Reaper 4.78 here.

Recently i had rarely used Reaper for testing and also did not update to v5 as first they ask for the full price to upgrade from v4 to v5 and second those other hosts i got are more than enough for me.

electro · Post by **electro** » Sun Sep 04, 2016 8:59 pm

I suspect a Nebula lineamp program could make any sonic differences between Largo and Blofield negligible.

Doc Brown · Post by **Doc Brown** » Sun Sep 04, 2016 9:29 pm

chk071 wrote:Does Reaper support VST3? If so, you could try to load the VST3 of Largo, if you have that installed, and see if that loads the state properly. It works fine here (VST2) under Cubase and Studio One 2 though.

Fantastic!

I didn't even think to try vst3 and based on some initial testing it seems to be recalling the plugin state correctly upon close and reopen of the project. Awesome. I'll need to do more testing but so far it looks promising.

Allow me to buy you a virtual pint.

Doc Brown · Post by **Doc Brown** » Sun Sep 04, 2016 9:35 pm

Ingonator wrote:
Doc Brown wrote:I bought Largo during the nks sale and regret it. It has a show stopper issue of not remembering the state when reopening a saved project in the latest version of Reaper(latest version of Largo) . It's a longstanding issue which apparently was never addressed. To make things worse emails to Waldorf go completely ignored, I guess they figure you already bought their product so shove off.
More details would be helpful like:

- Largo version Largo 1.6.0
- OS and versionWindows 7 x64 (latest build)
- Reaper version usedReaper x64 V5.23 (latest)
- VST2 or VST3 plugin?tried vst2 but just tried vst3 and it seems to work?!
- used inside Komplete Kontrol plugin (= nks support) or with the "normal" plugin outside Komplete Kontrol?
Normal plugin

FWIW i am a tester at Waldorf and got 6 hosts for testing (Live 9, Cubase 8.5, Studio One 3, Bitwig Studio, Pro Tools 12.5 and Reaper 4.78). My OS is Windows 10 64-bit.

FWIW saving and loading presets with a project seems to work with Live 9 and Cubase 8.5 which i just tested again (Largo VST2 v1.6.0). Also seems to work with the VT 2 plugin in Reaper 4.78 here.

Recently i had rarely used Reaper for testing and also did not update to v5 as first they ask for the full price to upgrade from v4 to v5 and second those other hosts i got are more than enough for me.

Thanks Ingo I will report back with further test results. It seems to be working with vst3 but I was having the same state saving issue with the ppg v3 also. I'll check to see if there is a vst3 version of that and give that a go.

Thanks again for trying to help. That's more than Waldorf did.

chk071 · Post by **chk071** » Sun Sep 04, 2016 11:42 pm

Doc Brown wrote:
chk071 wrote:Does Reaper support VST3? If so, you could try to load the VST3 of Largo, if you have that installed, and see if that loads the state properly. It works fine here (VST2) under Cubase and Studio One 2 though.
Fantastic!

I didn't even think to try vst3 and based on some initial testing it seems to be recalling the plugin state correctly upon close and reopen of the project. Awesome. I'll need to do more testing but so far it looks promising.

Allow me to buy you a virtual pint.

Thanks.

Glad it worked for you. Usually VST3's are more buggy in my experience, but in this case, it seems there's one bug less.

EnGee · Post by **EnGee** » Mon Sep 05, 2016 1:02 am

Largo is a wonderful synth

I have installed the VST3 (thanks for mentioning it) and it seems to work fine in Cubase Elements 8. Anyway, I did fast one preset with it, which made me order the Steinberg key (NZ$69 with shipping

). Now, if only I can make Retrologue and Padshop pro working without crashing

Snif! Resistance is useless, the devil is stronger than me

jobinho · Post by **jobinho** » Mon Sep 05, 2016 1:25 am

Does anyone know if it's possible to transfer a Largo licence via elicenser without a dongle?

Thanks

EnGee · Post by **EnGee** » Mon Sep 05, 2016 1:36 am

jobinho wrote:Does anyone know if it's possible to transfer a Largo licence via elicenser without a dongle?

Thanks

No you can't. Neither for another computer nor to another user (I wish someone tells me that I'm wrong!).

chk071 · Post by **chk071** » Mon Sep 05, 2016 1:37 am

You're right. See also here: http://www.waldorf-music.info/en/kunena ... next-owner

Ingonator · Post by **Ingonator** » Mon Sep 05, 2016 7:55 am

Doc Brown wrote:
Ingonator wrote:
Doc Brown wrote:I bought Largo during the nks sale and regret it. It has a show stopper issue of not remembering the state when reopening a saved project in the latest version of Reaper(latest version of Largo) . It's a longstanding issue which apparently was never addressed. To make things worse emails to Waldorf go completely ignored, I guess they figure you already bought their product so shove off.
More details would be helpful like:

- Largo version Largo 1.6.0
- OS and versionWindows 7 x64 (latest build)
- Reaper version usedReaper x64 V5.23 (latest)
- VST2 or VST3 plugin?tried vst2 but just tried vst3 and it seems to work?!
- used inside Komplete Kontrol plugin (= nks support) or with the "normal" plugin outside Komplete Kontrol?
Normal plugin

FWIW i am a tester at Waldorf and got 6 hosts for testing (Live 9, Cubase 8.5, Studio One 3, Bitwig Studio, Pro Tools 12.5 and Reaper 4.78). My OS is Windows 10 64-bit.

FWIW saving and loading presets with a project seems to work with Live 9 and Cubase 8.5 which i just tested again (Largo VST2 v1.6.0). Also seems to work with the VT 2 plugin in Reaper 4.78 here.

Recently i had rarely used Reaper for testing and also did not update to v5 as first they ask for the full price to upgrade from v4 to v5 and second those other hosts i got are more than enough for me.

Thanks Ingo I will report back with further test results. It seems to be working with vst3 but I was having the same state saving issue with the ppg v3 also. I'll check to see if there is a vst3 version of that and give that a go.

Thanks again for trying to help. That's more than Waldorf did.

Hi,

actually i am a long time tester (+ sound designer) for them and was also working for them from time to time for certain projects (last time at the NKS updates where also my own 64 patches bank was finally included with PPG Wave 2.V from Waldorf Edition 2). I got multiple ways to contact Waldorf if really necessary.

Back to your reported problem:
So the main differnces to my setup seem to be Reaper v5 instaed of v4 and Windows 7 instead of Windows 10. MY guess is that it could be somehow based on Reaper v5. I could try teh demo of v5 again but not sure if it allows saving projects.
Fine to hear that the VST 3 works for you but at my setup (Reaper v4.78, Windows 10 64-bit) it also works with the VST2. As already mentioend this also works properly in Live 9 and Cubase 8.5.

For testing/using the VST3 i got other options like e.g. Cubase 8.5 or Studio One 3 and also Pro Tools 12.5 for the AAX plugin (no Mac/OSX here so no AU testing here...).

Largo vs Blofeld