Latest Live 8 version: Live 8.1 is online!

[Pasha]

OMG when I read this here I get the feeling that Live 8.1 is very unstable and full of bugs...

So, a few things:

1) There is no Live 9, so I'm not sure what you're talking about there.

2) Ableton's developers are only human and all software has bugs. There will never, ever, ever, ever be a 100% stable, bug-free piece of interesting software. Something as complicated as Live is going to have issues from time to time.

3) Despite #2... Yeah. Some releases are better than others, and maybe this was a not so good one, though I don't think this is a particularly large number of reported issues in the release thread (I can remember seeing more).

4) The thing to keep in mind is that this is a forum where people post when they have problems, so of course you're going to hear about them here. I can see how it would create a skewed impression of how stable Live really is. I would guess that the number of live users who are doing fine and who don't post here far outnumbers those who do. But those silent ones are benefitting from our helping Ableton make their stuff better, so it works out better this way.

Honestly, the 8.1/Supatrigga crashing thing that I've posted about is the first trouble I've run into with Ableton software in quite some time. Just keep in mind the source of your impressions/information when forming opinions!

Good point.
I would also like ot add that the announcement reads "The main focus of that 8.1 version is the release for the "Max for Live" product."
and no change log is in sight. Strange for a very precise company like Ableton. They also missed 8.0.9 change log or post it in the wrong place.
Sometimes upgrading is not necessary. Still on 8.0.4 here. It works why do I have to change if I won't get M4L or a Launchpad soon?

- Best
- Pasha

[sparkletone]

Good point.
I would also like ot add that the announcement reads "The main focus of that 8.1 version is the release for the "Max for Live" product."
and no change log is in sight. Strange for a very precise company like Ableton. They also missed 8.0.9 change log or post it in the wrong place.
Sometimes upgrading is not necessary. Still on 8.0.4 here. It works why do I have to change if I won't get M4L or a Launchpad soon?

- Best
- Pasha

Exactly! I think maybe the holiday for the US office might've delayed the changelog and stuff getting up too maybe? No idea.

Not a big deal, but yeah. You can install multiple versions of live on the same machine (Assuming they are library-compatible)... So always keep the old version around till you're sure you're not going to have any trouble with the new one, then delete it.

Also, no need to download stuff the minute it gets posted!

That said, I want Max4Live, so obviously 8.1 is necessary for me.

[Lamont]

I'm having midi sync issues with 8.1.
My Roland TB 303 goes out of sync when I insert return channels in my live sets.
When I restart Live 8.1 everything plays in sync again, but after a while it start running out of sync again.
I'll wait for update 8.1.1

[Migra]

8.1 Works great for me, just produced this remix of my friend Juan Carlos Portillo - Vae Victis (Migra Mystical Remix)

http://www.youtube.com/watch?v=hOouW-54Tms

I used 2 instances of FM8, 1 Reason's Thor rewired and lots of Audio FX, no problems here! Ableton rocks!!!!!

[ark]

Has anyone else noticed the following behavior?

Launch Live 8.1

Drag "Instruments/Drum Rack/Kit/Kit-GrainBeams(Operator)" to MIDI track 2.

Double-click one of the clip slots to create an empty clip.

At this point, Live starts looping: Windows Task Manager shows it as taking up 25% of the cpu, which means it is completely consuming one core of my quad-core processor. Response is very sluggish, as you would expect.

The cpu consumption doesn't start until I create the empty clip.

I've reported this problem, but don't expect a response until Monday.

[Sureno]

why no change log???

[kb420]

Has anyone else noticed the following behavior?

Launch Live 8.1

Drag "Instruments/Drum Rack/Kit/Kit-GrainBeams(Operator)" to MIDI track 2.

Double-click one of the clip slots to create an empty clip.

At this point, Live starts looping: Windows Task Manager shows it as taking up 25% of the cpu, which means it is completely consuming one core of my quad-core processor. Response is very sluggish, as you would expect.

The cpu consumption doesn't start until I create the empty clip.

I've reported this problem, but don't expect a response until Monday.

I can confirm that!

Everything worked fine up until I opened one additional drum rack and tried to record a new midi clip. The cpu was reading 15%.

Doesn't happen in 8.0.9.

[Migra]

why no change log???

+1

????

[S-N-S]

when will the update for live LITE 8 be ready??

[houseluna]

I am new to Max so i am not pushing it as much as you pros are out there but I can recreate a crash with following with 8.1

equipment:
mbpro late 2008 running 10.5.8 2.4Ghz. Core 2 duo 4 gigs of RAM
APC40, Korg PadKontrol, presonus Firebox I/O

using 5-7 max based effects, instruments etc. & 2-4 loops.

Click midi map and it crashes
afterwards on Relaunch it asks if you want to recover your project. I click yes and it says it can't open it.

Anyone else have this problem?

Glad I kept 8.0.4

I am sure Ableton is working on fixes.

[mode:masters]

I am late coming to this post and didn't have time to read all 5 pages, but I am having some issues regarding 8.1 and Launchpad use, as well as some strange crashes and extreme CPU usage in an empty set!

Quick history:

*New ASUS laptop (Pro77), legit XP SP3 installed freshly 3 weeks ago, updated to latest patches. Running Sapphire Pro 40 interface on a Belkin 1394 ExpressCard (TI Chipset).

*FRESH Live 8.09 install. no other plugins AT ALL. So far so good working great.

*Purchased Launchpad, later that day upgraded to Live 8.1 (thankfully left 8.09 in place).

Since I got the Launchpad I started a new set template for me and my partner to use, he will jam on the Launchpad, I will rock the APC40.

So far the set consists of 6 track groups, each one containing one or two audio/midi tracks, all sending to master, NO EFFECTS AT ALL. Then there is a dedicated channel for Launchpad input, as well as 2 feedback tracks. One track receives MIDI from the dedicated Launchpad track and sends back to Launchpad for visual feedback. The other has one clip in it that send note data to the Launchpad to run a 4 step metronome and has no MIDI input. I also have one other MIDI channel set to recieve from my Sapphire Pro, which has my MIDI keyboard attached to it.

FIRST PROBLEM: I had two return tracks (Default A&B), both had nothing in them. When I delete the B track all good. Try to delete the A track, Live crashes immediately. Note that I have ZERO audio clips in the set and ONE MIDI clip providing the metronome to the Launchpad. Any further attempts to open the set and remove send track A result in an instant crash.

SECOND PROBLEM: With the set playing and the Launchpad track enabled, switching between Session and User1 modes on the Launchpad results in extreme CPU spikes (200% +). All this with no audio playing in the set. So essentially I cannot change modes during a set.


Now I can't say the Launchpad mode switch issue started with 8.1, but the crashing definitely has.

I have successfully re-created this in a new set. What is up with 8.1???

PLEASE PLEASE PLEASE CAN WE HAVE A 8.1 CHANGELOG?

[Angstrom]

Just a quick note that anyone experiencing bugs like this should also contact [email protected]
They do visit the forum, and it's a good way of promoting the visibility of common issues, but mailing support is the primary way of alerting Ableton themselves.

oh and remember to follow their guidelines for reporting the bug, because they will not be able to address the issue if it isn't described well enough. Here's how:

http://www.ableton.com/pages/support/co ... al_support

[cotdagoo]

PLEASE PLEASE PLEASE CAN WE HAVE A 8.1 CHANGELOG?[/b]

i think it's up to beta 15 now.. just a few more days of testing before the changelog for a 600mb .1 update might be ready for public consumption

[kb420]

8.1 = FAIL!

[8O]

There is something seriously wrong with 8.1 + the Acid-Pauli liveset. Loading it up, the Mac CPU monitor goes up over 100% for the Live app (while Live's own CPU monitor stays low). Live takes 3 seconds or so to respond to each mouse click. I mucked around a bit and then it went away after a minute or so... but something seriously not right here...

MBP / 10.6.2 / L8.1

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!