Only one core working in Live 6, any solution?

Psykid · Post by **Psykid** » Fri Feb 09, 2007 2:40 am

I've been finding that live really dropsout whenever I start press play, then slowly recovers to normal operating status. The weird thing is that while Live is clicking out at like 90-100%, my cpu meter on my 2 X 2.66 Ghz Intel Xeon reads 50% at the most on any one processor. Multicore support is definitely working, I click it on and off and can notice the difference. However, I'm not convinced it's utililzing it to the fullest extent. Anyone got any ideas?

Thinktanx · Post by **Thinktanx** » Fri Feb 09, 2007 3:42 am

Nevermind, I'm a moron. It definitely works for me. Just tried it on a small session I had up. It has 3 tracks of audio (all warped), 1 MIDI track, 2 reverb return tracks.

Multiprocessor Support On: 16% CPU Usage
Multiprocessor Support Off: 24-25% Usage

So, sorry for my pigheaded mistake, Ableton. I could swear I tested it when i first got Live 6 and it didn't do anything, but it definitely does now.

rikhyray · Post by **rikhyray** » Fri Feb 09, 2007 10:19 pm

Received some interesting information from the support. Will put it to practice and see how things work.
They cleared why the rewire button stays gray. It is only relevant when Live is slaved.

cube · Post by **cube** » Mon Feb 12, 2007 10:42 am

I am using the Demo version 6.0.3 with my Mac Pro 2x2,66 GHz 2GB RAM OS X 10.4.8.

Whe I enable the Multicore/MultiProcessor, the CPU goes about 5-10% higher than the function disabled=singleCore or one processor.

This must be a bug or bad code?

I have 4 cores in my Mac Pro so it should be like 60% lighter for the CPU when MutiCore/Multiprocessor support is enabled.

Something is completely wrong here.

Ableton fix this fast please!

DJ VAKIS · Post by **DJ VAKIS** » Mon Feb 12, 2007 11:35 am

tylenol wrote:
Michael-SW wrote:I read here that that button does nothing. Live will use both cores anyway. But I'm too lazy to dig up the reference.
This button most definitely does something. Live will use both cores in some sense without it(the OS supplies some default behavior for apps that aren't optimized for multi-cores), but it won't use them very effectively. What this button does is tell live to really make use of the multiple cores.

To see the multi-core support in action, put a reverb in high quality mode on a track. This usually causes enough of a CPU bump to notice (on my core duo 2ghz it is 9-11%). Then put a second one on another track. The CPU will not change this time -- because live is running one reverb on each core (or doing something that amounts to that). If you turn off dual core usage you get almost twice the amount of cpu usage (it is a little better than twice, because the os behind live will be making some
feeble and inefficient use of the multiple cores).

This ok but,if you open the reverb on returns the cpu goes high.