really annoying bug... sigh
Posted: Sun Aug 27, 2006 1:14 pm
i warped my song accordingly to the basedrum at every quarter. take a look at this picture:

however... after some time of using that clip, opening sets, closing sets, restarting ableton, ... and so on, it got corrupted.
now when i zoom in just a little, these markers slide as you can see on the next picuture:

and, this is actually how ableton then plays it, meaning not in sync with everything. if i zoom out again the markers appear to be at the right place again, but it still plays WRONG
did i do anything with the .asd file? no, it is still the same. i can tell by the last-modified timestamp of the file. it hasn't changed.
sometimes it works if i clear the cache and reload the clip into my set. then it plays in sync again. but sometimes it doesnt and i need to delete the .asd file and do all warping again. and this occassionally happens with ALL my clips.
what is this??? i use ableton 5.0.2 on two winXP systems. freshly installed on a laptop, AMD turion 2.2 GHz, and on one older system on a PC, AMD athlon 2700+. both 1 gig RAM
this thing occures on both of them....

however... after some time of using that clip, opening sets, closing sets, restarting ableton, ... and so on, it got corrupted.
now when i zoom in just a little, these markers slide as you can see on the next picuture:

and, this is actually how ableton then plays it, meaning not in sync with everything. if i zoom out again the markers appear to be at the right place again, but it still plays WRONG
did i do anything with the .asd file? no, it is still the same. i can tell by the last-modified timestamp of the file. it hasn't changed.
sometimes it works if i clear the cache and reload the clip into my set. then it plays in sync again. but sometimes it doesnt and i need to delete the .asd file and do all warping again. and this occassionally happens with ALL my clips.
what is this??? i use ableton 5.0.2 on two winXP systems. freshly installed on a laptop, AMD turion 2.2 GHz, and on one older system on a PC, AMD athlon 2700+. both 1 gig RAM
this thing occures on both of them....