Page 6 of 7
Re: Bugfix update 8.0.5 available
Posted: Thu Sep 24, 2009 5:48 pm
by slowdancer
i'm stickin to 8.0.4 until memory issues get addressed. ableton was kind enough to issue me a license for the latest 7 version, which i haven't used yet. they're cool like that.
Re: Bugfix update 8.0.5 available
Posted: Thu Sep 24, 2009 7:51 pm
by FadY
I get a lot of crashes on the track I am working on at the moment. I can't even kill it... It stays in the task list. This is very annoying I would be happy to just be able to kill it and launch it again.
Re: Bugfix update 8.0.5 available
Posted: Thu Sep 24, 2009 8:21 pm
by pwal
projects that run fine in 804 are covered in pops & crackles in 805
(amd-x2 lappy w/xp32sp3 +apc40)
Re: Bugfix update 8.0.5 available
Posted: Thu Sep 24, 2009 11:33 pm
by SKerkewitz
Hmm, something is definitive odd with 8.0.5: i have a very little project. Just some drums (using a simpler for each channel), one instance of NI Massive and one instance of NI FM8. Everything works fine as long as i not touch any settings on Massive. If i change the present or even turn on/off a LFO in Massive my CPU usage jumps from 9% to about 160%. I did no have this behavior in 8.0.4 and Live is the only thing that i changed recently. If i kill Live using the task manager and load the project again its back to about 9%. But as soon as i touch Massive i'm back to 160%.
PS: I know my Vista x64 is not offical supported and i also know that maybe the NI stuff is the problem - anyhow, it did worked in 8.0.4.

Re: Bugfix update 8.0.5 available
Posted: Fri Sep 25, 2009 11:09 am
by Hermanus
More testing here with Molar vst, monomulator, apc40 and 8.0.5.
I recorded another project and all was fine before and after having recorded the set.
It gently stays at 20%/30% with all audio tracks. me happy
I will try to figure out what was the thing which caused problems on my previous set [maybe some third-party vst].
I tested both previous and present projects on my laptop which is a bit faster than my desktop computer.
I really enjoy the speed for project Loading... it's like Light speed compared to 8.0.4_
Well more 804/805' testing on the weekend for sure

Re: Bugfix update 8.0.5 available
Posted: Fri Sep 25, 2009 11:25 pm
by Eddie Knucks
I am not a Suite owner but downloaded the suite update by mistake. Should I do something to correct this?
Re: Bugfix update 8.0.5 available
Posted: Sat Sep 26, 2009 9:28 am
by pwal
pwal wrote:projects that run fine in 804 are covered in pops & crackles in 805
(amd-x2 lappy w/xp32sp3 +apc40)
hm, it seems my hw driver got reset, and there's a buffer option that introduces p& c... 805 is playing nicely now
Re: Bugfix update 8.0.5 available
Posted: Mon Sep 28, 2009 8:35 pm
by punching_sandwiches
Gahh. So I install the new suite version. I continue working on a session I've been doing.
Covered in pops and crackles! And even worse all my M-tron work pitches randomly when bounced down!
And even worse, even worse it won't let me open the file in my previous version 8.0.1!!!
What do I do??
This track is on a deadline.
Will 8.0.4 let me open the file? If so where can I download it?
Please help
I am using an Mbox 2 for sound card and running a quad core intel Mac with OSX 10.5.6
Re: Bugfix update 8.0.5 available
Posted: Mon Sep 28, 2009 8:47 pm
by Anubis
Eddie Knucks wrote:I am not a Suite owner but downloaded the suite update by mistake. Should I do something to correct this?
Pay for it you sloth!

Re: Bugfix update 8.0.5 available
Posted: Wed Sep 30, 2009 7:28 pm
by Hermanus
punching_sandwiches wrote:Gahh. So I install the new suite version. I continue working on a session I've been doing.
Covered in pops and crackles! And even worse all my M-tron work pitches randomly when bounced down!
And even worse, even worse it won't let me open the file in my previous version 8.0.1!!!
What do I do??
This track is on a deadline.
Will 8.0.4 let me open the file? If so where can I download it?
Please help
I am using an Mbox 2 for sound card and running a quad core intel Mac with OSX 10.5.6
You can open a project made on 8.0.5 with every 8.0.x from the first 8.0.1, no problem at all

Re: Bugfix update 8.0.5 available
Posted: Thu Oct 01, 2009 5:29 pm
by FadY
I am back to 8.0.4...
Getting crashes while browsing samples... CPU goes to 300% without playing anything.
8.0.4 is OK on the same set.
the good news is that support team has good reactivity they are on it. I hope they will find a solution
Re: Bugfix update 8.0.5 available
Posted: Fri Oct 02, 2009 12:03 pm
by Hermanus
glad to hear it
Re: Bugfix update 8.0.5 available
Posted: Mon Oct 05, 2009 2:24 am
by glitchrock-buddha
33tetragammon wrote:N.I.'s Kore 2 still has parameterjumps in Live 8.05.
posted it in the beta bugs forum.
back to Live 7.016
"sigh............."
Try something, let me know if it works:
Whatever parameters you are tweaking and that are jumping, configure them in the live device. Once they are configured (Ie. visible for automation), do the jumps still happen?
I think there is something very wrong in Live with plug-ins who's parameters are not 'configured'. Automap VSTs parameters jump all over the place unless you configure them. Zebra's eq parameteres jump, until you configure them. And Kore seems to do the same. I don't know what it is, but it's a problem new to Live 8, that only seems to occur when parameters are not visible to automation in Live.
Re: Bugfix update 8.0.5 available
Posted: Mon Oct 05, 2009 6:29 pm
by kryz
Well, I get some horrific cpu spikes too on 8.0.5. What I don't get is: Why don't they test these updates properly before releasing them as official updates? This is totally unusable in any live setting. I thought that was what beta versions are about... I'm really tired about doing their testing after having paid a lot of money for their program. It's supposed to work flawlessly for Christ's sake. Come on Abes, get it done now, will ya?
Re: Bugfix update 8.0.5 available
Posted: Wed Oct 07, 2009 4:58 am
by FadY
kryz wrote:It's supposed to work flawlessly for Christ's sake.
Well... It's been a while that this is not true in the computer domain....
A part of the money you paid is provided to the support team to correct bugs.
Actually I reported this to the support and sent my live set and my vst folder but they were not able to reproduce it...
The problem with this sort of bug is that they are hard to reproduce, isolate and correct...