Ableton Live 9. Now the counting begins.
Posted: Mon Oct 24, 2011 7:50 am
wasn't it 8 bit?Valiumdupeuple wrote:The Super Nintentdo was 16 bit, and it was fucking awesome. So, maybe you should switch for another DAW.
The Nintendo was 8 bits I believe. The super was 16. The psx 32! then ableton !Forge. wrote:wasn't it 8 bit?Valiumdupeuple wrote:The Super Nintentdo was 16 bit, and it was fucking awesome. So, maybe you should switch for another DAW.
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 versionsMoved to The Lounge.
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.bzly wrote: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).
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.scutheotaku wrote:350mb usage per instance of Amplitube 3? 1gb usage per instance of "stand up bass"?glitchrock-buddha wrote: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.bzly wrote: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).
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.