Is anyone else experiencing lag in live with 8.1?

[outershpongolia]

Upgrading to 8.1 also changed my libraries so now there is no going back. I cannot work with my projects under these lagging and freezing conditions. So for now I'm using Logic to preserve my creativity.

Thats where my confusion was.. Everyone said keep the previous version and when you save save a new set instead of overwriting that way you have a live set that still works in the previous version..

This is all good, but what about the Library? No one tells you to make a second library, and if you don't, you might as well trash the previous version and those saved live sets because if you update the library you're screwed either way..

[filterstein]

Upgrading to 8.1 also changed my libraries so now there is no going back

first, always make sure you have a backup of your library before you upgrade.

But i think you can go back:
- rename your current library when live is not running
- start live 8.09
- it wil nag about the library.
- give it a new location from the preferences menu
- live will build a new one
you could also try to repair it with the repair option

[oberflaechlich]

super slow and sticky here. i think the 8.1 change log will read "given valium"

[Veiss]

I'm only experiencing the lag when using multiple drum racks with varying number of samples... Drum racks always slow shit down for me. Running a 3.06 GHz macbook pro with 4gb of ram. Nothing else slows live down..

[jessemiller]

yep, same problem with drum racks. supposedly the beta version fixes this, but i can't say because i can't get beta 8.1.1b3 to start.

[eliteforce]

The latest Beta version? First crash after 239 secs. Second crash after 421 secs. Third crash after 207 secs. Repeat to fade.

[Guillotine]

I upgraded to 8.1 before buying Max for Live, and now I'm having similar time lag issues. I'm extremely frustrated and disappointed with the software upgrade, and I PRAY these issues will be resolved quickly, as LIve has been rendered completely useless by these timing issues...... A track I had been arranging in 8.0.8 (with zero problems on my MBP/snow leopard) at about 35%CPU is so sluggish in 8.1 that: it takes 2 seconds for the software to respond to any mouse clicks; the scrolling is off by about 2 bars; and the audio skips. Basically it's a disaster.

I had no idea what I was getting myself into when I upgraded to 8.1.... Is 8.1 officially a "beta"? Is that a way of saying "there could be huge problems"? And if 8.1 is a beta, why isn't there a warning?

I strongly recommend not installing Live 8.1. At all costs, really.

I guess all I can do now is sit back and wait for these bugs to be fixed, or I can work on a much smaller project. Unless someone has a fix (let me guess trash preferences).

[Todd_Perry]

I've been experiencing this lagging under windows as well so it's not a Snow Leopard problem.

The kind of lag I have been experiencing is pretty wierd, and all seems to link back to the GUI. Audio continues as normal but is just slow to react. ANY editing commands take forever. The manual says that the CPU usage meter shows usage by the audio engine but not by the GUI. The live CPU meter says 1-2% but the windows CPU meter is maxed out.

Another thing I've noticed is that it only seems to happen when you open an 8.0.x set. If you start a clean set on my system and start from scratch everything seems to be normal! Very strange....

[jazzelias]

Same issues here MacBook Pro (late 2008, 4GB ram, Snow Leopard 10.6.2):

After starting 8.1 and opening a project with about 50 scenes in 4 audio and 2 midi tracks Ableton used 100% CPU as long as I didn't kill the process.

Once I waited about 20 min in order to see if it works finally but the user interface was most of the time freezed. When I managed to start the music it was nearly impossible to stop the music again because of the not responding UI.
For that project I didn't used any external VST, only Ableton effects.

I went back to 8.0.9 and everything is working fine. I'll give 8.1.1. a chance. However things like this shouldn't happen.

[eliteforce]

Personally I think what would be really helpful from software developers is some kind of recognition and explanation to their customers when a major issue like this arises, and perhaps withdrawing the Mac update (at least) from their site whilst they convert it into a usable update would be a good starting point. Once you've done a little work on a project with the new version (which was suggested to me by Tech Support given the issues I'd been having with 8.0.9 I might add), the lack of any backward compatibility means you are stuck with using the latest version, even if it's less use than a beta.

[H20nly]

Same issues here MacBook Pro (late 2008, 4GB ram, Snow Leopard 10.6.2):

After starting 8.1 and opening a project with about 50 scenes in 4 audio and 2 midi tracks Ableton used 100% CPU as long as I didn't kill the process.

Once I waited about 20 min in order to see if it works finally but the user interface was most of the time freezed. When I managed to start the music it was nearly impossible to stop the music again because of the not responding UI.
For that project I didn't used any external VST, only Ableton effects.

I went back to 8.0.9 and everything is working fine. I'll give 8.1.1. a chance. However things like this shouldn't happen.

What about your library? Can you go back?

[jessemiller]

I'm having the same problem. Unfortunately I started in 8.0.9 a couple weeks ago and then upgraded and didn't realize I needed to save my session separately to be able to open it in 8.0.9. I can't get the beta version started either. Its quite frustrating to work this slow.