Ableton Forum

Hi folks,

we just uploaded a beta version of the upcoming bug fix update Live 5.0.2.
This Beta is free for every Live 5 user.

Within this version we are really close to the final release of Live 5.0.2.
That means unless we did not "broke" anything this beta will correspond
to the final Live 5.0.2 version (probably coming at the end of next week).
This beta contains support for all languages including japanese language support but still does not contain any manual.

Use the following links to download the beta:

Mac: http://www.ableton.com/_common/download ... e502b8.dmg (18,4 MB)
Win: http://www.ableton.com/_common/download ... e502b8.zip (19,2 MB)


Please send all beta related feedback to [email protected].
Please also have a bit patience with us concerning your
[email protected] feedback. We try to answer all emails
but it needs its time.
Even though we will probably not be able to include your feedback into
Live 5.0.2 anymore please keep on sending it as this will not be the
last version of Live.


Current version: Live 5.0.2b8
Expire date: 2005-10-08

This versions has also some limitations:
- No manual is included
- No content is included

This version has enabled our bug reporter.
You will notice it when restarting Live after experiencing a crash.
Because of the crash reporter the "restore from undo.cfg" mechanism is
disabled in this beta.
Furthermore the Windows version has additional debug code to dump
information into the log file. Therefore the Windows version is a bit
slower as the final version (something between 5% to 15%).

When starting live 5.0.2b8 for the first time it should open the Beta lesson
which also contains the change log.


Kind Regards,
Alex



Change log Live 5.0.2b7 - 5.0.2b8

-----------------------------------------------------------------
[01] Bug: Changing clip properties
-----------------------------------------------------------------
Platform: All

Live could freeze when changing clip properties during a loop jump because a floating-point overflow. This was was introduced with 5.0.2b6.

Status: Fixed

-----------------------------------------------------------------
[02] Bug: Undo of "Insert Capture Scene"
-----------------------------------------------------------------
Platform: All

Under certain circumstances undoing of "Insert Capture Scene" would result in a crash.

Status: Fixed

-----------------------------------------------------------------
[03] Bug: VST plug-in presets
-----------------------------------------------------------------
Platform: All

The loading or saving of some VST plug-in presets would not work properly.

Status: Fixed





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

Sample Offset Bug - Live 5.0.2 b8

this is quite a serious bug, and it has existed through most of these
5.0.2 betas.

if i use a -1 sample offset in the first 16th note of any loop in the
"beats" warp mode, the loop's pitch and tempo are set back to original
during playback, as if i wasn't even warping at all.

OSX 10.4.2
12" Powerbook G4 1.5ghz, 1.25GB Ram

hey all,

Since 5.07 I can open a blank set, hit spacebar to start play, and open the TaskMan (win2k) to watch the memory just leak away. it literally climbs up by ~8k consistently when I do absolutely nothing.

we have confirmed this bug on win2k, windows xp sp2, and windows server 2003.

-nick

Hi nickb808,

Since 5.07 I can open a blank set, hit spacebar to start play, and open the TaskMan (win2k) to watch the memory just leak away. it literally climbs up by ~8k consistently when I do absolutely nothing.

How long did you run Live when monitored the memory consumption?
How much more RAM Live 5.0.2b8 consumes when a blank set is running for 30 minutes?

regards,
Alex

Hi Alex,

The memory consumption seems to start right away. I monitored it right off the bat. Then it seems to level off, and when i hit spacebar to start and stop again, it adds almost a meg to the memory sometimes then continues to climb.

One funny thing i noticed is that it will start off consuming about 118mb. THen when i minimize the window and re-maximize, RAM consumption drops to 18mb!

I am starting the 1/2 hour test right now.

-nick

I have noticed the same memory use on OSX tiger as well.Live doesnt seem to get rid of anything from memory. Other programs seem to use alot less memory and free it up when they have finished but when I use live my memory used always shows way higher amounts and it does not lower even after live has closed.
I hope you can check lives memory use out on OSX as well to make sure there isnt some sort of problem.

okay...here are my results of the half hour test.

live starts using 118mb of ram. minimize then maximize the window sheds 100mb of ram. (this could be because my default set has a few channels w/ vsts at the start.)

hit play w/ no clips running...live starts at 18mb and climbs a little. at this point i can hit start and stop to push it up to 40mb where it seems to level off. starting and stopping this set can add 1-5mb to the memory usage.

when i minimize the window again, it goes down to 13 mb usage then goes up to 24 immediately. then crawls up slowly again. starting and stopping make it go up to about 40-42mb ram and the slow crawl continues.

i don't know...maybe this is normal action or maybe there is some garbage not being cleaned up. i hope i'm not wasting developer time here.

thanks,
-nick

Okay, so I read abou the 5.0.2b6 with the "fixed" select on launch via midi/key assignments, so I capitulated and bought the upgrade to 5 now, and then downloaded the latest beta, b8. First I just tried to use it with the preferences and template set Live found from prior versions, but the select on launch via midi didn't seem to work. So I tried deleting the preferences and template files in the b8 folder, to start "fresh". I still get behavior like 4, select on launch does NOT work the first time you launch recording of a clip via midi. If you use a mouse yes it works, but not with midi. If you select a track (using the mouse) and delete it, then launch again via midi, it is selected, but that isn't the point. Can anyone verify this for me, that b8 doesn't do proper Live 3 style select on launch via midi? I definitely have it selected in the preferences menu, I did the delete prefs and templates to start fresh, I'm definitely using b8, but the select on launch is consistently not working.

Try it yourself. If it "seems" to work, try adding a new track, assining midi to the track luanch, arm and then launch recording of a clip. hit the midi pedal again to loop the clip, then try hitting delete to delete the clip--doesn't work. If you haven't clicked with the mouse on the clip slot (this includes just "highlighting" the clip slot, not just launching clips), then select on launch via midi does not work. Can anyone verify?

Ryan

nickb808 wrote:Hi Alex,

The memory consumption seems to start right away. I monitored it right off the bat. Then it seems to level off, and when i hit spacebar to start and stop again, it adds almost a meg to the memory sometimes then continues to climb.

One funny thing i noticed is that it will start off consuming about 118mb. THen when i minimize the window and re-maximize, RAM consumption drops to 18mb!

I am starting the 1/2 hour test right now.

-nick

I've had this problem since I first bought Live 5. Its also the reason I still use Live 4. It gets worse the bigger your set is, switching back between taskmanager (or just making Live lose focus i.e. minimizing) and Live will sometimes add around 200-400mb and will finally jump my RAM usage up to 1.8 gigs, where Live then gives me an out of memory error.

I've reported it already with some debug files sent to the Abes, but haven't heard anything back...

There are half a dozen posts in here about this as well.

Quandry, no issues here.. select on launch working like a charm with MIDI!

EDIT: I see what you mean, actually it seems to only work as long as the clip grid is in focus... no biggie for me tho, use the alt+arrow keys on the keyboard to put the grid in focus and it works fine for me

just want to chip in here as well - i've seen the memory leak issue. with no mention of a fix for it.
i'll try out hte latest demo during rehearsals for a show tomorrow and will report back whether its as bad as wtih the release version 5.01

Hi nickb808,

this behavior concerning memory with minimize and maximize you can already do with Live 4 but we we will investigate this for sure.
What me would interest is when you start Live with an empty set, start to play it and let it then run for half an hour without doing anything (no minimize - maximize, no other actions)... does Live then also consumes several MB more after half an hour?

regards,
Alex

Hey Alex,

Here are my results.

On start : 30,804 MB of memory taken
First 5 Min : 33,000
Next 5: 33,416
Next 5: 33,444
Next 5: 33,456
Next 5: 33,464
Final: 33,464

When I hit stop, it jumped to 35,736.

I moved the mouse 2 times to prevent the screensaver. Live 5.02b8 was the only app running aside from firewall/antivirus. It definitely hit a point where the increases were VERY small as you can see then appeared to stop.

-nick

Not a serious issue but can be confusing. It was there in 5.01, but only noticed it now...

When you have an audio clip and you're looking at the waveform (bottom), you get a little icon (speaker) so you can change the playhead position (i don't know what this thing is called and can't find it in the manual, sorry).
What's the issue? Well, when you click and hold the mouse down, the thing gets into repeat. Ok, that's what it has to do. Only thing is, the new starter position turns blinking orange only when you hit click. Once it's in repeat mode, it doesn't get orange anymore, unles you move your mouse a few pixels. This was it bit confusing at first.