Live 11 offers less than 50% of Live 10

[[jur]]

Ok so the indexing is most certainly done.
Could be the removed MaxFps option...
At this point I think you should write to support@ableton.com as I have no idea what it could be, sorry.
Interaction with Adobe software? This isn't impossible thanks to computer's magic, but I doubt it. You've tried with these softwares not opened, right?

[properLofi]

I’m running Ableton with everything apart from system daemons running.

Thanks for the tip, I’ll send a support ticket in and see what comes of it. I’m predicting it might take a while but I’ll update if I either hear anything back or find a reason for the issue.

[kyefox]

There's a similar thread on Reddit and, like here, everyone with problems seems to be on Intel. People with AMD chips don't seen to experience this. It might be an Intel-specific bug. I get good performance on my Ryzen 5 4500U/Vega 6.

[properLofi]

I don’t know if it’s just Intel to be honest. I saw the Reddit post but I’ve seen M1 issues which I think are to be expected but I’ve also seen AMD issues and plenty of people saying they have no issue on Intel chips. I’m sure it’ll probably boil down to a specific combination of factors for each user rather than a simple Intel bug.

[[jur]]

Something you can try too, that sometimes 'magically" solves issues is to re-install Live. Who knows..

[perrycomo]

have also had to end up freezing most tracks and setting buffer to 2mb to be able to mouse up a finished track. Reverting back to to L10 until either this is fixed or I have a good enough specced laptop again.

Lenovo T480s i7-8650ou @ 1.90gHz 16gb RAM

[perrycomo]

Something you can try too, that sometimes 'magically" solves issues is to re-install Live. Who knows..

Funnily enough I rebooted after a Win 10 update to find a "corrupt install", uninstalled, reinstalled, still ran like shit...

[omniphonix]

I noticed the same thing when I first fired up Live 11. I never had performance issues with 10 and I wouldn't expect to since I have a 14-core i9-7940X with 64GB of RAM. I got a drum track going in the native drum sampler, fired up the Roland Cloud TB-303 and got a pattern playing over it, then slotted in Vital and started getting the CPU light and very minor dropouts. I thought maybe it was because I had just updated Vital to 1.0.7, so I swapped it for Spire. Nope, same deal there (although a bit less frequent). Live 10 still runs smooth as does Cubase Pro 11 on the same machine. Something is definitely going on with the new version. I'm going to chalk it up to being an X.0 release, I'm sure they will work it out soon.

[properLofi]

I’d suggesting doing some formal testing and sending your findings to Ableton support. The more accurate info they have, the quicker they can find a solution.

[Pasha]

This post just made me curious as an owner of L11.
... so I made the same test after no indexing. I am running L10 and L11 with different Libraries. Those Libraries are on a SAMSUNG t5 Drive hooked via USB 3.0.

L10 : at 128 Tracks my CPU cannot keep up, at 64 it runs flawlessly
L11 : at 128 Tracks my CPU cannot keep up at 64 and 32 I got anomalous spikes in the 'Current' CPU indicator with Disk Overload and CPU Overload that occur when the demo set reaches bar 17. Although this does not affect the sound output it's VERY annoying and worrisome.
The anomalous spike is reproducible at the same bar and can reach 108% and in some of the tries @ 64 tracks... an unbelievable 204%.
The Average Indicator stays around 70% and the temperature of CPU is below 70 Celsius.
So, I think that something is wrong in the 'Current' load calculation, or it's not optimized/compatible for multi-core CPU of the past so it reads wrong. Given the information below you might notice that some CPU cycles are used for the USB 3.0 port but... why it does not light up in L10?

iMac 2013, 2.9 Ghz i5 CPU with 8GB RAM. macOS 10.14 latest patch.
(booting from external SAMSUNG SSD 840 as my internal drive is fried)
FW Audio card - core audio - no drivers.
Novation Launchpad MK1
M-Audio K61es Keyboard - core midi - no driver

Hope this helps
Pasha

[Calagan]

Hi ProperLofi

Your issue scared me because I've got almost the same setup as you and pre-ordered Live 11 last winter.
I just installed Live 11 alongside Live 10 and tested it all the day.

My conclusion is that my CPU use is absolutely the same in Live 11 and in Live 10.

I used the demo set from Live 10, and the CPU is truly the same.
I checked it on 2 or 3 different projects full of third party plugins, and it's still the same.
Because the CPU Meter in Live 11 is different (the default setting is a "peak meter" ("current"), and Live 10 legacy meter is more like a "RMS" meter), I compared watching the average metering, and listened too at which point I heard crackles.
I didn't find any difference.

My setup is a macbook pro mid-2012 (non-retina) 15 inches, i7 2.3 GHz, 16 Go RAM, NVIDIA GeForce GT 650M 512 Mo (discrete) & Intel HD Graphics 4000 1536 Mo (integrated). I run Mojave 10.14.6.

During my test, I used the discrete gpu, as adviced everywhere, by turning off the automatic graphics switching in preferences.

So the only difference between our setups seems to be that your macbook is retina, you have a better CPU and your discrete gpu has more RAM (1Go instead of 512Mo).
To me, it doesn't explain your problem, because we've got very similar machines (and your specs are even better).
It must lie in something else.

Did you use any internet app while using Live 11 ?
Did you turn off iCloud (I had some problems with this in the past, and needed to turn it off permanently because I had spikes randomly when icloud wanted to access internet, even with wifi turned off) ?

[properLofi]

I had all apps shut down while I ran the tests.

Did you try duplicating tracks in the test project? When opening it initially it didn’t appear to show a significant difference but when I started duplicating tracks is when I saw the choke point.

I’m willing to accept that this is situation specific for individuals who are seeing problems but I can’t see why 11 would interact differently with my system than 10. With all things being equal between tests it suggests something is significantly different with Live 11 not that there’s an issue with my machine or system. iCloud works just fine being active in 10, if it’s an issue in 11 it’s a bug. WiFi works with 10 if not 11 it’s a bug.

Bottom line if there’s that much less power in 11 on my system it sort of doesn’t matter why it’s a problem, but the way 11 works has changed from 10 because nothing within my hardware or software has changed.

[CancerRidden]

It literally just came out a few days ago, they're still working out the bugs and efficiency issues

[properLofi]

I totally get that they’re still working on bugs hence highlighting specific issues. I’m not saying 11 sucks, I’m saying performance sucks on my machine. If you don’t highlight issues how will they know what to fix. The more people who identify specific problems with specific systems the quicker we get a stable release.

[[jur]]

iCloud works just fine being active in 10, if it’s an issue in 11 it’s a bug.

What do you mean here with iCloud?? Are you storing and/or reading your user library or sets from here?