Largo 1.10 update available

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
RELATED
PRODUCTS

Post

rob_lee wrote:
Ingonator wrote:
rob_lee wrote:i did read the posts..there's nothing wrong with my licence as it's still there on the dongle and in the device tree..
largo just does not show up in sonar but the dll is still there...
nevermind i'll sort it out somehow...

rob
Maybe you can try to install the LCC from the eLicenser page like i pointed out above. It worked in my case.
Largo is now working nice :D

great new layout..very nice

rob
So what did you do for making it work? Would help others maybe.
Ingo Weidner
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1

Post

Worked fine in the Mac - shows as 1.1.0 in the GUI as well. eLicenser just launched the control center and showed everything okay.

I have to say, this is a great update :D :D It would be nice to have additional 'copy' and 'paste' buttons in the 'part' section, to save having to use the edit menu at the top (took me a while to find it) and make copying parts/layers very easy.

I love the new setup for multi-part though. 8)

Post

hi

1 - click on the installer and go through the proccess accept agreement etc
2 - find the largo dll file in your plugins and copy/paste it to your desktop
3 - delete the largo dll file still in the vst plugins folder
4 - drag the largo dll back from your desktop into your chose vst folder
5 - start up your sequencer
6 - scan all vst plugins
7 - the new largo now shows up :) (in sonar 8pe it does anyways)

ps

i did'nt even remove the dongle or anything as it worked no problem above doing the above on the list

rob :)

Post

I received my copy of Largo yesterday, nice to see an update for it that improves the reverb.

I was actually going to make a post today of my impressions and note some of the bad things about Largo, especially the FX section. I was actually shocked when I first tried it yesterday, to find such bad sounding FX :(

Anyway, hoping this update improves that..Having installer troubles now..

Post

What, a new version of the manual and still no warnings to keep Largo away from small children, animals, and mother-in-laws! :lol: :wink:
------------------------------------------
Gribs

Post

Ok, the reverb has been improved a LOT! Sounds very nice now, where before it sounded very cheap and metallic no matter what you did with the settings.

A small improvement to the delay, but I was hoping the would give us separate controls for L and R delay times. Instead we have new modulation controls on the delay, but I just can't seem to dial in a nice subtle modulation on the delay with it, any settings I use just sound awful.

Oh. According to the readme file with the update, there's a demo version available now.

Post

A new version of the zip file from version 1.1.0 for windows is published today. This fixes the incorrect version number shown on the Largo GUI.

I my case the installation of the new file just went fine. No dongle/LCC problem this time. :D :D


Remaining fixes for the future:

1.) improving the CPU load

2.) implementing a PPG filter (maybe just for me...)
Ingo Weidner
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1

Post

Ingonator wrote: 1.) improving the CPU load
Usually making CPU loading improvements by lowering sound quality in some parts of the synth. Isn't it? Then I'm against this.

Post

Igro wrote:
Ingonator wrote: 1.) improving the CPU load
Usually making CPU loading improvements by lowering sound quality in some parts of the synth. Isn't it? Then I'm against this.
Since i use a Quad Core CPU it's not so much important for me but maybe for others !!
Ingo Weidner
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1

Post

Ingonator wrote:
Igro wrote:
Ingonator wrote: 1.) improving the CPU load
Usually making CPU loading improvements by lowering sound quality in some parts of the synth. Isn't it? Then I'm against this.
Since i use a Quad Core CPU it's not so much important for me but maybe for others !!
i have a quad core but even playing a chord chews up all my cpu in sonar and the audio engine stops :( i can't even design pad sounds because opening up the amp env release espescially needs all my cpu if i play more than 3 notes together.
this was not the case in v1.0 so i don't know what's happend...i'll keep largo but it's on the back shelf till it can run properly on my system.

rob

Post

rob_lee wrote:
Ingonator wrote:
Igro wrote:
Ingonator wrote: 1.) improving the CPU load
Usually making CPU loading improvements by lowering sound quality in some parts of the synth. Isn't it? Then I'm against this.
Since i use a Quad Core CPU it's not so much important for me but maybe for others !!
i have a quad core but even playing a chord chews up all my cpu in sonar and the audio engine stops :( i can't even design pad sounds because opening up the amp env release espescially needs all my cpu if i play more than 3 notes together.
this was not the case in v1.0 so i don't know what's happend...i'll keep largo but it's on the back shelf till it can run properly on my system.

rob
Hi, Rob! Do you have only Sonar? Maybe try in other DAWs as well?

Post

rob_lee wrote:i have a quad core but even playing a chord chews up all my cpu in sonar and the audio engine stops :( i can't even design pad sounds because opening up the amp env release espescially needs all my cpu if i play more than 3 notes together.
this was not the case in v1.0 so i don't know what's happend...i'll keep largo but it's on the back shelf till it can run properly on my system.
There's definitely something wrong there, Rob. The core i7 isn't that much faster than the quad, and I'm barely getting over 15% on any patch, with all fingers playing - on 1.1.0/OSX/Live

Post

rob_lee wrote:
Ingonator wrote:
Igro wrote:
Ingonator wrote: 1.) improving the CPU load
Usually making CPU loading improvements by lowering sound quality in some parts of the synth. Isn't it? Then I'm against this.
Since i use a Quad Core CPU it's not so much important for me but maybe for others !!
i have a quad core but even playing a chord chews up all my cpu in sonar and the audio engine stops :( i can't even design pad sounds because opening up the amp env release espescially needs all my cpu if i play more than 3 notes together.
this was not the case in v1.0 so i don't know what's happend...i'll keep largo but it's on the back shelf till it can run properly on my system.

rob
Something wrong with your setup ?? Even a complex pad patch with 6 voices unison gave maximum 30% on my CPU (a Core 2 Quad Q6600) while playing a chord. Only around 10-11% when using 2 voices unison.

I tried to make a patch using almost all features of Largo at once like 3 OSCs, 2 filters, 2 FX and 6 voice unison. CPU load for a chord goes up to 38% maximum. Around 5-6 % of that go to the FX. Biggest CPU killer is the unison: Double voices = double CPU.
Ingo Weidner
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1

Post

Yep something has happened since last night... im finding now that all my plugins are maxing out just playing 2 or 3 notes... only stable plugin is Kubik with 5%.
Im using Sonar 8pe so that's all i have now to test..im noticing only 1 core is being used and stopping the audio engine.. :cry:

What did i do from switching off my pc last night for this to happen?

never installed updates or nothing just switched off last night and on again today and my cpu usage is at max

rob

Post

http://www.macmusic.org/software/versio ... /id/14702/

scroll down for the update notes...

wtf with those download links? is that a working mac demo? then where is the win version? I've downloaded one of the win files but it seems to be full because it asks for my license...which I don't have :D

Post Reply

Return to “Instruments”