Live 5 bug

[deaneager]

I had Live 5 at Christmas to use (primarily) as a DJ tool. Since then, on a few occasions now, I've loaded up a set and watched as Live appears to re-scan the waveform for a few tracks. After it's finished, the whole set is out of time and warp markers are all over the place.
Other people on the Ableton forum have ahd the same problem, but with no workaround. Ableton are a bit slow on support and seem blissfully unaware that such a problem exists. For me, it has made it impossible to use it for it's intendd purpose (i.e. Live performance). I thought Live was supposed to be rock solid!
Has anyone else had this problem? If you have, have you found a fix for it?

[krushing]

Live was pretty solid until v5...I'm still on 4.1.4. The app has bloated, the userbase has bloated and consequentially Ableton has grown and the response time has grown longer.

Sorry, no fix that I can think of right now...

[diverdee]

are u using converted mp3's? i've heard that they can be problematic - best to convert to wav's oneself first.
Also i've heard that there is some kind of issue with quicktime.

[foxal]

you need to warp the tracks

[deaneager]

if I convert all my MP3's to wavs, I won't have anywhere nearly enough hard drive space (there's not much left as it is!). I suppose I could buy another external drive.
If I pre-warp the tracks, that means I can only DJ at one tempo, which, dependant on venue, time of night, music policy and how many substances the crowd have had, might not be suitable. SO I have to be able to warp the track to a current project tempo.

[sqook]

if I convert all my MP3's to wavs, I won't have anywhere nearly enough hard drive space (there's not much left as it is!). I suppose I could buy another external drive.
If I pre-warp the tracks, that means I can only DJ at one tempo, which, dependant on venue, time of night, music policy and how many substances the crowd have had, might not be suitable. SO I have to be able to warp the track to a current project tempo.

This isn't true. First of all, live converts all your MP3's to wav's anyawys before playing them. The only difference is that it uses a cache with a predetermined size (which can be set in the preferences) to set a maximum of how much hard disk space it will consume.
And if you pre-warp the tracks, it actually helps you play at different tempos. First of all, there's no way that you can be thinking before your gigs, "well, should I bang it at 140BPM tonight, or take it nice and easy at 105?". Odds are, your music will keep you in a 10-15BPM range, and if you DO like to mix it up to this extent, then I highly doubt you are doing so with the same tracks. If you prewarp all of your tracks to a tempo roughly in the middle of where you intend to play, and then bounce them to disk in "complex" mode, then you can play them back using the "beats" warp mode and save a lot of CPU without sacrificing audio playback quality. I personally bounce at 125, and play in the 120-128 range.

In regards to live5, yes, the abes are a bit slower fixing bugs, as the product has grown massively but their company has remained roughly the same size. I personally don't experience half of the shit that people complain about, although there are definitely unfixed bugs in live5 that really piss me off. Nevertheless, I don't think that it's unstable, and I've never had it crash in an important situation.

[DELUDE]

edit: someone was faster

[deaneager]

if I convert all my MP3's to wavs, I won't have anywhere nearly enough hard drive space (there's not much left as it is!). I suppose I could buy another external drive.
If I pre-warp the tracks, that means I can only DJ at one tempo, which, dependant on venue, time of night, music policy and how many substances the crowd have had, might not be suitable. SO I have to be able to warp the track to a current project tempo.

This isn't true. First of all, live converts all your MP3's to wav's anyawys before playing them. The only difference is that it uses a cache with a predetermined size (which can be set in the preferences) to set a maximum of how much hard disk space it will consume.
And if you pre-warp the tracks, it actually helps you play at different tempos. First of all, there's no way that you can be thinking before your gigs, "well, should I bang it at 140BPM tonight, or take it nice and easy at 105?". Odds are, your music will keep you in a 10-15BPM range, and if you DO like to mix it up to this extent, then I highly doubt you are doing so with the same tracks. If you prewarp all of your tracks to a tempo roughly in the middle of where you intend to play, and then bounce them to disk in "complex" mode, then you can play them back using the "beats" warp mode and save a lot of CPU without sacrificing audio playback quality. I personally bounce at 125, and play in the 120-128 range.

In regards to live5, yes, the abes are a bit slower fixing bugs, as the product has grown massively but their company has remained roughly the same size. I personally don't experience half of the shit that people complain about, although there are definitely unfixed bugs in live5 that really piss me off. Nevertheless, I don't think that it's unstable, and I've never had it crash in an important situation.

OK, so if I use 'beats' warp mode, Live won't do this re-scanning thing and shift the warp markers all over the place?