Ableton Forum

Hi folks,

we just released the bugfix update Live 5.0.2.

Just check the download section on our website or use the 'Check for Updates...' entry from Live's help menu.

A very big thanks to all people participating on the 5.0.2 beta period.
I did not yet managed to answer all mails sent to [email protected] but
I will try to catch up on everything in the next days.



Two notes:

1)
To all Live 5.0.2 beta tester, please keep in mind that the final Live 5.0.2
version copies the preferences from the last final Live version (Live 5.0.1)
but not from any beta version.

2)
Because a bug fix related to the latency information provided from the audio interface
you might have to reset your 'Overall Latency' value in the 'Audio' section of
Live's preferences.


Kind Regards,
Alex



Change log Live 5.0.2b8 - 5.0.2

-----------------------------------------------------------------
[01] Bug: Memory leak
-----------------------------------------------------------------
Platform: All

Depending on the audio buffer size, the number of audio clips within a Live set and the number of audio clips with the 'RAM' switch activated there was a memory leak which could in a worst case increase the memory usage because an overflow in an internal queue.

Status: Fixed

-----------------------------------------------------------------
[02] Bug: Sample offset modulation
-----------------------------------------------------------------
Platform: All

A negative sample offset modulation would not work properly at clip start.

Status: Fixed

-----------------------------------------------------------------
[03] Bug: Browser: Recursive alias
-----------------------------------------------------------------
Platform: All

Under certain conditions with recursive folder aliases Live would freeze when switching the browser root up.

Status: Fixed

-----------------------------------------------------------------
[04] Bug: Filter-curve views
-----------------------------------------------------------------
Platform: All

Filter-curve view would not displayed properly after a sample rate change.

Status: Fixed




Link to the annoucement of Live 5.0.2b8
http://www.ableton.com/forum/viewtopic.php?t=27532

Link to the annoucement of Live 5.0.2b7
http://www.ableton.com/forum/viewtopic.php?t=27196

Link to the annoucement of Live 5.0.2b6
http://www.ableton.com/forum/viewtopic.php?t=26978

Link to the annoucement of Live 5.0.2b5
http://www.ableton.com/forum/viewtopic.php?t=26554

Link to the annoucement of Live 5.0.2b4
http://www.ableton.com/forum/viewtopic.php?t=26266

Link to the annoucement of Live 5.0.2b3
http://www.ableton.com/forum/viewtopic.php?t=25938

clap clap clap clap !

so this is no longer a beta?

So does the Freeze feature work now without deleting the frozen wavs the next time you open the project?

so does that mean the clip transpose doesn't need to be in ram mode in order to be real time rather than always having 1 bar latency?

thanks a lot ! i had a bug and it is resolved

So when are we getting some new features?

hoffman2k wrote:So when are we getting some new features?

Thanks Alex... and all the team

Alex wrote: 2)
Because a bug fix related to the latency information provided from the audio interface
you might have to reset your 'Overall Latency' value in the 'Audio' section of
Live's preferences.

Quick question about this...

I'm using the M-Audio Ozonic interface, set to buffer size 256 samples...

In 5.0.1 latency is reported as 9.0 + 6.0 = 15.0ms

In 5.0.2 it is reported as 9.52 + 6.89 = 16.4

Is there a problem here, or is it simply that 5.0.2 is reporting with greater accuracy?

Thanks

Hi headquest,

In 5.0.1 latency is reported as 9.0 + 6.0 = 15.0ms

In 5.0.2 it is reported as 9.52 + 6.89 = 16.4

Is there a problem here, or is it simply that 5.0.2 is reporting with greater accuracy?

This was part of the bug fix. In Live 5.0.1 the latency values are truncated so the values reported in Live 5.0.2 are the ones with higher accuracy.


regards,
Alex

Great! Thanks for the confirmation (and the fix, of course!)

Awwww!!! I still have a memory leak in 5.0.2

Switching back and forth from Live to taskmanager then back to live eats up 200mb + each time I do it... Only with my bigger sets though, other ones work fine now!

-tim

Hi timothyallan,

Switching back and forth from Live to task manager then back to live eats up 200mb + each time I do it... Only with my bigger sets though, other ones work fine now!

When monitoring the memory consumption in the task manager please watch the virtual memory size.

Are these 200MB added each time you switch back to Live in a Live session so that if you do this 5 times it add 1GB?
Or does it happen just once in a Live session?

regards,
Alex

Hi Alex, I did this 2 minutes ago with 5.0.2.

Please note that this has been identical ever since I bought Live 5, and is the reason I am still forced to use 4 for all my 'Live' gigs!

I just loaded the set, click off Live onto something else(for this instance it was taskmanager), then back onto Live. Live then uses 100% processor while it rescans everything, then the ram increase happens. I did it 3 times here, but I can keep doing it until I hit my physical limit (2gb RAM), and Live gives me an out of memory error.





There are no other programs running in the background and only a few vsts are used on the output bus, the rest is audio and impulse.

Thanks for your time,
Tim

Hi timothyallan,

- please send me the Live sets where it happens (only the .als, no samples).

- please also check if it happens too when removing the used VSTs temporarily

- please check if it also happens when the Live set is playing while you switch between Live and another application.

regards,
Alex