Latest Live 8 version: Live 8.1 is online!

[Sly One]

I'm definitely switching back to 8.0.5 until the problems with 8.1 are sorted out.

Getting:

- Crashing when using certain combinations of VSTs
- The entire environment locking up and taking around a minute to respond to each click
- Almost all my old projects either crash live on load or lock it up.

New projects started in 8.1 generally seem ok as long as I don't use any VSTs!

Windows XP Home/Intel Quad/4gb/Firewire 1814/Virus TI/APC40/Oxygen8

[d-track]

im still on 8.0.5
very stable for me.
i would take the risk if at least a change log would be available.
abes seem to be on a skii holiday...

[Skylark]

What do we want? A Change Log
When do we want it? Now!

then audio goes silent and the program slows down like mad, unable to do anything without waiting for a few minutes...?

Have you got a PreSonus Fire Pod by any chance?

Now I feel crap answering yes...

[Skylark]

abes seem to be on a skii holiday...

hehe, maybe, but i did get a response from support yesterday afternoon, but at that stage live was working (IT WORKED FOR A WHOLE 10MINS, then died again)

They couldnt help me, just asked for the log file.

Hopefully will get a response today.

GOODLUCK YOU ALL!

[crumhorn]

^^^ I'll be very interested to know the outcome.

[ark]

Edit: narrowed it down a bit: if I just double-click on the first track's track name "1 Kit-White" so that the frozen device is displayed in the detail view, then the CPU load goes down to normal. All of this crazy behaviour while the track is not even playing yet. Something seriously buggy here... will post again in Support forum...

Edit: looks to be fixed with L8.1.1b1!

This looks a lot like the long filename bug.

The symptom is this: If you put a drum rack with a long name into a MIDI track, Live starts taking 100% of the cpu. Both of my machines are multi-core (so when I say 100% I really mean 50% on a dual-core machine and 25% on a quad-core machine), and on those, the program continues to work--but the GUI becomes very jumpy. I would think that the behavior would be truly wretched on a single-core machine.

As far as I can tell, this problem is fixed in 8.1.1b1.

[hoffman2k]

For all of you looking for the changelog(s):

Changes from Live 8.1 to Live 8.1.1b1
http://forum.ableton.com/viewtopic.php?f=35&t=130799

Changes from Live 8.1b9 to Live 8.1b10
http://forum.ableton.com/viewtopic.php?f=35&t=129807

Changes from beta 8 to 9
http://forum.ableton.com/viewtopic.php?f=35&t=129220

Changes from beta 7 to 8
http://forum.ableton.com/viewtopic.php?f=35&t=128533

Changes from beta 6 to 7
http://forum.ableton.com/viewtopic.php?f=35&t=127311

Changes from beta 5 to 6
http://forum.ableton.com/viewtopic.php?f=35&t=127311

Changes from beta 4 to 5
http://forum.ableton.com/viewtopic.php?f=35&t=126139

Changes from beta 3 to 4
http://forum.ableton.com/viewtopic.php?f=35&t=125366

[d-track]

not interested in betas

[Skylark]

looking forward to my response from ableton....

[hoffman2k]

looking forward to my response from ableton....

I hope you gave them more info than in that thread, otherwise it'll be a long wait.
You play a loop and stuff clips. Not very specific considering 90% of us have loops in our sets too.
My wild guess would be mismatching sample rates between 2 applications. But it could be anything.
All I'm saying is if Live did nothing else than clipping, you'd hear more about it.

not interested in betas

Regardless if you are or not, those are the changes.

[peeddrroo]

For all of you looking for the changelog(s):

Changes from Live 8.1 to Live 8.1.1b1
http://forum.ableton.com/viewtopic.php?f=35&t=130799

Changes from Live 8.1b9 to Live 8.1b10
http://forum.ableton.com/viewtopic.php?f=35&t=129807

Changes from beta 8 to 9
http://forum.ableton.com/viewtopic.php?f=35&t=129220

Changes from beta 7 to 8
http://forum.ableton.com/viewtopic.php?f=35&t=128533

Changes from beta 6 to 7
http://forum.ableton.com/viewtopic.php?f=35&t=127311

Changes from beta 5 to 6
http://forum.ableton.com/viewtopic.php?f=35&t=127311

Changes from beta 4 to 5
http://forum.ableton.com/viewtopic.php?f=35&t=126139

Changes from beta 3 to 4
http://forum.ableton.com/viewtopic.php?f=35&t=125366

would be nice to have the changelog from 8.0.9 to 8.1 without having to read bugfixes of the whole 8.1 beta testing.
especially for those who don't own m4l.

[hoffman2k]

For all of you looking for the changelog(s):

Changes from Live 8.1 to Live 8.1.1b1
http://forum.ableton.com/viewtopic.php?f=35&t=130799

Changes from Live 8.1b9 to Live 8.1b10
http://forum.ableton.com/viewtopic.php?f=35&t=129807

Changes from beta 8 to 9
http://forum.ableton.com/viewtopic.php?f=35&t=129220

Changes from beta 7 to 8
http://forum.ableton.com/viewtopic.php?f=35&t=128533

Changes from beta 6 to 7
http://forum.ableton.com/viewtopic.php?f=35&t=127311

Changes from beta 5 to 6
http://forum.ableton.com/viewtopic.php?f=35&t=127311

Changes from beta 4 to 5
http://forum.ableton.com/viewtopic.php?f=35&t=126139

Changes from beta 3 to 4
http://forum.ableton.com/viewtopic.php?f=35&t=125366

would be nice to have the changelog from 8.0.9 to 8.1 without having to read bugfixes of the whole 8.1 beta testing.
especially for those who don't own m4l.

Ableton usually posts a changelog in the announcement section when all beta's are finished. Since 8.1.1 is currently in beta, we probably wont see a changelog until its 8.0.9 to 8.1.1.
And when you see the changelog, it'll be these changes pasted into one list.

[sporkles]

The only problem I've been having with 8.1 is that accessing a specific chain in an instrument
rack via the mixer (clicking the arrow on the actual track, which lets you treat each chain as
an individual track) takes forever. Other than that, it seems fine, though I haven't really
pushed the envelope since the update.

[Skylark]

I hope you gave them more info than in that thread, otherwise it'll be a long wait.

if thats the case, then im super disappointed.

live 8.1 is completely useless to me, the program just doesnt work.

what is so unclear about my thread?

i load live, load any type of audio and press play, as soon as play starts there are continuous clipping sounds, from start until i stop (or till the program stops for me)

all support have done is ask for a logfile and i havnt heard back from them.

whats so difficult to understand?

and why do you think ill be waiting a while, is that common around here?

[hoffman2k]

I hope you gave them more info than in that thread, otherwise it'll be a long wait.

if thats the case, then im super disappointed.

live 8.1 is completely useless to me, the program just doesnt work.

what is so unclear about my thread?

i load live, load any type of audio and press play, as soon as play starts there are continuous clipping sounds, from start until i stop (or till the program stops for me)

all support have done is ask for a logfile and i havnt heard back from them.

whats so difficult to understand?

and why do you think ill be waiting a while, is that common around here?

No, you usually get a swift reply if they know more.
I mean, I could try to reproduce this problem and I did. I load an audio file, press play and it plays as it should. So where does one go from here in order to help you further? The log you sent them has some info on what was going on, but if its just the log then they still don't have enough data. A crashpack would have been useful but its not a beta. I do believe you can still do a bug report snapshot though.

Its not that your thread is unclear, it just doesn't contain the details to determine what is wrong. Its probably not Live 8.1 at fault but rather some setting somewhere. Support will help you fast if they can. My guess is, without details they have to wait till a more detailed report comes in or if you're lucky a similar report already came in and they're comparing notes.
I'm still betting on a sample rate issue. There are many ways the word "clipping" is used. Either you mean it in the audio sense where your waveforms are literally cut at 0dB. Or you mean you get a lot of clicks and garbled audio. Thats a sample rate mismatch or a sign of the buffer being too small.