Ableton Live 9. Now the counting begins.

[chelemasty]

When??????????????????????????????? Let us atleast know, what year. This year? Earlier next year??? WHAT??? I've been a heavy Live user, tried Studio One 2 and I really like the workflow, plus its 64 bit, so it's really a big plus since most of my work now, Live won't cut it unless I freeze stuff. So please, don't let my money come to them. I will try to resist, but till when??? Atleast, give me goal up to when... Kthanksbye!!! End of rant. TEEHEE

[steffensen]

Yea, 64bit is just so frkn important!



Or is it.............................

[Valiumdupeuple]

The Super Nintentdo was 16 bit, and it was fucking awesome. So, maybe you should switch for another DAW.

[Forge.]

The Super Nintentdo was 16 bit, and it was fucking awesome. So, maybe you should switch for another DAW.

wasn't it 8 bit?

[The Carpet Cleaner]

The Super Nintentdo was 16 bit, and it was fucking awesome. So, maybe you should switch for another DAW.

wasn't it 8 bit?

The Nintendo was 8 bits I believe. The super was 16. The psx 32! then ableton !

[Ableton_David]

Moved to The Lounge.

[regretfullySaid]

I have one project that always crashes now to due "Out of Memory"
If Live x64 resolves that, hell yeah it's important.

[supamonsta]

Moved to The Lounge.

I love that quote. Maybe I'll make a track named like that when I get live 9 and its new refunded program that will give me the power I need to write tracks and that is not available in the former versions

[Styles Bitchly]

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"

[chelemasty]

Uh, it will not affect quality but maybe it will improved workflow? Also, 64 bit will make Live a not so hoggy DAW anymore since it can access more RAMs. And no I don't have a shitty computer, I have an i5 with 8 gigs of RAM and I cant freakin use all of its power. Last time, I'm still halfway done, I freezed some of tracks yet I still get 90% CPU. So we're not really talking about quality of tracks here, its about usability.

[glitchrock-buddha]

Also gotta love the arguments like "But the Beatles made great music on a four track!"

Well the Beatles didn't have huge sampled instruments on a laptop. They had all the real instruments in a studio. The rest of us would like 64 bit so Live doesn't run out of memory when we're playing instruments that sound great but take up a lot of space.

[bzly]

I Finally have Ableton 8 Suite so it can handle anything i throw at it, 60gb plug-in instruments, very processing heavy mastering effects, absurd amounts of audio tracks and i only run around 15% CPU load for a full project. Locking up like that is caused from bad plugins, and poor PC setup, not your amount of ram, try to reinstall those plugs or get new and better ones.

There are many variables to shitty performance, most are PC related. Solve it all and buy a MAC with an i7.

What operating system are you running? Running a 32bit program in compatibility mode on a 64bit platform will only cause you trouble. Some OS (like Vista and 7) take more PC resources to run and don"t like 32bit compatibility mode. In compatibility mode I always found some ghost in the machine. The ghosts did not go away until i was on a 32bit platform.

Try opening the task manager (CTRL+ALT+DELETE) without ableton running and see how taxed you machine really is. (Running Vista or 7 will see a huge amount of your PC's resources dedicated to running useless bullshit on the OS, TURN IT ALL OFF).

What sound card do you have? That could be your problem. Also related to your sound card...
Have you looked at your internal buffer settings inside of Ableton? What is your sample size? What bit rate? What is your sample rate? Are you recording/processing at 16/44.1 24/96 32/192, or something else? Improper settings may be putting unnecessary stress on your machine.

How is your airflow? Your CPU may be overheating.

If you are having trouble with memory, follow these steps (in XP) (control panel/system properties/advanced/performance options). Set Visual effects to best performance. In the advanced tab set processor scheduling to background services. Memory usage to system cache and at least double the current size of your paging file (this is virtual ram, acting like you just installed more ram, but this will eat up some of your hard drive space).



Win XPsp2: 3.0Ghz AMD-PHENOM II, 4GB ram, Ableton 8 Suite 8.2.6 MOTU Ultralite MKIII and finally no more issues.

[glitchrock-buddha]

I Finally have Ableton 8 Suite so it can handle anything i throw at it, 60gb plug-in instruments, very processing heavy mastering effects, absurd amounts of audio tracks and i only run around 15% CPU load for a full project. Locking up like that is caused from bad plugins, and poor PC setup, not your amount of ram, try to reinstall those plugs or get new and better ones.

There are many variables to shitty performance, most are PC related. Solve it all and buy a MAC with an i7.

What operating system are you running? Running a 32bit program in compatibility mode on a 64bit platform will only cause you trouble. Some OS (like Vista and 7) take more PC resources to run and don"t like 32bit compatibility mode. In compatibility mode I always found some ghost in the machine. The ghosts did not go away until i was on a 32bit platform.

Try opening the task manager (CTRL+ALT+DELETE) without ableton running and see how taxed you machine really is. (Running Vista or 7 will see a huge amount of your PC's resources dedicated to running useless bullshit on the OS, TURN IT ALL OFF).

What sound card do you have? That could be your problem. Also related to your sound card...
Have you looked at your internal buffer settings inside of Ableton? What is your sample size? What bit rate? What is your sample rate? Are you recording/processing at 16/44.1 24/96 32/192, or something else? Improper settings may be putting unnecessary stress on your machine. Luckily I have a macbook pro i7, so I can use the memory server in Omnisphere and Trilian but Windows users don't get that, so they would appreciate it even more than I.

How is your airflow? Your CPU may be overheating.

If you are having trouble with memory, follow these steps (in XP) (control panel/system properties/advanced/performance options). Set Visual effects to best performance. In the advanced tab set processor scheduling to background services. Memory usage to system cache and at least double the current size of your paging file (this is virtual ram, acting like you just installed more ram, but this will eat up some of your hard drive space).

That's all well and good, but it doesn't change the fact that Live has an upper limit of useable ram. And that limit is in reality around 3gb. When you are using ram hungry devices like Omnisphere/Trilian (which an empty instance alone of Omni is 250mb for the first and 150 for successive ones, but especially when you're using a huge instrument like a 1gb stand-up bass), or like Amplitube 3 (350mb per instance), then it becomes an issue. No amount of system tweaks and performance perfection can save you from that.

[mikemc]

ok you've gotten far too serious:

http://www.youtube.com/watch?v=cbRmpKjw ... re=related

[glitchrock-buddha]

I Finally have Ableton 8 Suite so it can handle anything i throw at it, 60gb plug-in instruments, very processing heavy mastering effects, absurd amounts of audio tracks and i only run around 15% CPU load for a full project. Locking up like that is caused from bad plugins, and poor PC setup, not your amount of ram, try to reinstall those plugs or get new and better ones.

There are many variables to shitty performance, most are PC related. Solve it all and buy a MAC with an i7.

What operating system are you running? Running a 32bit program in compatibility mode on a 64bit platform will only cause you trouble. Some OS (like Vista and 7) take more PC resources to run and don"t like 32bit compatibility mode. In compatibility mode I always found some ghost in the machine. The ghosts did not go away until i was on a 32bit platform.

Try opening the task manager (CTRL+ALT+DELETE) without ableton running and see how taxed you machine really is. (Running Vista or 7 will see a huge amount of your PC's resources dedicated to running useless bullshit on the OS, TURN IT ALL OFF).

What sound card do you have? That could be your problem. Also related to your sound card...
Have you looked at your internal buffer settings inside of Ableton? What is your sample size? What bit rate? What is your sample rate? Are you recording/processing at 16/44.1 24/96 32/192, or something else? Improper settings may be putting unnecessary stress on your machine. Luckily I have a macbook pro i7, so I can use the memory server in Omnisphere and Trilian but Windows users don't get that, so they would appreciate it even more than I.

How is your airflow? Your CPU may be overheating.

If you are having trouble with memory, follow these steps (in XP) (control panel/system properties/advanced/performance options). Set Visual effects to best performance. In the advanced tab set processor scheduling to background services. Memory usage to system cache and at least double the current size of your paging file (this is virtual ram, acting like you just installed more ram, but this will eat up some of your hard drive space).

That's all well and good, but it doesn't change the fact that Live has an upper limit of useable ram. And that limit is in reality around 3gb. When you are using ram hungry devices like Omnisphere/Trilian (which an empty instance alone of Omni is 250mb for the first and 150 for successive ones, but especially when you're using a huge instrument like a 1gb stand-up bass), or like Amplitube 3 (350mb per instance), then it becomes an issue. No amount of system tweaks and performance perfection can save you from that.

350mb usage per instance of Amplitube 3? 1gb usage per instance of "stand up bass"?

I have a project playing and my CPU peaks at 9 percent. I added three instances of Amplitube 3 and it peaked at 20 percent. 20 - 9 = 11 percent. 4gbs of ram, 2.85 gbs available = 2918.4 mb of ram available. 2918.4 * 11% = 321.024. That's 321.024 mbs of usage for three running instances of Amplitube.

What sampled instruments are you using (i.e. for your stand up bass)? I can run four instances of Kontakt 4 with each running various sample-heavy patches, and I just barely get CPU usage peaking at 20%/583.68 mb (that's including the CPU usage taken up by Ableton Live running and Firefox running and normal system processes).

EDIT: Just to clarify, I'm not saying you're lying or anything - the numbers just seem big and I'm curious.

Hey man, I think you're seriously confused about cpu usage and ram usage. You are doing some very strange and irrelevant calculations there. 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.

cpu usage depends on your processor. Ram is simply the amount of ram you have in your machine. Plug-ins will use ram and also processing power. They are (for the most part) completely independent as far as plug-ins go. We aren't talking about cpu usage at all. If you want to know how much ram a plug-in is using, open up your activity monitor, look at how much ram your Live application is using, then add the plug-in and see the difference.

You can have a project using only 10% of your cpu and max out the ram by going above about 3gb (for example using sample heavy stuff), which can cause Live problems. You can also use only a fraction of your available ram and max out your cpu (this would happen for examples using lots of soft synths at high polyphony which are cpu intensive but don't use tons of ram).