Help... Ableton bugs... :s

my guess would be that it's cpu overload. even if the cpu monitor doesn t show more than 64 (which is high, btw) there could be spikes higher than that missed by the monitor (for example, if the monitor polls the cpu every 50ms there could be a short spike in between that). try increasing the latency a bit. also, is your machine configured well for audio? no background progams/processes running? power settings at max performance?

• no background progams/processes running? power settings at max performance?** 

I shut down everything I find... for instance wifi, norton security... etc...

yep power setting on green bulb "pleine puissance"*

Originally posted by : dtr try increasing the latency a bit. 

you mean to 2048? I fear the machine freezes at the first little prob.

also, is your machine configured well for audio? 

maybe there's something I didnt think about... how to?

is it a legal live? (if not, try to find another crack or send me a message...)

did you use the laptop for audio purposses before this? with ableton? and did this started suddenly? or is it the first time you try? did you used it with other programs?

and is it only a note being lost? or is everything affected by the glimps?

pfieuw, a hell of a lot question marks, sorry for that :-p 

Originally posted by : liquidbass

The cpu use swichtes from 23 to 64 percent, but this is irrelevant to the bugs... 

I think cpu is your problem. Peaks up to 64% are enough to cause this. In FL I have them from 75% and above, in ableton lower than that (50%). Solutions: as dtr said: 2048 samples buffer size, use asio. All these audio tweaks like virusprotection off and all help a bit but not much. One big reverb and all your efforts are in vain. So:

• mind the cpu hogs

• render/bounce/consolidate what you can

• don't use big reverbs (at work)

• mind decays of delays

• what's your graphics card? Strangely enough this can cause this too (cpu taking over when scrolling, when it skips on my pc, i's when I scroll).

• play less live (I play several wavs ith some plugs, no more then 10% cpu)

when i play live, 60% is like the minimum of cpu-use i have; mostly i got it between 70-80 without any problems. but i think i've had a similar problem in the past, although it was not a full live-set, only a live-set of one track (with audio and midi). to solve the problem, i had to remake the live-session of that one track. appearantly there had been a bug while working that stayed i that one live-file, and because i saved oover the original, i couldn't go back to a previous version of the session (that's when i learned to save multiple versions of my sessions: 1.0, 1.1, 1.2, 2.0, 2.1, …). try previous livesets you've made and see if the problems occurs there also. btw: is it with vst's/rewire or only audio-samples and external synths? 

maybeye you could try using 2 laptops.

this way you can put the audio and the most important plugins on 1 laptop, and link both pc's with fx teleport. i once tested it and it really works well

http://www.fx-max.com/fxt/

Originally posted by : Tezcat

is it a legal live? (if not, try to find another crack or send me a message...)

did you use the laptop for audio purposses before this? with ableton? and did this started suddenly? or is it the first time you try? did you used it with other programs?

and is it only a note being lost? or is everything affected by the glimps?

pfieuw, a hell of a lot question marks, sorry for that :-p 

1 no but it worked fine til now

2 I am mostly a reason user and I never had trouble The problem only occurs with Live

3 a glimpse of everything is lost

Originally posted by : bandarlog

• render/bounce/consolidate what you can
• don't use big reverbs (at work)
• play less live (I play several wavs ith some plugs, no more then 10% cpu) 

This is the solution I was also thinking about... Indeed theres a compressor and reverb and a stereo expander running on each track.

I think i'll spend the day rendering and rebuilding a nofx set. Thats much less fun on stage... because I really had fun messing around with these fx... but better be save and not mess up the fruit of 10 weeks ful time preparation.

(by the way in my first message I forgot to mention... the two vst fx I use are guitar rig2 and glitch)

Originally posted by : firefrog appearantly there had been a bug while working that stayed i that one live-file, and because i saved oover the original, i couldn't go back to a previous version of the session (that's when i learned to save multiple versions of my sessions: 1.0, 1.1, 1.2, 2.0, 2.1, …). try previous livesets you've made and see if the problems occurs there also. btw: is it with vst's/rewire or only audio-samples and external synths? 

I think that might be the origin of all the trouble... I saved at least 30 times on the same *.als, imported, sliced, deleted samples and tracks... In the future I'll mind that multisession thingie!

I use wave samples with internal fx and the two vst fx I mentionned above.

I create the samples in reason... or at least 95% of them...