Ableton Forum

daizok wrote:

TheWholeDamnZoo wrote:I have a similar issue. I'm working on a project on which the CPU marker hovered around 30-50% in Live 9, and now in Live 10 it's around 90%. Even the default track that loads when you start up Live 10 goes past 90%. And I have an i7-8700K CPU with 16 GB DDR4-3000 RAM and I'm running Live (and most of my sound libraries) on an SSD. Anyone know what could be the issue?

That's not good. I'm running a pretty old I7 (4770) with 16GBDDR3 and the default 10 (suite) project (on SSD as well) hardly touches 10% CPU.

Hello [TheWholeDamnZoo], I had exactly the same situation but was solved after downgrading from Win10 to Win7, so I guess the problem is Windows 10.

daizok: You are completly right, I've made another thread talking about the best configurations for audio and I tell exactly this, my rig with an i7 3770 with 32gb DDR3 and SSD was working almost better than an i7 8700 with DDR4 3000 and SSD NVMe and that it's unacceptable. I start to gain anger for Windows 10.

Hey abletoners, I've just released a very simple M4L device that helps saving CPU power, eCo.
Hope this will help a bit.

Valiumdupeuple wrote:Hey abletoners, I've just released a very simple M4L device that helps saving CPU power, eCo.
Hope this will help a bit.

sweet.

I also confirm Live 10 is a CPU hog.
Projects from Live 9 barely play in Live 10.
Macbook Pro 2016 2.9 GHz Intel Core i7 / 16 GB 2133 MHz LPDDR3 / running on 10.12.6

For everyone interested: STRESS TEST [Ableton 10 + Windows 7]
******************************************************************************************************************

67 channels of heavy VST plugins and libraries running with only 16GB of RAM at 2900mhz for all the people that dare to say most of the times incorrectly, that you need more than 16GB for audio tasks. AND STILL ALMOST 4GB AVAILABLE! and don't forget to count the other software that was executed in the background as the system monitor Speccy and the DSP Checker, Firewall, etc.

SETUP: Ableton 10 + Windows 7 Ultimate (x64)
Intel i7 8700 4.3ghz
Corsair cooling H110i
16gb Corsair Vengeance LPX 2.900mhz
RME Hdspe RayDat (PCIe)
EVGA Nvidia GTX 1050 2GB
SSD Samsung 960 Evo 250GB
3 SSD's more running projects, libraries and samples.

DETAILS OF CHANNELS: each instance using a different patch totally random.
* U-he Diva:* 10 instances (in "divine" quality)
* NI Kontakt 5:* 10 instances
* NI Reaktor 6 / Monark:* 10 instances
* NI Massive:* 10 instances
* Spectrasonics Trillian:* 5 instances
* Spectrasonics Omnisphere 2:* 5 instances
* Xfer Serum:* 5 instances
* Arturia Minimoog V3:* 5 instances

Plus: 7 channels more of Reverb effects applied to all the channels
* Valhalla VintageVerb
* Valhalla Room
* Valhalla Shimmer
* Audio Damage EOS x64
* Audio Ease Altiverb 7

VIDEO:
*****************************
https://youtu.be/pvKoYGqSZLs
*****************************

Hey All - For what it's worth (I'm on a Macbook Pro with a discrete graphics card), I've disabled automatic graphics switching in System Prefs, and Live 10 is now handling much better. Give it a shot, if you haven't already.

You wold help us greatly by moving the benchmarking to the test forum at ableton.centercode.com

If preventing switching graphics in prefs resolves the problem , please file a bug report on this and attach your system details.

We have also released 10.0.2b2, available at ableton.centercode.com which includes improvements for HighDPI machines on windows. We will continue to improve the performance of Live 10 in our beta.

Same here. Unexplainable cpu spikes. When playing stuff and Live 10 uses 10 to 20 % CPU at one moment, it just starts jumping from 50 to 80 % the other with no reason.

papawise wrote:

daizok wrote:

TheWholeDamnZoo wrote:I have a similar issue. I'm working on a project on which the CPU marker hovered around 30-50% in Live 9, and now in Live 10 it's around 90%. Even the default track that loads when you start up Live 10 goes past 90%. And I have an i7-8700K CPU with 16 GB DDR4-3000 RAM and I'm running Live (and most of my sound libraries) on an SSD. Anyone know what could be the issue?

That's not good. I'm running a pretty old I7 (4770) with 16GBDDR3 and the default 10 (suite) project (on SSD as well) hardly touches 10% CPU.

Hello [TheWholeDamnZoo], I had exactly the same situation but was solved after downgrading from Win10 to Win7, so I guess the problem is Windows 10.

daizok: You are completly right, I've made another thread talking about the best configurations for audio and I tell exactly this, my rig with an i7 3770 with 32gb DDR3 and SSD was working almost better than an i7 8700 with DDR4 3000 and SSD NVMe and that it's unacceptable. I start to gain anger for Windows 10.

Thanks for the info! Unfortunately downgrading to Windows 7 is not an option for me currently.

Had The same problem,

Fixed it by setting energyconsumption in windows to high performance
Workflow is like butter now!!!

Cheers

I tested the CPU usage on my rig (see signature) using Live 10.0.1 trial:

The Live 8 test set needed about the same CPU power as in L 9.7.6 x64, on this machine about 11% with L 10.
I then used a set with many instances of "TrueVerb" (a Waves plugin) which ate only slightly more CPU cycles than L 9.
Finally I tested a set with many instances of Native Instruments Reaktor 5 FX which required 64% CPU usage in Live 9 and consumed about 69% CPU in Live 10.

So the outcome is dictated by the type of the set in question. Also, the kind of plugins used plays quite a role in the degree to which Live's CPU meter is being maxed out.
But as Ableton stated, in the ongoing evolution of Live 10 an attempt will be made to bring down the CPU usage of the application.

Things may improve even more so.

UnderwaterSunlight wrote:I tested the CPU usage on my rig (see signature) using Live 10.0.1 trial:

The Live 8 test set needed about the same CPU power as in L 9.7.6 x64, on this machine about 11% with L 10.
I then used a set with many instances of "TrueVerb" (a Waves plugin) which ate only slightly more CPU cycles than L 9.
Finally I tested a set with many instances of Native Instruments Reaktor 5 FX which required 64% CPU usage in Live 9 and consumed about 69% CPU in Live 10.

So the outcome is dictated by the type of the set in question. Also, the kind of plugins used plays quite a role in the degree to which Live's CPU meter is being maxed out.
But as Ableton stated, in the ongoing evolution of Live 10 an attempt will be made to bring down the CPU usage of the application.

i think this test is a lot more straightforward and telling than some of the elaborate tweaking testoramas i've seen so far.
based on these results... i think 5% is negligible and not worth wasting more brain power and/or music making time on.*


*results may vary... i know.

With 5% CPU increase, I could live. But not with erratic behavior boosting the CPU 5O% up. I'm on Mac OSX 10.12 btw.

As I said before:
• Live 9 cpu stays stable, 20 % doesn't become 40 % after a random period of time.
• Live 10 is stable for one moment, than the next the CPU increases from 20 % to any percentage between 50 and 90, with crackling and unstable audio as a result. Ironic, but this is totally unusable in live settings at the moment.

Sarrova-Q wrote: • Live 10 is stable for one moment, than the next the CPU increases from 20 % to any percentage between 50 and 90, with crackling and unstable audio as a result. Ironic, but this is totally unusable in live settings at the moment.

You also need to watch the CPU usage in the OS itself. The native meters only show what Live uses of what is available in the system. It's not a CPU meter. What background processes are running and could be using CPU? What are the processor settings regarding throttling? Just because Live 9 was fine with specific settings doesn't mean Live 10 will be.

In my experience of the beta — haven't installed the release yet — everything I do used less CPU (macOS 10.12 on a duocore). I'll try the release on a quadcore soon.

Stromkraft wrote:

Sarrova-Q wrote: • Live 10 is stable for one moment, than the next the CPU increases from 20 % to any percentage between 50 and 90, with crackling and unstable audio as a result. Ironic, but this is totally unusable in live settings at the moment.

You also need to watch the CPU usage in the OS itself. The native meters only show what Live uses of what is available in the system. It's not a CPU meter. What background processes are running and could be using CPU? What are the processor settings regarding throttling? Just because Live 9 was fine with specific settings doesn't mean Live 10 will be.

In my experience of the beta — haven't installed the release yet — everything I do used less CPU (macOS 10.12 on a duocore). I'll try the release on a quadcore soon.

In my case, the Windows CPU meter only shows 5% while the Live meter exceeds 100%. It wouldn't be a problem if it was just the meter but there's also crackling and increased latency.