I've been using 5.0, then 5.02, and then 5.03 in live DJ sets successfully now for months without so much as a hiccup. I just purchased a new top of the line IBM Thinkpad dual core T60p, 100gb 7200rpm hard drive, 2 GB memory - killer system and perfect for Ableton right?
So I decide to load it up with the new 5.2 release (which is supposed to provide some benefit for PC users with dual core, right)...
What a nightmare... in my live set, it crashed twice. But before that, I was treated to the following:
Problem #1 - delayed starts of clips. I have a Hercules DJ Console set up (as midi controller only) mapped to Ableton to cue, play, adjust pitch, etc. Imagine my surprise as I cue and launch a clip, only to have it start 2, 3, sometimes 4 beats to late. I have quantization set on ONE BAR, yet Live 5.2 would sometimes wait 2 bars, and not even start on the first beat! It would routinely start the clip on beat 2 or 3 of the bar! What a mess.. Just in case this could be a contoller/MIDI latency issue, I stopped using the controller and launched the clips the old fashioned way, with the mouse and the keyboard, and Live 5.2 still did the same thing - randomly starting the clip when it felt like it. Beats were still lined up with warp markers (except see below), but the start time would only randomly be on the first beat of the next bar - usually a bar late and on the 2nd or 3rd beat.
WHAT IS UP WITH THAT?
Problem #2 - over 1/3 of my tracks have shifted the warp markers! The starting marker and other markers placed in the track have somehow moved off a bit... discovered this pleasantly during a mix as the beats were all way off... then learned i had to check each clip as I loaded it. About 12 out of 30 tracks had screwed up markers. This has never happened before.
WHAT HAPPENED?
Problem #3 - sound quality - the sound coming out of Ableton was severely muffled or muted, even when bringing the gain way up - i could not get decent loud output out of the channels (using ECHO DJ sound card.) Luckily, I brought my old computer with me and swapped back to it in the middle of a set, and everything was back to normal in 5.03 on that computer - no delays in clip launches, markers where they should be, and decent volume.
Everything was working perfectly before, what happened to 5.2?
----------
Ok, so to eliminate the new computer as a suspect, I put 5.03 on it for a gig tonight and the launch latency/delay (problem #1) is gone, and the clip markers seem to be ok, except for in the tracks that were opened in 5.2. Also, the sound volume is perfect again.
Is anyone else noticing these problems? The fact that everything worked as it should in 5.03 on BOTH the old and NEW computer makes me think 5.2 is the problem...
Suggestions/ideas? Is 5.2 ready for prime-time?
HELP!-5.2 disasters/bugs! delayed clip start, moving markers
-
masterbeat9999
- Posts: 6
- Joined: Thu Oct 20, 2005 12:28 am
- Location: Los Angeles
- Contact:
dual core = live 6
other than that, these are very odd problems. IE the muffled sound on the Echo DJ - I have one and it is fine here with 5.2.
I cant think of a software option that you would have missed anywhere for 'muffledness' either. I assume you mean muffled as in 'no top end' rather than another meaning
its just as odd with the clip trigger. They didn't change THAT much in 5.2 from 5.03 - removing a few bugs only (on pc). So if 5.03 was ready for primetime then so is 5.2 it seems to me.
perhaps contact support about this directly and let us know the results
other than that, these are very odd problems. IE the muffled sound on the Echo DJ - I have one and it is fine here with 5.2.
I cant think of a software option that you would have missed anywhere for 'muffledness' either. I assume you mean muffled as in 'no top end' rather than another meaning
its just as odd with the clip trigger. They didn't change THAT much in 5.2 from 5.03 - removing a few bugs only (on pc). So if 5.03 was ready for primetime then so is 5.2 it seems to me.
perhaps contact support about this directly and let us know the results