live only using one processor core
live only using one processor core
Hey everyone I just installed live lite and for some reason it will only utilize one processor core, I enabled multicore support in the preferences tab and downloaded the latest version of live (8.2 something) but I still only get activity on one core. I am using an AMD Athlon 64FX-62 dual core, it is an older processor is it possible that live just doesn't recognize that it is a dual core?
I know the processor uses both cores with other tasks so it seems to be unique to live.
Any help would be very much appreciated, Thanks.
I know the processor uses both cores with other tasks so it seems to be unique to live.
Any help would be very much appreciated, Thanks.
Re: live only using one processor core
hi i've got nearly the same problem...i have a amd processor and live don't seems to support it well.... when live begin to use the second processor,i've got cpu spikes when the second processor kick in...
-
data__stitch
- Posts: 65
- Joined: Mon Mar 31, 2008 9:16 pm
- Location: COLORADO
- Contact:
Re: live only using one processor core
Same problem for me. With multicore support on, cpu usage hits the fan, audio goes nuts, and I am forced to restart.
-
Dean Corrie
- Posts: 56
- Joined: Sat Oct 09, 2010 3:14 pm
Re: live only using one processor core
Hello,
No problems here, using my AMD quad core desktop, or dual core laptop.
Have you got Windows power options set to high performance/100% cpu?
Cheers,
Dean
No problems here, using my AMD quad core desktop, or dual core laptop.
Have you got Windows power options set to high performance/100% cpu?
Cheers,
Dean
-
data__stitch
- Posts: 65
- Joined: Mon Mar 31, 2008 9:16 pm
- Location: COLORADO
- Contact:
Re: live only using one processor core
Yes, everything set to high performance and everything optimized for audio. Still, problem doesnt happen with cpu support off. ive searched the web but have not found much in the way of this problem. What is the deal?
Re: live only using one processor core
After playing around awhile and a bios update i found that certain instruments when played live will only utilize one core but during playback both cores are used, i think its a bug in the program that creates this problem with AMD processors.
Any others with this problem could look and see if there is a bios update available that seems to help.
BE VERRY CARFULL UPDATING BIOS!!! if you are not real familiar with that sort of thing, if not done correctly a bios update can turn your computer into a big paper weight!
Any others with this problem could look and see if there is a bios update available that seems to help.
BE VERRY CARFULL UPDATING BIOS!!! if you are not real familiar with that sort of thing, if not done correctly a bios update can turn your computer into a big paper weight!
Re: live only using one processor core
Rahad Jackson wrote:My Awesome Mix Tape #6
-
data__stitch
- Posts: 65
- Joined: Mon Mar 31, 2008 9:16 pm
- Location: COLORADO
- Contact:
Re: live only using one processor core
Maybe I missed something, or didn't get a full understanding of the forum linked, but I didn't really see anyone having the same issue. When cpu support is off I am stable, when on, cpu hits the roof. This is in a new live set with no effects of any sort or instruments on any channel.
-
Gregory Wells-King
- Posts: 249
- Joined: Sat Mar 03, 2007 6:46 pm
- Location: Somerset UK
- Contact:
Re: live only using one processor core
Hi
In offering my 2p's worth, You can change your processor settings in BIOS F2 or F10 or F12 on startup, I have a Dell XPS 1520 and altered my set up for Speedsteping (disabled) in my Dual Core. due to not seeing a constant rate in my CPU which I prefer for referencing when I think there maybe audio drop out's or a crash. It does'nt seem to effect any performance. You can also set up for single core or dual core from there. (This may have been done in the past or if you've ever tinkered in BIOS something may have got changed..)
Also after reading your comment I thought I would turn on my task manager to see what's happening and noted Live was ok on my set up, but of course some of my Instruments are using only one core 'FAW Circle' for one, which shows up as spikes on only one core, oddly reminding me why 'Circle' has such a large foot print on the CPU. Thanks for the tip, I will use in the future to find out what's happening.
In offering my 2p's worth, You can change your processor settings in BIOS F2 or F10 or F12 on startup, I have a Dell XPS 1520 and altered my set up for Speedsteping (disabled) in my Dual Core. due to not seeing a constant rate in my CPU which I prefer for referencing when I think there maybe audio drop out's or a crash. It does'nt seem to effect any performance. You can also set up for single core or dual core from there. (This may have been done in the past or if you've ever tinkered in BIOS something may have got changed..)
Also after reading your comment I thought I would turn on my task manager to see what's happening and noted Live was ok on my set up, but of course some of my Instruments are using only one core 'FAW Circle' for one, which shows up as spikes on only one core, oddly reminding me why 'Circle' has such a large foot print on the CPU. Thanks for the tip, I will use in the future to find out what's happening.
-
improbabilitist
- Posts: 14
- Joined: Tue Nov 03, 2009 11:13 am
- Location: The Interwebz
Re: live only using one processor core
Hey, I think I have the same issue here.
I have glitches and CPU spikes beyond 110%, while having a quad core processor.
What's even more amazing, is that Ableton utilizes only 1 core!
My laptop specs:
Clevo M860TU (Clevo barebone, branded by XXODD)
Core 2 Quad q9000 (2.0GHz)
4GB RAM @ 1066
128GB SSD (Team Combo)
win7 Ultimate x64
Ableton Live 8.1
BIOS Settings (Advanced)
Installed O/S: Other (can choose between XP and Vista)
Legacy USB Support: Enabled
Boot Time Diagnostics Screen: Enabled
Legacy O/S Boot: Enabled
Reset Configuration Data: No
Power On Boot Beep: Disabled
Battery Low Alarm Beep: Enabled
Fan Control: Auto
My Ableton Preferences:
Driver type - MME/DirectX
Output Device - Speakers (Realtek High Definition Wave)
48KHz
SR & Pitch Conversion - High Quality
4096 samples
Plugin buffer size (default, As Audio Buffer)
Multicore support - On
Multicore Rewire - Off (have problems with rewire, but I don't think that should matter)
A little info on my test project:
Everything is in Ableton, everything is native (also no sends & returns are used)
After initial load of the project, Ableton CPU meter is idling on around 15%.
0. [MIDI] Kick (4 kicks in simpler, whole instrument rack and effects are disabled)
1. [AUDIO] Kick (resampled version of #0 in complex mode, RAM mode)
2. [MIDI] Synthlines - 1 Operators and 1 Analog with each their own effect rack (with no more than 6 effects each) - often disabled because I use #3 to save CPU.
3. [AUDIO] Resampled version of #2 (also in RAM mode)
4. [MIDI] Synth lead with 2 Analogs (frozen)
5. [GROUP] Cymbals
- 1 clap with an effect rack with couple of compressors
- 3 impulse loaded samples (all frozen)
6. [MIDI] Crashes (8 in the zone, whole track is frozen)
Also, when I keep #2 disabled and #3 running, it doesn't cause glitches as much.
As I've already mentioned, what's even more funny, is that while Live is around 120% CPU, only 1 of my cores get the full load. Overall CPU (if looked at the task manager) rarely gets past 30%
I've checked the affinity, and all cores are checked.
Though when I turn the Multicore support off, it gets considerably worse.
I am, what they call it, truly bedazzled
edit: I've also tried disabling WiFi, memory card controllers and DVD-drive.
edit2: I tried starting Ableton in Admin mode but I wasn't able to drag&drop files anymore, so hence I disabled it.
I have glitches and CPU spikes beyond 110%, while having a quad core processor.
What's even more amazing, is that Ableton utilizes only 1 core!
My laptop specs:
Clevo M860TU (Clevo barebone, branded by XXODD)
Core 2 Quad q9000 (2.0GHz)
4GB RAM @ 1066
128GB SSD (Team Combo)
win7 Ultimate x64
Ableton Live 8.1
BIOS Settings (Advanced)
Installed O/S: Other (can choose between XP and Vista)
Legacy USB Support: Enabled
Boot Time Diagnostics Screen: Enabled
Legacy O/S Boot: Enabled
Reset Configuration Data: No
Power On Boot Beep: Disabled
Battery Low Alarm Beep: Enabled
Fan Control: Auto
My Ableton Preferences:
Driver type - MME/DirectX
Output Device - Speakers (Realtek High Definition Wave)
48KHz
SR & Pitch Conversion - High Quality
4096 samples
Plugin buffer size (default, As Audio Buffer)
Multicore support - On
Multicore Rewire - Off (have problems with rewire, but I don't think that should matter)
A little info on my test project:
Everything is in Ableton, everything is native (also no sends & returns are used)
After initial load of the project, Ableton CPU meter is idling on around 15%.
0. [MIDI] Kick (4 kicks in simpler, whole instrument rack and effects are disabled)
1. [AUDIO] Kick (resampled version of #0 in complex mode, RAM mode)
2. [MIDI] Synthlines - 1 Operators and 1 Analog with each their own effect rack (with no more than 6 effects each) - often disabled because I use #3 to save CPU.
3. [AUDIO] Resampled version of #2 (also in RAM mode)
4. [MIDI] Synth lead with 2 Analogs (frozen)
5. [GROUP] Cymbals
- 1 clap with an effect rack with couple of compressors
- 3 impulse loaded samples (all frozen)
6. [MIDI] Crashes (8 in the zone, whole track is frozen)
Also, when I keep #2 disabled and #3 running, it doesn't cause glitches as much.
As I've already mentioned, what's even more funny, is that while Live is around 120% CPU, only 1 of my cores get the full load. Overall CPU (if looked at the task manager) rarely gets past 30%
I've checked the affinity, and all cores are checked.
Though when I turn the Multicore support off, it gets considerably worse.
I am, what they call it, truly bedazzled
edit: I've also tried disabling WiFi, memory card controllers and DVD-drive.
edit2: I tried starting Ableton in Admin mode but I wasn't able to drag&drop files anymore, so hence I disabled it.
Last edited by improbabilitist on Mon Feb 21, 2011 4:16 pm, edited 2 times in total.
-
Gregory Wells-King
- Posts: 249
- Joined: Sat Mar 03, 2007 6:46 pm
- Location: Somerset UK
- Contact:
Re: live only using one processor core
Your not using 'ASIO 4 All' Audio Driver that's not a solution to your problem necessarily just a statement, I'm suprized you've not chosen to download and install the good old free for nothing enhancement..Ave a go..improbabilitist wrote:Hey, I think I have the same issue here.
I have glitches and CPU spikes beyond 110%, while having a quad core processor.
What's even more amazing, is that Ableton utilizes only 1 core!
My laptop specs:
Clevo M860TU (Clevo barebone, branded by XXODD)
Core 2 Quad q9000 (2.0GHz)
4GB RAM @ 1066
128GB SSD (Team Combo)
win7 Ultimate x64
Ableton Live 8.1
BIOS Settings (Advanced)
Installed O/S: Other (can choose between XP and Vista)
Legacy USB Support: Enabled
Boot Time Diagnostics Screen: Enabled
Legacy O/S Boot: Enabled
Reset Configuration Data: No
Power On Boot Beep: Disabled
Battery Low Alarm Beep: Enabled
Fan Control: Auto
My Ableton Preferences:
Driver type - MME/DirectX
Output Device - Speakers (Realtek High Definition Wave)
48KHz
SR & Pitch Conversion - High Quality
4096 samples
Plugin buffer size (default, As Audio Buffer)
Multicore support - On
Multicore Rewire - Off (have problems with rewire, but I don't think that should matter)
A little info on my test project:
Everything is in Ableton, everything is native (also no sends & returns are used)
After initial load of the project, Ableton CPU meter is idling on around 15%.
0. [MIDI] Kick (4 kicks in simpler, whole instrument rack and effects are disabled)
1. [AUDIO] Kick (resampled version of #0 in complex mode, RAM mode)
2. [MIDI] Synthlines - 1 Operators and 1 Analog with each their own effect rack (with no more than 6 effects each) - often disabled because I use #3 to save CPU.
3. [AUDIO] Resampled version of #2 (also in RAM mode)
4. [MIDI] Synth lead with 2 Analogs (frozen)
5. [GROUP] Cymbals
- 1 clap with an effect rack with couple of compressors
- 3 impulse loaded samples (all frozen)
6. [MIDI] Crashes (8 in the zone, whole track is frozen)
Also, when I keep #2 disabled and #3 running, it doesn't cause glitches as much.
As I've already mentioned, what's even more funny, is that while Live is around 120% CPU, only 1 of my cores get the full load. Overall CPU (if looked at the task manager) rarely gets past 30%
I've checked the affinity, and all cores are checked.
Though when I turn the Multicore support off, it gets considerably worse.
I am, what they call it, truly bedazzled
-
improbabilitist
- Posts: 14
- Joined: Tue Nov 03, 2009 11:13 am
- Location: The Interwebz
Re: live only using one processor core
ASIO4ALL does make things a little better, but I would still have drop-outs and glitches.Gregory Wells-King wrote:Your not using 'ASIO 4 All' Audio Driver that's not a solution to your problem necessarily just a statement, I'm suprized you've not chosen to download and install the good old free for nothing enhancement..Ave a go..
I have it installed though, I'm just not using it because sometimes I surf the web and watch a youtube video, but since ASIO4ALL can only be utilized by 1 program I have to shut down my browser a lot of times in order to get on with Ableton.
I know, it's best to have a system dedicated to a DAW, but this is sadly my only computer
-
Gregory Wells-King
- Posts: 249
- Joined: Sat Mar 03, 2007 6:46 pm
- Location: Somerset UK
- Contact:
Re: live only using one processor core
I'm sorry to hear that.
No doubt, it's driving you crazy.
If it were an issue like this for me, I would start with the simplest set I can i.e, one track of audio. stick in one sample, check your task manager.
Then just start building upon it with more tracks, more samples, then devices, instruments etc, till you find the offending item.
Sounds like you've done this allready, so I guess some diagnostic bench test may be in order.

No doubt, it's driving you crazy.
If it were an issue like this for me, I would start with the simplest set I can i.e, one track of audio. stick in one sample, check your task manager.
Then just start building upon it with more tracks, more samples, then devices, instruments etc, till you find the offending item.
Sounds like you've done this allready, so I guess some diagnostic bench test may be in order.
Re: live only using one processor core
It sounds to me like this has been an isue for quite some time is there any indication that it will ever be fixed.
i am personally using live lite wich was bundled with an interface i purchassed if i had actualy purchased the full program i would be really irritated with this.
i am personally using live lite wich was bundled with an interface i purchassed if i had actualy purchased the full program i would be really irritated with this.
-
Street Spirit
- Posts: 73
- Joined: Thu Mar 18, 2010 10:56 pm
- Location: MI
Re: live only using one processor core
yeah same problem here too, running win xp sp3 AMD 2 core, live only runs on 1... not about to mess with bios.