Ableton Live 9. Now the counting begins.

[glitchrock-buddha]

glitchrock-buddha wrote:
Did you just multiply the cpu footprint of your amplitube instances by your available ram to get a total ram usage of amplitube? That's like me multiplying the pixels on my screen by the number of bananas in my kitchen to get the sample rate of my project. No offense, it was just funny.


Haha nope! I just told you how much CPU three instances of Amplitube 3 were using - 11%. I then told you how much physical memory three instances of Amplitube 3 were using - 321.024mb. Perhaps I wrote my post strange (I'll have to look at it again)?

I'm pretty sure you did.
"2918.4 mb of ram available. 2918.4 * 11% = 321.024. That's 321.024 mbs of usage for three running instances of Amplitube."

You multiplied the available ram (2918.4) by the cpu usage of three instances of amplitube (11%) to get what you think three instances of amplitube takes up in ram (321.024). The percentage of cpu that a plug-in uses does not translate into it using that percentage of ram.
That's whack.

Open a fresh Ableton Live. Look at the ram usage in Activity Monitor. Now add 3 amplitubes. For me it goes like this:
-Fresh Live: 241.0 mb
-After three isntances of Amplitube 3: 1.05 GB used in Live

I'm on an i7 macbook pro, 8gb ram. The above numbers are normal and accurate. So in this case Amplitube is using a bit under 300mb per instance actually. There is no way you're loading Amplitube 3 at around 100 mb per instance. Are you on a PC?

[MarkvW]

Live 9 isn't going to make one single solitary difference in the quality of your music. Look inside yourselves and ask "why do I really want that Ver. 9"

I want 9 because they haven't come out with eleven yet!

[Ryanmf]

I want 9 because they haven't come out with eleven yet!

Yeah, Live X is going to be total bullshit.

[supamonsta]

hi, looking for a live 7 licence to buy, anyone?

cheers


(not kiddin')

[bzly]

The main issue is that Ableton is designed for a 32bit platform not 64bit.
Windows 7 is a HEAVY OS. Lots of unnecessary apps, widgets, visual effects and user options are running in background, and need to be eliminated. When they are eliminated, there will be much more resources (ram) available.

I understand the want for more ram but there is a lot to be said for machine efficiency.

To solve your problems running spectrasonics plugs you need to increase your paging file (a space of your hard drive treated as virtual ram) and improve your processor's affinity (what programs have priority).

I had all the same problems you are talking about with memory and processing running spectrasonics /native instruments/ IK / Waves /and UAD plugins.

I got a better sound card, increased my virtual ram, and eliminated the visual effects in windows, and ran it on XP service pack 2 on a 32bit platform. After that i have made a project using all of these Omnisphere, Atmosphere, Stylus RMX, Trilogy, Sampletank, Analog factory and a bunch of waves plugins without an issue.

I believe the ghosts you are seeing are because you are running on a 64bit platform.

[Forge.]

The main issue is that Ableton is designed for a 32bit platform not 64bit.
Windows 7 is a HEAVY OS. Lots of unnecessary apps, widgets, visual effects and user options are running in background, and need to be eliminated. When they are eliminated, there will be much more resources (ram) available. ....

on that topic - I installed Win 7 on a Boot camp partition and for some stupid reason I thought I'd only need 20GB for it as I only need it for one program really. The install took up almost all of that and not it is a total PITA to do anything about it - I either have to buy a program to manage the partition size or install it again.

[glitchrock-buddha]

Open a fresh Ableton Live. Look at the ram usage in Activity Monitor. Now add 3 amplitubes. For me it goes like this:
-Fresh Live: 241.0 mb
-After three isntances of Amplitube 3: 1.05 GB used in Live

I'm on an i7 macbook pro, 8gb ram. The above numbers are normal and accurate. So in this case Amplitube is using a bit under 300mb per instance actually. There is no way you're loading Amplitube 3 at around 100 mb per instance. Are you on a PC?

Yes, exactly.
-Fresh Live (well actually, with a few audio clips in it as I already had a set open): 697 mb
-After three instances of Amplitube: 1031 mb

I'm on a PC. Windows 7 Premium 64 bit, 4gb of ram.

Also, if you're wondering why my fresh Live is 697mb and yours is 241mb - I'm not sure.

When I say a Fresh Live, I mean freshly opened. That's probably the difference. If you had already been using, then it's not a freshly opened live. Ram builds up in the application.
Do the steps literally:
-Close Live
-Open Live
-Look at ram usage
-Add the 3 amplitubes and look at the ram usage again.

I'd be amazed if there is really that much ram difference. I think those instances of amplitube are using ram temporarily stored in Live. That's why you need to test on a newly opened set.

[Rave]

The main issue is that Ableton is designed for a 32bit platform not 64bit.
Windows 7 is a HEAVY OS. Lots of unnecessary apps, widgets, visual effects and user options are running in background, and need to be eliminated. When they are eliminated, there will be much more resources (ram) available. ....

on that topic - I installed Win 7 on a Boot camp partition and for some stupid reason I thought I'd only need 20GB for it as I only need it for one program really. The install took up almost all of that and not it is a total PITA to do anything about it - I either have to buy a program to manage the partition size or install it again.

Try changing the partition size using disk utility.

[Forge.]

The main issue is that Ableton is designed for a 32bit platform not 64bit.
Windows 7 is a HEAVY OS. Lots of unnecessary apps, widgets, visual effects and user options are running in background, and need to be eliminated. When they are eliminated, there will be much more resources (ram) available. ....

on that topic - I installed Win 7 on a Boot camp partition and for some stupid reason I thought I'd only need 20GB for it as I only need it for one program really. The install took up almost all of that and not it is a total PITA to do anything about it - I either have to buy a program to manage the partition size or install it again.

Try changing the partition size using disk utility.

nah can't without wiping it

[bzly]

try shrinking the larger drive then expanding the smaller 1... google expand partition

[Forge.]

try shrinking the larger drive then expanding the smaller 1... google expand partition

point is there is considerable risk involved which I can't quite be arsed with at present. i.e. high chance the W7 partition won't work

[crumhorn]

I'm fairly sure there is a counter in Live 8 already

[bzly]

Well I tried to give a solution without reinstalling W7,
but any way you stack it you are best off with a fresh install of 7 with at least 50GB on that partition.

And btw isn't there a comparable program on Mac?
What program are you trying to run on W7?