Upcoming bug fix update Live 5.0.2! Wanna take a look...?
Upcoming bug fix update Live 5.0.2! Wanna take a look...?
Hi folks,
as you might already know we are going to release the bug fix update Live 5.0.2 in the next days.
Beside several bug fixes and improvements we also changed the clip transport to let it behave a bit more like in Live 4.
So it would be good if you could download the latest beta and try out for yourself how it "feels" now.
http://www.ableton.com/forum/viewtopic.php?t=27532
thanks and regards,
Alex
as you might already know we are going to release the bug fix update Live 5.0.2 in the next days.
Beside several bug fixes and improvements we also changed the clip transport to let it behave a bit more like in Live 4.
So it would be good if you could download the latest beta and try out for yourself how it "feels" now.
http://www.ableton.com/forum/viewtopic.php?t=27532
thanks and regards,
Alex
Last edited by Alex on Fri Oct 07, 2005 1:37 pm, edited 1 time in total.
-
philippe n
- Posts: 71
- Joined: Mon Oct 03, 2005 5:21 pm
- Location: France
- Contact:
-
Pandamonium
- Posts: 198
- Joined: Thu Jan 02, 2003 2:12 am
- Location: Cairns, Australia
- Contact:
As long as the freeze works without randomly deleting the frozen wavs (!!!!) at least it wil be an improvement over the current version which which I can't believe they released in the state it is in. Don't ableton have proffesional beta testers? Would hate to see them go the way of Steinberg and NI, up until version 5 Ableton have had a pretty good record for stable releases.
Visit Pandamonium Records homepage @ http://www.pandamonium.com.au
Site best viewed with stereo cranked.
Site best viewed with stereo cranked.
Hi Alex
if you end up doing another beta, would it be possible to take out the crash log code that eats CPU? It would be good to be able to test it as it will be (and we managed on the 3 and 4 betas without one, right!)
Alot of the tracks I have in the making are quite beefy and I usually like to try current sets in progress in a beta to make a fair comparison, but if I have not much time on my hands, if the CPU hit just pushes a track that bit too far it means I'm more likely to quit and load up 5.01 rather than persevering.
if you end up doing another beta, would it be possible to take out the crash log code that eats CPU? It would be good to be able to test it as it will be (and we managed on the 3 and 4 betas without one, right!)
Alot of the tracks I have in the making are quite beefy and I usually like to try current sets in progress in a beta to make a fair comparison, but if I have not much time on my hands, if the CPU hit just pushes a track that bit too far it means I'm more likely to quit and load up 5.01 rather than persevering.