Ableton Forum

When Live plays and you click delete midi track you get BAAAAANNNG and total freeze.Is it kind of permanent bug that will never be resolved ? I remember it in ver 4, and I thought it was corrected, now it happened few times and that crash is truly big bang one with annoing noise etc. Maybe even worse then in Live 4
I woudnt wish anyone to do it accidentaly live, people would lynch you.
If it is not possible to fix it then at least make some kind of warning or security, or block the option of deleting midi track making it possible through some menus. The way it is now it is freaky .

Hi rikhyray,


some questions:

1) On which computer platform and operating system you are?
2) Do you refer to Live 5.0.1?
3) What do you mean with "click delete midi track"? The 'Delete' entry in the 'Edit' menu?

regards,
Alex

Alex wrote:Hi rikhyray,


some questions:

1) On which computer platform and operating system you are?
2) Do you refer to Live 5.0.1?
3) What do you mean with "click delete midi track"? The 'Delete' entry in the 'Edit' menu?

regards,
Alex

1 XP home SP2, Vaio FS285M, 7200 Hitachi, 1 Gig Ram.
2.Yes 5.0.1 dont have any Beta rests since I never test anything on music partition ( do it always on Internet one)
3.Midi track marked> hit delete button on the keyboard. Not very keen to repeat it, since it is very nasty, I mean the only way was using power button It happened twice and I think there was no any data on the track. The scary thing for me is that mega loud buzz. After all it can happened accidently, special on dark stage, want to hit Pos1 and hit delete instead

Switch off this computer Alex and enjoy your weekend, didnt expect any response before Monday ! You people are the greatest. Thanks so much for your attention.

ive posted at least 5 times about this.it should have been fixed long ago!!!

I can`t reproduce it anymore. The deleted tracks are deleted and songs saved. Will check if I have the old version on some backup HD .I should have check it immediately but I wanted to finish tha project I was working past few weeks. Now it is done so I will have to to experiment.

Tried my best but failed to reproduce it. Next time something like that happens I will definitely make some notes and check it in free time. It happened twice within 2 days but cant say it was same song, all I know one of the 6 of the project i was working on past week. now I am not sure if it was Impulse or rewired midi track. Dont really intend to delete midi tracks live but it could happen accidently. Locking option would be great anyway, too often, specially when tired edit delay instead of volume, or on wrong track.

It can be reproduced, took chance with old song that i wanted to try for remix. Could it be that it happens with ver4 songs ?
Anyway what should I send you Alex?

A way around this that works for me is delete the tracks effects and instruments one by one then delete the track- no crash, i find anyway.

yeah this one has happened to me repeatedly - Also when I have had Guitar Rig loaded in a track that I tried to delete it wanked my system...

ikeaboy wrote:A way around this that works for me is delete the tracks effects and instruments one by one then delete the track- no crash, i find anyway.

The point is to find out what and how, not the way around it. Deleting a track is a basic function, you cant expect people spending few hundred on a software to "find they ways around". Since Ableton support takes things seriously we should help them help us and (themselves)

I'll echo that last sentiment -

"Since Ableton support takes things seriously we should help them help us and (themselves)"

These guys have their work cut out for them this time around... Someone screwed the pooch big time when determining the features that were to be included in 5 -

It is sad but true - I hate to even say it because I am a loyal Ableton customer and advocate - All the problems that 5 has so far are starting to outweigh much of what this program has to offer... In some cases, the new features, at the expense of some of the old ones don't make sense - and the fact that after getting to a point where I really knew how to manipulate the app I'm having to deal with a learning curve again sucks. (yeah I know poor baby..: ] )

So at the very least - helping them to patch this beast up is probably the best we can hope for. I wouldn't be surprised if a 5.5 came out at some point - to buy them some time. These guys write code faster than anyone in the business - Their versions seem to come out before you get used to the current version - Next time around, even if it takes a bit longer I hope they nail it like before.

God forbid that this forum starts looking like a Digidesign forum - one complaint after another - I doubt it - the one thing I know Ableton has that those other guys don't (besides Germanic genes) is dedication and a real love for what they do.... I know they care about me and you and you and that other guy too a hell of a lot more than Digi cares about anything - except for money...

rikhyray wrote:

ikeaboy wrote:A way around this that works for me is delete the tracks effects and instruments one by one then delete the track- no crash, i find anyway.

The point is to find out what and how, not the way around it. Deleting a track is a basic function, you cant expect people spending few hundred on a software to "find they ways around". Since Ableton support takes things seriously we should help them help us and (themselves)

I was just trying to help you avoid a crash the next time your in the middle of some work pal not hault the software developement cycle.

Here's another tip Camamile tea or less caffine

Hi folks,

[quote]Anyway what should I send you Alex?[/quote]
What I would need is any kind of pattern to reproduce this.
If you can reproduce it in Live 5.0.1 you can try if it behaves the same in Live 5.0.2b3.

It is also possible that it depends on which instrument/effect is used within this track. So there are a lot of dependencies which makes it hard to find the reason for this problem.

regards,
Alex

forget about 5.02b3 - that guy has crashed... and crashed, and crashed... and ...you get the picture... since its beta test i lose stuff each time...

I want to be perfectly clear that I am referring to how it behaves in my setup - I don't doubt that for other people some of the quirks I've run into might not even occur...

[quote="Alex"]Hi folks,

[quote]Anyway what should I send you Alex?[/quote]
What I would need is any kind of pattern to reproduce this.
If you can reproduce it in Live 5.0.1 you can try if it behaves the same in Live 5.0.2b3.

It is also possible that it depends on which instrument/effect is used within this track. So there are a lot of dependencies which makes it hard to find the reason for this problem.

regards,
Alex[/quote]

Alex,

How can I get a copy of Live 5.0.2b3? I am a registered owner of 5.0.1, but I do not see anything in the downloads section...