Ableton Forum

...and is still not decided when it will come out?

I wonder if current Live users will need to pay for the upgrade to 64 bit.

Nobody of us "ordinary users" knows.

Have you checked one of your Live projects with Activity Monitor?

steko wrote:

...and is still not decided when it will come out?

I wonder if current Live users will need to pay for the upgrade to 64 bit.

Nobody of us "ordinary users" knows.

Have you checked one of your Live projects with Activity Monitor?

I will tonight and check back in.

ramangill wrote:

steko wrote:

...and is still not decided when it will come out?

I wonder if current Live users will need to pay for the upgrade to 64 bit.

Nobody of us "ordinary users" knows.

Have you checked one of your Live projects with Activity Monitor?

I will tonight and check back in.

Here is what I saw:

Real Memory: 490.8 MB
# of Threads 14
Virtual Memory: 1.51 GB
Shared Memory: 18 Bytes
Private Memory Size 402 MB
Virtual Private 527.2 MB
Overall CPU % : 51.9% (Seems high no? But in Live's cpu monitor it only went as high as 19%)

I don't see NERVE or Aruturia pop up though.

So how do these #'s look?

levelpan24 wrote:Been having a similar problem.I get crashes when using Amplitube 3.I thought I might need more ram as well,but Ableton said the crashes came from inside Amplitube and that it brought down the host system with it.Still working on figuring it out.Good luck with yours.

We have been working with Ableton to resolve AmpliTube issues within Live.
The next AmpliTube update which is due out in a few weeks will address this.
And it will support x64, too.

maybe is the problem is live ?

ramangill wrote: Real Memory: 490.8 MB
# of Threads 14
Virtual Memory: 1.51 GB
Shared Memory: 18 Bytes
Private Memory Size 402 MB
Virtual Private 527.2 MB
Overall CPU % : 51.9% (Seems high no? But in Live's cpu monitor it only went as high as 19%)

I don't see NERVE or Aruturia pop up though.

You mean vsts? They dont show up. But if you remove them one by one from Live, you will imediately see their ram usage in the activity monitor. Dont know how to read it on OSX, but on Windows its easy. I have no idea what "virtual private" means!

Not sure if this is related to the problem you're having, but yesterday my Live 8.2.1 stopped working. First I got a crash, so I restarted the app, no biggie.. But then Live said "audio engine is disabled", and now every time I try to switch the audio engine back on, I get a beach ball followed by a crash! And yes, this is with the default coreaudio lineout, no external soundcard or peripherals in use..

So it's back to using earlier builds for me.. a pity that I already made a bunch of projects in 8.2.1 so now I can't open them due to version incompatibility..

All in all, I'm slowly becoming disinterested in Live.. Definately not a "fanboi" anymore at least..

Just sent a mail to support. Lets see what they say.

I had this problem running an i7 macbook pro 2.66ghz when I was running 10.6.5. Updated to 10.6.6 and your problems will most likely go away. You should still add more ram to your system. 3gb is not enough - you should add an additional 4gb. Ideally you want to give a full 4gb to Live, and let your OS use 2-3gb by itself.

Do you get (high amounts) of "Page outs" in Activity Monitor?

I think you have a problem with your 3rd-party audio stuff...

You can also try this:

- quit Live & drag your Preferences.cfg file (/Users/ramangill/Library/Preferences/Ableton/Live 8.2.1/Preferences.cfg) to the desktop.

- start Live & reenter your Preference settings (maybe make screenshots - Cmd-Shift-4-Spacebar-click - of your settings before dragging Preferences.cfg)

or try the newest beta...

Overall CPU % : 51.9% (Seems high no? But in Live's cpu monitor it only went as high as 19%)

That's normal - Live's CPU-meter & the one in Activity Monitor are not comparable.

ze2be wrote:Just sent a mail to support. Lets see what they say.

+1

ze2be wrote:

ramangill wrote: Real Memory: 490.8 MB
# of Threads 14
Virtual Memory: 1.51 GB
Shared Memory: 18 Bytes
Private Memory Size 402 MB
Virtual Private 527.2 MB
Overall CPU % : 51.9% (Seems high no? But in Live's cpu monitor it only went as high as 19%)

I don't see NERVE or Aruturia pop up though.

You mean vsts? They dont show up. But if you remove them one by one from Live, you will imediately see their ram usage in the activity monitor. Dont know how to read it on OSX, but on Windows its easy. I have no idea what "virtual private" means!

Remove them??? You mean calculate total RAM now, delete the VST from Live, see the total RAM and do the math?

ramangill wrote:

ze2be wrote:

ramangill wrote: Real Memory: 490.8 MB
# of Threads 14
Virtual Memory: 1.51 GB
Shared Memory: 18 Bytes
Private Memory Size 402 MB
Virtual Private 527.2 MB
Overall CPU % : 51.9% (Seems high no? But in Live's cpu monitor it only went as high as 19%)

I don't see NERVE or Aruturia pop up though.

You mean vsts? They dont show up. But if you remove them one by one from Live, you will imediately see their ram usage in the activity monitor. Dont know how to read it on OSX, but on Windows its easy. I have no idea what "virtual private" means!

Remove them??? You mean calculate total RAM now, delete the VST from Live, see the total RAM and do the math?

Yes.

ze2be wrote:

ramangill wrote:

ze2be wrote: Remove them??? You mean calculate total RAM now, delete the VST from Live, see the total RAM and do the math?

Yes.

LOL, I hate Math

Alright, were working quite intensly in Live here, and get a lot of ram crashes. (100 hours of work on this track alone, 12 hours a day)

We have now recorded 90% of the synths to audio tracks, because of audio glitches and ram crashes the last 3 days.
What remains is 1 instance of Surge, and 1 instance of Tension, 3x 3rd party reverbs that use about 30mb of ram in total, roughly 60 Samplers and Simplers (mostly from 2 sliced audio clips), and lots of effects from Live that really use next to nothing of ram.
Project uses about 50 tracks, including grouped drums tracks.


Total Ram in use by this WinXP PC: 3000mb
Ram used by system alone: 196mb
Ram usage of system + empty Live set: 363mb
Ram usage of our Live project + system: 1690mb

We then out of curiosity deleted one by one track, and all the sends too.
In the end there was only one empty midi track left. No sends, no plugs.

Current system ram usage was now: 1390mb. Wheres that 1000mb going? No audio files are loaded into ram. Its all run from the drive.


It appears that we have actually used about 300mb with plugs on the project, which measures up quite right with the combined usage of the plugins ram usage, upon testing. (See the Live 8 Plugin Performance Test thread)
Saving the file; restart Live; and re-open this save; it now uses 363mb. It lost 1000mb of usage.. The crashes appears upon nearing 2gb of ram usage. But where is the last 1gb of the 3gb in total?


The last thing we did of musical editing work before we let it go, was trying to cut some time in this project. So the system is using 1690mb of ram, and Live uses 1300mb of those, and we execute the "cut time" command on a loop in Arrangement view: System jumps to 1999mb of ram usage, and Live freeze up. Waiting 15 minutes.. Hmm.. Lets try a system reboot. Reboot: PC uses 5 minutes to shut down. Re-open Live after reboot: 5 minutes to open. "Yes", we would like to open the unsaved file: another 10 minutes loading time. And from there: Selecting soundcard in prefs: 5 minutes loading time.


Im clueless. Live 8.2 has really been working flawlessly a couple of months, with this kind of hard work, until the last few days.


System: Win XP sp2
Ableton Live Suite v8.2
CPU: Intel q6600, 2.4ghz quad core
Ram: 3000mb
Drive: 7200rpm
Free disk space on system drive: 20%
Free disk space on project drive: 40%

I have the same issue as several people in here have noted. Recently I downloaded a lot of plugins, and am gaining a lot of samples stored on an external hard drive as well. I have about 6 different plugins running in one session, and in some cases multiple instances of things such as effects and reverb. At first I thought it was caused by my midi controllers, an apc40 and an akai mpd32, but I'm pretty sure its the plugins. I start live up, it gets to a certain point of the loading process, and crashes. I then have to go into my task manager (PC) and end the process. Then I click into Live again, and it works. Yesterday it kind of froze my task manager, and wouldn't end the process, so I had to restart. After the restart, Live just wouldn't open and crashed instantly after clicking it. It resolved itself magically though.

I kind of wonder if its because all my software is cracked though...