Ableton Forum

+1

they should first deallocate and clear memory that was allocated by a deleted plugin/internal effect before start addressing the 64bit issue.

use some memory hungry plugin (or even a big live rack with sampler), notice the memory consumption of live, delete the plugin, or even close the set. notice the memory allocation of your empty set... its not what live started up in the first run..
such a shame, they can't their act together.

On my mac, I use iFreeMem until that issue is fixed. I find that problem across several DAWs

zigzag wrote:they should first deallocate and clear memory that was allocated by a deleted plugin/internal effect before start addressing the 64bit issue.

use some memory hungry plugin (or even a big live rack with sampler), notice the memory consumption of live, delete the plugin, or even close the set. notice the memory allocation of your empty set... its not what live started up in the first run..
such a shame, they can't their act together.

If iFreemem can release it, then Live probably dealocated it. In other words : the OS probably keeps stuff in ram cache, and really frees the mem, only if an app needs it.

+1 for 64bit

I think you can pretty much be guaranteed that live 9 will be 64 bit. The audio engine is already, (yeah I know that's not as relevant as some think, just sayin).
Ableton were über quick about getting on board with Intel Macs, and OSX, so I see no reason they would be that far behind in terms of 64 bit?
Maybe everyone will get lucky and the code rewrite for 64 bit allows them to justify working on clip automation and automation in general? That's my guess for Live 9 anyway, 64 bit and automation upgrades.

+1 for 64 bit. I don't think Live is that ugly, but the siezures have got to go!

I've been working with Omnisphere, East West Quantum Leap Symphonic Orchestra and EWQL Pianos, and NI Kontact4. With EWQL under Ableton, I can barely load the Steinway. Omnisphere is also RAM intensive. Under Cubase 5.5 64-bit I have no issues on my system, which has 10GB of fast memory and an i7 processor.

Reaper, Sonar, Cubase, Protools, Logic, they are all providing 64-bit. Ableton in 32-bit is just crushing flexibility in experimentation. I'm afraid to load new sounds. The EWQL PLAY plugin constantly warns me of low memory conditions and possible system instability, but I tell it to load anyway and cross my fingers.

Lately I've had to put parts into Cubase and mix them down and then load them as audio into Live. To put it mildly, now that I'm used to Ableton's workflow I feel like I can't stand working without it.

Can Ableton please release a statement of estimate on when the 64-bit refactoring and building is scheduled for release, or internal QA? Also, as a professional software QA engineer (my daytime job) I will gladly volunteer to test and stress this in beta.

Thanks

+1 for 64bit support

If I lived in Germany, I would march around their office for an hour every day! 64BIT!! 64BIT!!

I've got a crazy idea......64bit!

+64

i would love 64bit support to either by a kind of bridged or native

+1
I need to buy a new PC (or MAC) I didn't decide yet.
But all new Hardware and Software are 64b - and most of my plugs-in are 64b
will be a huge improvement to follow up the trend of the technology!
regards, ludande

Me too!!!!!

I have 12Gigs of RAM.