Dubstepforum.com

hmm I hadn't thought of that, could very well be the reason why I'm having this problem... Guess I just gotta wait till Ableton 9 then :/

RAM has nothing to do with running out of CPU. They're totally different problems.

http://createdigitalmusic.com/2012/07/a ... e-caveats/

Having 64 bit software has more to do with it than you think. I can create projects twice to three times as large in software with more 64 bit advantages. DO some research on the subject and you'll see varying opinions. But from personal experience, this is what I have concluded.

The problem that will arise though is that your 32 bit plug ins wont work in Ableton 64bit! Without an adapter (whatever that means). Which sucks for lesser known plug ins that do cool things that may not be able to upgrade to 64 bit.

ill mindset wrote:http://createdigitalmusic.com/2012/07/a ... e-caveats/

Having 64 bit software has more to do with it than you think. I can create projects several times larger in software with more 64 bit advantages. DO some research on the subject and you'll see varying opinions. But from personal experience, this is what I have concluded.

Lol i've worked in IT for years, i know about 64 bit software. No need to research, i can tell you right off the top of my head that a 64bit program running on a 64bit cpu will indeed run slightly faster than a 32bit program on a 64bit cpu, as it'll bypass the wow64 subsystem. The difference is usually about 1-3%, so on a 2.5ghz chip it'd be like having a 2.55ghz chip. Hardly much of a solution, but every little helps.

You were talking about the ram limit which is why i commented, as ram has nothing to do with the op's problem. Perhaps it is you who needs to do the research, as you'll see that not having enough ram will only starve the cpu as the computer would have to use the page file which is orders of magnitude slower. The op's cpu is running at 100% which indicates that the cpu is getting fed plenty of data, we can therefore see that a ram limit isn't the bottleneck.

hey bro, I'm not trying to argue with you. I'm telling him what I have found to be a way of dealing with the same problem. And here you are trying to disprove what I know works. I wasn't only talking about RAM. You will find a significant cpu performance advantage on 64 bit software. I was pointing out the HUGE difference in the RAM ceiling between the 2 because its incredible. Have fun writing your ridiculous retort. I have nothing more to add here.

Edit: I should be more clear. I'm not saying I have noticed a 300% increase in CPU performance. I can work on much bigger projects now. I dont know what the exact numbers are but its made a difference and its awesome.

You're calling me dipshit and telling me to do research, i'm not the one claiming 300% increases for switching to 64bit, that's just dumb. Stop acting like a child, its not a competition.

I'm very interested in potential gains from switching to 64bit, i'm still using 32bit Cubase. But so far the gains haven't been there from what i've read. In some cases 64bit apps have even run slower, but that may have been teething problems.

The main benefit to 64bit is as you posted, being able to address exabytes of ram. Definitely an advantage for someone working with lots of 96khz samples.

And an adapter you mentioned would be something like jbridge. Problem is, it'll decrease performance using it but at least you can use older vst's.

I have just had to deal with this problem myself.


My cpu was balls to the wall over 130 sometimes. I run an intel i5 .3.2 ghz. 8 gb ram. I am runnning about 50 tracks. Live is in Beta for 64 bit which will help it to access that extra ram, which in turn will allow for higher sample rate. I was using Reason 64 bit , and it didn't come close to the crashes and lags in Live!

I also posted a thread in Live forums about this. My response was tame some of the synths I am running and freeze and flatten some tracks. Lol... if you want a powerful cpu, you might think about a Xeon board as I am. this will probably take care of the lags.

ok this issue's got out of control now. I've literally only got 6 channels running on a 2.2ghz 6gb ram laptop and its still crashing at 140%

Try Asio, buffer all the way up, that automatic disable thing ill mindset talked about (although you shouldn't use it for some plugins, like dblue glitch because of the sequencer), and make sure your antivirus isn't scanning in the background.

I run a 4 yr old 32 bit daw, 2 ghz, 4gb ram, at a 44.1 sample rate without asio with 10ms latency most of the time and hardly have problems.

I dont think anyone asked this but are you using a legit copy of ableton? In your original post, you mention one of your ableton projects. Is this happening on other projects as well? Have you tried cleaning/ computer maintenance (CCleaner's a good one) ?

i have an i5 macbook but i just upgraded my ram from 4 gb's to 8 gb's at the mac store.

it is not a game changer but it has noticeable effects to my computer speed. I can now "function" with projects that were originally impossible to do.

However, I still cannot say i'm comfortable with the speed at all. MY projects tend to stay under 30 tracks ALL because of CPU limitations. In fact, I would say I have produced "unnecessarily empty" productions wholly because of CPU limits.

I'm not sure if the actual track count matters although maybe it does because one time I consolidated 7 drum rack tracks and I bought like 5 % cpu.. (all the same simpler modules in the cells and number of sounds and effects but consolidated to one beefier drum rack track and it functioned better.

cheers mate hope you get through this.. i've been fighting the cpu fight for almost a year now

haha, 'tis a tough fight indeed...

I could upgrade to 8gb ram but i doubt thats the main problem here. I was reviewing whats changed in my production methods over the last week and realized I've been using the drum rack a Lot more, before this I would just place in audio clips for percussion cos that worked for me. So now I've been tracking down certain fx and stuff in particular, like say my Ambience Reverb VST that take up a shitload of cpu and doing send return chains within the drum rack, etc etc. This has stopped my overload for now. So that is something everyone can try: find that one vst thats just insane when it comes to cpu and maybe send/return it?

Also artie, whats the automatic disable option that ill gates talked about?

JizzMan wrote:gates

who?

ah, I reread his post. he was talking about FL, not ableton. I would imagine ableton as well as most other daws have it in some form.
maybe abletons just crap *puts on flamesuit*

neonmansion wrote:i have an i5 macbook but i just upgraded my ram from 4 gb's to 8 gb's at the mac store.

it is not a game changer but it has noticeable effects to my computer speed. I can now "function" with projects that were originally impossible to do.

However, I still cannot say i'm comfortable with the speed at all. MY projects tend to stay under 30 tracks ALL because of CPU limitations. In fact, I would say I have produced "unnecessarily empty" productions wholly because of CPU limits.

This is such a stupid post!

Learn to use your equipment properly - people have been making electronic music for decades with only a fraction of the power we have today. If your tracks are empty, bounce stuff to audio then add more stuff. Stop hiding behind excuses!

30 tracks and he considers the tracks empty?

hahaha my bad, all credit goes to ill mindset not gates

and No, abletons not shit. Skrillex uses it bruh

^ hahaha it crashed when I saw him live.

Electric_Head wrote:30 tracks and he considers the tracks empty?

probably uses every effect on a send

Check the plugins you are using in the project. I know I had a problem when I used Uhbik- A Reverb in my projects, my cpu would randomly jump up to above 100%, audio dropout, the works. If you can pinpoint the plugin, you can talk to the plugin manufacturer about it and they may come up with a solution. You should'nt be overpowering your cpu with that many tracks unless you have 30 Divas on "Divine."

2.2ghz. there is your problem. whether it is an i7 or not has nothing to do with it.