Ableton Forum

i have my cache set to 3gb/500mb min and have been seeing this issue for the last couple of weeks and i think its finally debilitated my ability to play to such a degree i think i may have to fall back on traktor for tomorrow's show.

the problem is that i have a fairly small set (approx 2 hours) loaded into a live set. there are only 4 channels, and a total of about 20 scenes. each scene has at least one mp3 loaded on it and a max of three.

when i start loading the set, well... lets just say its slow. i started loading my current set at 10:30 in anticipation of creating a recorded mix and its now 40 minutes later and i still can't get the application to respond to the clip activate button.

i thought it might be a caching issue so i grew the cache to 3gb. what seems to happen though is that, when i load the set, it wants to completely re-analyze the clips. i had even saved warp markers and such last night in a two hour editing session.

as it is, i can't rely on it to load in time to play the set tomorrow, and i certainly can't figure out why its still loading. any thoughts? i've given up on using it for dj'ing at this point unless i load, mix and render the set all in one night.

stupid question, but did you create your set during the beta testing period? have you saved it since then?

a little bit less stupid: does Live re-analyze all the clips each time you load your set?
that shouldn't happen, so it might be linked to faulty preferences/cache path.

Wasn´t the decoding bug still there in 5.0.1?
Do you use 5.0.2?

In 5.0.2 it never happened again for me.

I gave up on MP3s after realizing they're more trouble than they're worth. Hard drives are cheap, so I went back to AIFFs.

So much easier!

I agree, the MP3's are decoded to wave files before being played back anyway, so I just convert them all to wav files now ahead of time. I have hundreds of tracks on my 60GB drive with plenty of room for more, and external hardrives are pretty cheap if you have greater storage demands.

it was either a bug or cache or ... who knows.

to answer the questions, it was a brand new set. i had started it last night, worked on it for a while, left and came back. when i reloaded it was awful. i rebooted, restarted everything and reloaded the set and it was much quicker but i have seen it several times so i'll try to narrow it down to a specific set of circumstances.

i seem to have bigger problem now... but thats' the subject of another post.

thanks gang.