[amo] scrambled warp markers and eventual crash.

[scientist]

a set that worked correctly in beta12, in beta13 has various warp markers and/or start positions scrambled in a few clips. attempting to correct warp markers froze live.

the restored backup of the set (see kids, backing up is a wonderful habit!) opens correctly in beta12, but has identical warp problems when opened again in beta13. not sure if i'll be able to send the crash report, as the alp is over 50mb.

[mholloway]

just loaded a song built in 8b12 into 8b13 and have the exact same issue. vocal recordings I did now have warp markers all over them that *I never put there*. the start point has also been changed in all of them -- I had to grab it and drag it back to get the samples in the clips to start where they should. it's all fixable, but a pain in the ass. and what's with the pre-generated warp markers???

[scientist]

still present in b14, but its possible that this was a problem introduced into b13 files and thus persists.

this must have something to do with live putting transient markers (and thus additional warp information) into previously warped material. i have auto warp turned off in preferences, and am a little at a loss as to why live would need/want to re-analyze old files in the first place...'if it ain't broke, why fix it!'.

also, this might be a good argument for extending expiration so betas overlap a little. it was quite helpful to compare identical sets in beta12 and beta13. now with things apparently broken for good, i have no way of returning to a the previous non-broken version to confirm/deny any issues.

[scientist]

BTW I have also noticed that for long samples beat 13 is re analysing them every time i load up the project.

same here. this is still present in beta 14 as well. i'll experiment with the save button and see what it does. also, the .als files are much larger than the live 7 versions, e.g. was 3mb, is now 15mb.

[scientist]

still an issue in beta 15...
loaded unaffected (pre-beta 13) version of the set. opened fine. closed, re-opened and its messed up again. restored the entire project folder from backup = fixed! close and open again = broken! so, i get one successful load and anything after comes up with the same warp errors. here's a couple screenshots showing one of the strange clips...under any circumstances is what's shown here normal? when i try to move this loop bracket, live hangs (no full crash, i need to force quit).

wtf? brackets 1:


wtf? brackets 2:

this second screenshot is taken while live was hanging...hung? hanged?
also, note all the warp markers. i did not make them.

here's a screenshot of the identical clip in live 7:

THAT is what it should look like, new transient info be damned.

[audiojunkies]

Yes I have, had this with a three track DJ Set completely mashed up...

Also if you have the start of the loop halfway through a warped and grooved file, this fails to load also even after pressing save..

Ableton Don't and refuse to believe this is happening, and whats more the beta email address is now refusing emails...

[scientist]

question for others having this issue: have you noticed this problem with any sets that were never opened in beta 13 or 14? i'm still trying to suss whether it is an ongoing bug, or whether something in either of those betas corrupted the sets to being with.

[scientist]

more info: so i'm starting to think it is app/preference related, rather than corrupted sets. after opening a problem set and crashing when attempting to move a warp marker, i opened a new set and crashing still occurred trying to warp a brand new 100% unwarped audio file. trashed everything and reinstalled beta 15, everything worked correctly until the problem set was opened...warp causes crash again, and new clips loaded into the set are having the same thing happen: new warp markers introduced that i didn't put there...pretty much the same as the above screenshots.

[forge]

it does sound like this might be related:

http://forum.ableton.com/viewtopic.php?p=857826#p857826

we need to somehow narrow down any variables that may have changd - only thing I could thuink of was that it looked at the sets tempo? other than that I have no idea what changed - I was using the same file again and again, deleting the ASD file and rewarping - so it should have been identical

[scientist]

whatever the fuck is going on is still in beta16. opened a version of the set that has not been modified since beta12, and it has the same errors. corrupted .asd files? who knows. i'm done trying to figure this out until there's word from ableton...they have at least a few versions of this crashed set emailed to them by now.

[magestro]

+1

Same Prob over here. It is even getting worse. Rigth now i can`t open any saved set without all Warp Markers with in Live recorded Audio being misplaced or completely lost.

In Beta 12 everything worked out smooth.

There should be a word from Ableton around here, if this Prob is already adressed. Starting from Beta Nr. 14 i got loads of Crashes, which is kind of depressing since the earlier Versions worked out quite well on my System. Just an occasional Crash every 3 Hours or so.

Cheers

[forge]

There should be a word from Ableton around here, if this Prob is already adressed.

really we need to try and isolate exactly when it happens so they can reproduce it - they can't fix it otherwise as it's not happening on their machines

mean time maybe a bug report snap shot

[scientist]

one idea i had was to delete all the affected .asd's and see if that would have an effect, but i'm not going to bother unless ableton thinks it'll do some good. multiple bug reports sent + many hours on my part + zero response or feedback from ableton = fuggit. at this point i'll just chalk it up to a one time corruption (albeit of pretty much everything that got opened with beta 12) and move on...

[forge]

one idea i had was to delete all the affected .asd's and see if that would have an effect, but i'm not going to bother unless ableton thinks it'll do some good. multiple bug reports sent + many hours on my part + zero response or feedback from ableton = fuggit. at this point i'll just chalk it up to a one time corruption (albeit of pretty much everything that got opened with beta 12) and move on...

in my example I was repeatedly deleting th eASD file and doing it again

[scientist]

one idea i had was to delete all the affected .asd's and see if that would have an effect, but i'm not going to bother unless ableton thinks it'll do some good. multiple bug reports sent + many hours on my part + zero response or feedback from ableton = fuggit. at this point i'll just chalk it up to a one time corruption (albeit of pretty much everything that got opened with beta 12) and move on...

in my example I was repeatedly deleting th eASD file and doing it again

heh. i must've read your post, assimilated it, and called it my own. i'm the microsoft of beta forum posters.