KVR Audio

Everglide · Post by **Everglide** » Mon Jun 15, 2015 8:14 am

DrGonzo wrote:
aMUSEd wrote:
masterhiggins wrote:
Everglide wrote:
aMUSEd wrote:If you guys like Largo and bass get Plughugger's Large Bass Expander - one of my favourite Largo banks and some of the best bass patches I've heard

http://www.kvraudio.com/news/plughugger ... argo_12436
Plughugger's Large Bass Expander can be found here:
http://damagedbits.com
Not seeing it. Can you double-check?
That's weird, have they pulled it, it was one of their best soundsets?
Wow! Talk about a blast from the past

Large Bass Expander was the first soundset I made under my own brand. Not bad, but a bit all over the place. I hade a firesale of it about 1-2 years ago before I took it away. Nave looks incredibly cool - but I am so sucked-into-another-dimension with Omnisphere 2 that I barely have time for anything else.

/C

why not make it free

Apostate · Post by **Apostate** » Mon Jun 15, 2015 10:03 am

Everglide wrote:. Nave looks incredibly cool - but I am so sucked-into-another-dimension with Omnisphere 2 that I barely have time for anything else.

/C

Nave, Alchemy, and Iris 2 are the reason I haven't bothered with Omnisphere. Not sure about it working vice versa, but from what I've read about Omnisphere, it's a great one stop thing for soundtracks. The above first three get so much done for me in that realm I feel no lack.

Everglide · Post by **Everglide** » Mon Feb 20, 2017 9:38 am

Is anyone else having trouble with DAW automation with parts, 2, 3 and 4 in Largo v1.6?

Largo v1.5 doesn't have the same issues for me, it works as you'd expect. I can map and automate any part successfully.

Incase anyone asks I'm using Mac Sierra with Bitwig studio

jobinho · Post by **jobinho** » Mon Feb 20, 2017 11:01 am

If anyone's interested I'm selling my Largo license here:

viewtopic.php?f=43&t=479456&p=6706349#p6706349

chk071 · Post by **chk071** » Mon Feb 20, 2017 11:13 am

Everglide wrote:Is anyone else having trouble with DAW automation with parts, 2, 3 and 4 in Largo v1.6?

Largo v1.5 doesn't have the same issues for me, it works as you'd expect. I can map and automate any part successfully.

Incase anyone asks I'm using Mac Sierra with Bitwig studio

FWIW, there's a version 1.7,at least on Windows, but, as far as I know, that one only changes the copy protection.

Everglide · Post by **Everglide** » Mon Feb 20, 2017 11:46 am

Thanks for the heads up, I'll try it out when I can!

Has anyone notice this small anomaly;

1. add Detune to your patch
2. set Detune back to 0 and adjust the Spread and Voices to taste
3. save the patch
4. open the project and the patch loses the Stereo Spread, its now forced Mono

Before you say you need to add at least 001 Detune to keep the width.
What if you don't want the Detune movement?
What if I'd like to keep the static voice spread for sound design?

Surely Waldorf could add an option like Stereo or Static button next the Mono.

c_voltage · Post by **c_voltage** » Sun Apr 02, 2017 2:50 am

Everglide wrote:Thanks for the heads up, I'll try it out when I can!

Has anyone notice this small anomaly;

1. add Detune to your patch
2. set Detune back to 0 and adjust the Spread and Voices to taste
3. save the patch
4. open the project and the patch loses the Stereo Spread, its now forced Mono

Before you say you need to add at least 001 Detune to keep the width.
What if you don't want the Detune movement?
What if I'd like to keep the static voice spread for sound design?

Surely Waldorf could add an option like Stereo or Static button next the Mono.

Thank for tip. I tried Largo demo now, and also reproduce this. Well, i believe it's not should be, ie a little bug. Also, for example if you re-load your preset inside Largo (not daw project) then even in zero detune, the spread still sound properly - what confirm thats it bug.

In general, i slightly surprized how was optimize Largo since older vrersion which i tried long time ago, it's a much more usable for now, UI response and it seems main cpu usage now better.
Some question about latest version - i see installer called as 1.17, but in about screen inside plugin it v1.70, maybe some mistake ? (What really latest Largo version today?)

Dakl · Post by **Dakl** » Mon Apr 03, 2017 12:08 am

aMUSEd wrote:
chk071 wrote:It puzzles me actually that Massive is mainly abused as such a dubstep or EDM preset slut.
Not really, sure there are a lot of throwaway banks but most of them are variations on the same few sound and therefore ignorable; leaving them to one side there are a lot of banks that really stretch Massive's capabilities and always has been. I think in terms of sound design some of the best banks available for any synth are now out for Massive (up there with some of the best Alchemy and Zebra banks).

Can you name names?

chk071 · Post by **chk071** » Mon Apr 03, 2017 12:11 am

c_voltage wrote:
Some question about latest version - i see installer called as 1.17, but in about screen inside plugin it v1.70, maybe some mistake ? (What really latest Largo version today?)

Version 1.70 is correct.

c_voltage · Post by **c_voltage** » Mon Apr 03, 2017 12:59 am

chk071 wrote:
c_voltage wrote:
Some question about latest version - i see installer called as 1.17, but in about screen inside plugin it v1.70, maybe some mistake ? (What really latest Largo version today?)
Version 1.70 is correct.

Thank, then ok.

Waldorf Largo Appreciation