KVR Audio

EvilDragon · Post by **EvilDragon** » Mon Dec 19, 2011 11:35 am

To bypass the use of bit-bridging, of course.

draft14 · Post by **draft14** » Mon Dec 19, 2011 11:40 am

Because jbridge is unstable. but I don't understand why Waldorf edition and not Largo or PPG v3....Waldorf edition is very old and not very good. I don't understand why porting it. Largo and PPG v3 must be 64 bit like a Lector.

ZINO · Post by **ZINO** » Mon Dec 19, 2011 11:41 am

Aiyn wrote:Why do we need 64-bit softsynths again?

Because we are in 2011 (almost 2012)?

Why do we need softsynths at all?

Why do we need a core i3, i5 or i7 when we can have a Motorola 68000?

Why do we need a computer at all when we can have a yamaha 4 track cassete recorder?

EvilDragon · Post by **EvilDragon** » Mon Dec 19, 2011 11:44 am

draft14 wrote:Because jbridge is unstable. but I don't understand why Waldorf edition and not Largo or PPG v3....Waldorf edition is very old and not very good. I don't understand why porting it. Largo and PPG v3 must be 64 bit like a Lector.

No worries - if they started doing 64-bit version of Waldorf Edition, Largo and PPG v3 x64 will come in due time.

About "not very good", I disagree. There's some excellent things to be had with Attack, and PPG v2 can still find a place in the mix with less CPU load than v3.

Ingonator · Post by **Ingonator** » Mon Dec 19, 2011 11:55 am

EvilDragon wrote:
draft14 wrote:Because jbridge is unstable. but I don't understand why Waldorf edition and not Largo or PPG v3....Waldorf edition is very old and not very good. I don't understand why porting it. Largo and PPG v3 must be 64 bit like a Lector.
No worries - if they started doing 64-bit version of Waldorf Edition, Largo and PPG v3 x64 will come in due time.

Exactly my thoughts (like already mentioned...). Now that 4 of 6 Waldorf plugins are 64-bit (Waldorf Edition + Lector) the remaining two should be less problematic IMO.
For me it was a logical step to start with the older plugins after they already released the new Lector plugin with 64-bit (and VST3).

I also agree that the 3 plugins in the Waldorf Edition are great. Even the PPG 2.V could have it's use when you already got PPG 3.V.

Ingo

aMUSEd · Post by **aMUSEd** » Mon Dec 19, 2011 12:00 pm

On the subject of Largo - can it open Komplexor patches? If not can it open the original Waldorf synth banks that Komplexor could?

Ingonator · Post by **Ingonator** » Mon Dec 19, 2011 12:13 pm

aMUSEd wrote:On the subject of Largo - can it open Komplexor patches? If not can it open the original Waldorf synth banks that Komplexor could?

No, it could not.

AFAIK Komplexer by default had only the 2 Q wavetables which coould be reoplaced by loading others which caused problems when using presets which need otherv wavetables. In Largo you got both Q wavetables and a lot more (around 67, 69 in total).

In PPG Wave 3.V you could import banks of the old version and besides differnt sample formats also Waveterm B image files (in .WTB format).

You could get an Evaluation license of Largo here (soft eLicenser possible):
http://www.waldorfmusic.de/en/largo-evaluation.html
latest version (works with Evaluation license too): http://www.waldorfmusic.de/en/downloads-largo.html

Same for PPG Wave 3.V and Lector:
http://www.waldorfmusic.de/en/ppg-3-evaluation.html
http://www.waldorfmusic.de/en/version-102.html

http://www.waldorfmusic.de/en/lector-ev ... cense.html
http://www.waldorfmusic.de/en/lectordownloads.html

------------------------------------------------------------------

There is a version of Sample Robot 4 now which supports the Blofeld XML files:
http://shop.audiosurfer.de/product_info ... anguage=en

A free 3rd party wavetable editor for the Blofeld is available here:
http://lady.rdsor.ro/~kotro/index.php?m=soft

PS:
If you purchase the full version of the Waldorf Edition and the upgrade version of PPG wave 3.V you pay almost the same as with the PPG Wave 3.V full version.

Ingo

aMUSEd · Post by **aMUSEd** » Sat Dec 24, 2011 9:57 pm

I just got this - what are the good soundbanks for it? (more into experimental stuff rather than BnB or dance orientated material)

Ingonator · Post by **Ingonator** » Sun Dec 25, 2011 8:09 am

aMUSEd wrote:I just got this - what are the good soundbanks for it? (more into experimental stuff rather than BnB or dance orientated material)

If you speak about Largo banks are here:
http://www.soundsdivine.com/largo.html
http://www.frantic-records.com/soundsets.htm
http://www.waldorfmusic-shop.de/epages/ ... ries/Largo

free ones (also from me):
http://www.waldorfmusic.de/en/downloads ... ounds.html
http://www.kvraudio.com/banks.php?s=lis ... order=date

There seems to be a new one:
http://www.kvraudio.com/forum/viewtopic.php?t=337346

I am planning doing a Largo bank in 2012. I already started but do other stuff first.

Ingo

Elektrobolt · Post by **Elektrobolt** » Fri Jan 06, 2012 6:25 pm

Ingonator wrote:For me it was a logical step to start with the older plugins after they already released the new Lector plugin with 64-bit (and VST3).

Hi Ingo,

Does that mean that the others (e.g. Largo), when 64-bit, will also be VST3?

Ingonator · Post by **Ingonator** » Fri Jan 06, 2012 9:10 pm

Elektrobolt wrote:
Ingonator wrote:For me it was a logical step to start with the older plugins after they already released the new Lector plugin with 64-bit (and VST3).
Hi Ingo,

Does that mean that the others (e.g. Largo), when 64-bit, will also be VST3?

I'm not sure about all plugins. In Lector it made sense due to the use of sidechaining. In the VST 2 version you got a second plugin ("Lector Carrier") to do sidechaining.

Ingo

ShamanicRitual · Post by **ShamanicRitual** » Tue Jan 10, 2012 12:36 am

They should fix memory leaking bug first. Synth filters kick ass I love to use it in production. But Largo have huge memory bug. It makes smooth production with this synth almost impossible. First of all WTF in this synth GUI must eat 300-500mb memory??? It's rather crazy. Zebra has much more functions, but memory usage below 50 mb.
But when you unload largo, memory don't recover in logic and reaper too.

There are details. http://www.logicprohelp.com/forum/viewt ... 19#p290902

Aiynzahev · Post by **Aiynzahev** » Tue Jan 10, 2012 1:04 am

I have had problems with this synth. It sounds great, its as good or better than any synth out there at what it does, but I have problems with it. Memory issues. Also does anyone use the Arp in it? I find it impossible to use.

ShamanicRitual · Post by **ShamanicRitual** » Tue Jan 10, 2012 2:00 am

I go back from 1.5 to 1.1 version. And it did the trick!! Now 40mb in use per instance and memory recovering is fine. So 500 mb memory is price of Largo 1.5 preset browser interface

Ok then, I will be fine with logic aupreset management.

But oscilator section now weaker. There is no phase control, no brilliance and no limit.

That's fine too.

Aiyn, I try to avoid usage of arpegiators in synths, so did never program arp in Largo.

I agree with you, Largo sound really good. It have some depth right out the box even without internal FXs. FXs are excellent too, I must to say.

P.S.
Ingonator, thanks a lot for your free patches. Largo UI inspire to create own sounds, but it is always good to have some presets for instant play.

Ingonator · Post by **Ingonator** » Tue Jan 10, 2012 8:21 am

ShamanicRitual wrote:I go back from 1.5 to 1.1 version. And it did the trick!! Now 40mb in use per instance and memory recovering is fine. So 500 mb memory is price of Largo 1.5 preset browser interface
Ok then, I will be fine with logic aupreset management.

But oscilator section now weaker. There is no phase control, no brilliance and no limit. That's fine too.

Aiyn, I try to avoid usage of arpegiators in synths, so did never program arp in Largo.
I agree with you, Largo sound really good. It have some depth right out the box even without internal FXs. FXs are excellent too, I must to say.

P.S.
Ingonator, thanks a lot for your free patches. Largo UI inspire to create own sounds, but it is always good to have some presets for instant play.

Hmm,

in the other thread i just mentioned you should try the latest version but here you wrote 1.1. is better which is quite strange.
In the Windows version v1.5.1 the Arp works fine. It's possible that some of my presets will not works correctly with v1.1.
I could confirm a problem with the memory. First instance takes 300 MB and another one additional 230 MB. As i got 4GB RAM i never found it to produce trouble so i didn't recognize it. I'll try to add a report at the bug database.
BTW that problem with the Arpeggiator seems to be a Mac (+ Logic) only problem.

Ingo

Waldorf Largo 64 bit, when?