Live 2.1.2 is online!!!
Live 2.1.2 is online!!!
Hi folks,
like announced we just uploaded the Live 2.1.2 version,
availabe here: http://www.ableton.com/downloads
This update fixes 3 problems:
[all platforms]
1. The memory leak problem when using the "Render to disk"
[Win only]
2. The zoom, (browser)prehear and record freezes experienced under Windows
[OS X only]
3. Problems with wrong access rights of the application support folders in which result
Live was not able to start.
Concerning the Live 3 beta, it will be released in the next days, so stay tunded, cause we need your feedback.
Happy weekend
kind regards,
Alex
like announced we just uploaded the Live 2.1.2 version,
availabe here: http://www.ableton.com/downloads
This update fixes 3 problems:
[all platforms]
1. The memory leak problem when using the "Render to disk"
[Win only]
2. The zoom, (browser)prehear and record freezes experienced under Windows
[OS X only]
3. Problems with wrong access rights of the application support folders in which result
Live was not able to start.
Concerning the Live 3 beta, it will be released in the next days, so stay tunded, cause we need your feedback.
Happy weekend
kind regards,
Alex
Last edited by Alex on Thu Oct 09, 2003 9:35 pm, edited 1 time in total.
Re: Live 2.1.2 is online!!!
I can't find a thread on that problem........is it an issue on Mac 9.2.2 and if so what are the symptoms..??Alex wrote:Hi folks,
This update fixes 3 problems:
[all platforms]
1. The memory leak problem when using the "Render to disk"
kind regards,
Alex
Thanks
I don't know if this is the bug in question, but this morning I was seeing some weird CPU-overload behavior on a very simple track in OS X (on both a 500mhz G3 and a 1.2ghz G4.) The CPU meter would periodically jump to ridiculously high values and audio would drop out, once every 10 seconds or so. After installing 2.1.2 that problem seems to be gone.
yum
my first impression: 2.1.2 is the serious funk version version !
gareet!
[ ]
gareet!
[ ]
The File browser bug dissapeared on my system with this version.
What a relief!!
Ableton you really can't have such a mess again, as it was with the whole V2 affair.
I think the public beta test for V3 is the way to go.
You have to be careful no to introduce new bugs after finishing the final beta with adding new (untested) features.
regards,
Steve
What a relief!!
Ableton you really can't have such a mess again, as it was with the whole V2 affair.
I think the public beta test for V3 is the way to go.
You have to be careful no to introduce new bugs after finishing the final beta with adding new (untested) features.
regards,
Steve
Hi speedbird,
like Bernd already mentioned in his posting the main problem with this bug was that is was difficult to reproduce it. After we could reproduce this one, it took some hours to fix it.
We don't add features after a final beta. As example, this browser bug was in all 3 beta versions of Live 2.1 but we just got the bug report from raapie at the end of version 3 and failed to reproduce it.
So it's really important to get as many user testing the beta as possible.
Please have also in mind that the beta is free, which means everybody, Live user or non Live user, can test it. So if you have friends not knowing what to do, they are welcome :)
regards,
Alex
like Bernd already mentioned in his posting the main problem with this bug was that is was difficult to reproduce it. After we could reproduce this one, it took some hours to fix it.
We don't add features after a final beta. As example, this browser bug was in all 3 beta versions of Live 2.1 but we just got the bug report from raapie at the end of version 3 and failed to reproduce it.
So it's really important to get as many user testing the beta as possible.
Please have also in mind that the beta is free, which means everybody, Live user or non Live user, can test it. So if you have friends not knowing what to do, they are welcome :)
regards,
Alex
So far so good
Live 2.1.2 seems to be much more stable on my PC than 2.1.1, which was unusable, lockups, etc. I had one lock-up today but I think it was due to an older VST plug P4 denormal thang.
Nice work, thanks a lot for taking care of bidness...
Nice work, thanks a lot for taking care of bidness...
;-)
well, the more serious bug was with cliprecording, which in 2.1.2. seems to work again. 2.1.2 is a brilliant program in my opinion. I really love the way Live feels, but this version can do the things I need.
Thanks again Ableton.
Thanks again Ableton.
tempo changes still cause horrid cpu spikes
Hi, most of the problems seem fixed with live 2.12
the only problem i still have, is that if i change the tempo in my main host while the song is playing, i get horrendous cpu spikes..i tried this in acid pro4 and logic 5.51 (the acid one was just to test if it would be the same)..
is this a rewire issue? i am just thinking it might be hard to do tempo changes within a track as the cpu might overload...
can someone please shed light on this?
thanks.
the only problem i still have, is that if i change the tempo in my main host while the song is playing, i get horrendous cpu spikes..i tried this in acid pro4 and logic 5.51 (the acid one was just to test if it would be the same)..
is this a rewire issue? i am just thinking it might be hard to do tempo changes within a track as the cpu might overload...
can someone please shed light on this?
thanks.
no spikes
I am having no trouble with Reason and Live and tempo changes under 2.1.2 Even on very busy songs (lots of effects in Live, lots of devices in Reason) a tempo change sounds great.
Might be your system. Have you tried it with version 2.0.3 ? In my opinio 2.1.2 solves the bugs of 2.0.3 and works fantastic.
Good luck.
Might be your system. Have you tried it with version 2.0.3 ? In my opinio 2.1.2 solves the bugs of 2.0.3 and works fantastic.
Good luck.
Hi pazzap,
some questions about the CPU spikes,
1) Do you get these spikes also when you have just one clip running in Live without any effect (no ableton, no vst).
2) Do you get the spikes just with a special ableton effect or a special VST plug
3) What type of tempo change to do you make? A slowy but continous one or a really fast one more like a tempo jump?
regards,
Alex
some questions about the CPU spikes,
1) Do you get these spikes also when you have just one clip running in Live without any effect (no ableton, no vst).
2) Do you get the spikes just with a special ableton effect or a special VST plug
3) What type of tempo change to do you make? A slowy but continous one or a really fast one more like a tempo jump?
regards,
Alex
hi all,
I 've used Live 2.0.3 during the summer during shows we did with our band, mainly as a set arrangement (sort of a computerised eight track).
The arrangement lasts for about an hour (1700 bars). It comprises a lot of seperate clips (most of them 8 or 16 bars long) of the submixes of our album, since it was my initial plan to change scenes on the fly. The live session is therefor rather big (1.1MB).
The 2.1.1 and 2.1.2 version won't open the same 2.0.3 session anymore. because of "not enough memory". Before, I had allocated 197 MB to the 2.0.3 version. Even if I give like 220 MB or even higher to the newer version it still won't open. There's 512 MB in my Tibook and I was careful to leave the system still enough memory to expand into. Nothing helps .. Do the 2.1.1 and 2.1.2 versions need that more memory? Can't believe that... Is it a bird, is it a plane, is it a bug......?
Any thoughts about this, Ableton crew?
kind regards
I 've used Live 2.0.3 during the summer during shows we did with our band, mainly as a set arrangement (sort of a computerised eight track).
The arrangement lasts for about an hour (1700 bars). It comprises a lot of seperate clips (most of them 8 or 16 bars long) of the submixes of our album, since it was my initial plan to change scenes on the fly. The live session is therefor rather big (1.1MB).
The 2.1.1 and 2.1.2 version won't open the same 2.0.3 session anymore. because of "not enough memory". Before, I had allocated 197 MB to the 2.0.3 version. Even if I give like 220 MB or even higher to the newer version it still won't open. There's 512 MB in my Tibook and I was careful to leave the system still enough memory to expand into. Nothing helps .. Do the 2.1.1 and 2.1.2 versions need that more memory? Can't believe that... Is it a bird, is it a plane, is it a bug......?
Any thoughts about this, Ableton crew?
kind regards