Waldorf Largo 64 bit, when?

[ShamanicRitual]

Thanks, Ingonator.

I don't have any problems with arpeggio, because have not used it at all.
And I have 8gb of ram, but I still use 32 bit logic. It can allocate around 2.3-2.8Gb than it quit with low memory message. So for kill logic you should just load 8 instances of Largo. When you just load it, it takes less then 100 mb. But if you open GUI, it take 300mb or something like that. When you unload Largo, memory is not released, so it make impossible to use synth in production workflow.
It's not logic related bug, I repeated it in cockos reaper too.

I guess it's will be better solution to release new mini version with new chorus and OSCs, but without preset browser (if browsers costs 150mb, not worth it).
But I lost hope. Maybe sometime I'll switch on 64bit DAW and will use new 64bit version of Largo, 300mb without release not a big problem in this case.

For now, 1.1 much better for me. But you can't make super-punchy sounds without phase control, and I have 1 crash of project already with this version. There can be another bugs. I really like sound of Largo, but developers did terrible job in terms of optimization and bug testing before release.

Btw, Ingo. What OS and DAW do you use with your Largo? And how many instances do you loaded. Did you experience Largo sluggish interface or crashes during production?

[Ingonator]

Thanks, Ingonator.

I don't have any problems with arpeggio, because have not used it at all.
And I have 8gb of ram, but I still use 32 bit logic. It can allocate around 2.3-2.8Gb than it quit with low memory message. So for kill logic you should just load 8 instances of Largo. When you just load it, it takes less then 100 mb. But if you open GUI, it take 300mb or something like that. When you unload Largo, memory is not released, so it make impossible to use synth in production workflow.
It's not logic related bug, I repeated it in cockos reaper too.

I guess it's will be better solution to release new mini version with new chorus and OSCs, but without preset browser (if browsers costs 150mb, not worth it).
But I lost hope. Maybe sometime I'll switch on 64bit DAW and will use new 64bit version of Largo, 300mb without release not a big problem in this case.

For now, 1.1 much better for me. But you can't make super-punchy sounds without phase control, and I have 1 crash of project already with this version. There can be another bugs. I really like sound of Largo, but developers did terrible job in terms of optimization and bug testing before release.

Btw, Ingo. What OS and DAW do you use with your Largo? And how many instances do you loaded. Did you experience Largo sluggish interface or crashes during production?

Hi,

i'm using Largo on Windows 7 32-bit and either Ableton Live 8.2.2 or Reaper 4 32-bit. I 'm using Largo v1.5.1 for Windows without bigger problems, except the problem with the memory like i was able to confirm now. I have added a new entry to the Largo bug report (with mentioning there is also a problem at the Mac).
BTW i found that the "memory problem" is only there when the GUI was opened. This goes away when either starting a new project or reloading a Largo project without opening the GUI (or GUIs for multiple instances).

You could also contact Waldorf yourself at:
support@waldorfmusic.de

BTW the CPU use depends on if you use e.g. the Unison (and how many voices) and/or the layer feature. If you do a layer using the layer features instead of multiple instances you'll need much less CPU (same in PPG Wave 3.V).


Ingo

[ShamanicRitual]

BTW i found that the "memory problem" is only there when the GUI was opened. This goes away when either starting a new project or reloading a Largo project without opening the GUI (or GUIs for multiple instances).

Yeah, how I said before, it's GUI. Why Massive or Zebra with same/expanded functionality keep memory usage lower than 100mb?
Version 1.1 of largo use around 40mb too. So it's probably bug of fancy preset manager in new version.

[draft14]

Any news about x64 update?

[HcDoom]

I would like to see Largo in 64bit....but that's only wish and Waldorf shows no interest in 64bit as far as I know.

[Josmoker]

Bump - any news on a 64bit version of the Waldorf Edition?

[draft14]

Even Ableton x64 bit beta now but no news about Waldorf plugins

[ObsoleteAcc99]

[DELETED]

[aMUSEd]

Bit annoying really, they seem to have no problem investing energy into trying to flog it, but where is the same energy invested into developing it further?

[Robo2k]

Nov 2012 and STILL no 64-bit version. It's a total joke, like KORG legacy.

[EvilDragon]

Patience = virtue.

[Cyforce]

Me as Blofeld user also still waiting for MicroQ Patch import and an software editor for it - both should come - long before Largo was released...

So be patient

[MatzeMillion]

Nov 2012 and STILL no 64-bit version. It's a total joke, like KORG legacy.

The 64bit version of the Waldorf Edition is mentioned in the system requirements at their site since a while now. It will be version 1.7.3 but I couldn't find a download link. Anyway... I just guessed the filename and voila... works well!

Strange, the installer is from 2011. What is keeping them from releasing it to the public?

[EvilDragon]

I purchased Waldorf Edition and got 64-bit installer with that purchase. So, it's in public alright.

[horsma]

You have to send email to Waldorf support to get new Waldorf edition installer (If you have the old CD install version).
From Waldorf FAQ:
The Plug-ins of the Waldorf Edition themselves run fine on a 64 bit system, but the CD installer is unfortunately not compatible with 64 bit operating systems. The solution: Our new download-version without any CD-authorization installs and runs without any problems. Please send a scan of your original Waldorf Edition invoice as a proof of purchase along with a picture of the packaging showing the serial number to our support. We will then authorize a download-version for you.