Ableton Forum

Chris J wrote:I have 2 athlon 3000+ with 1Mb ram. one is a laptop with built in soundcard the other a desktop with a STAudio.
With Live 5, a set done in L4 that used to run very smoothly on both machines, is completely unusable on the laptop due to the drop outs when triggering clips. No VST, praticaly no effects, very low CPU.

One can argue that the asio4all is the culprit on the laptop. Yes but the same set runs with no problem under L4

only 1Mb ram?
its amazing you can even run the operating system!

oops, I meant 1 kb

My session ran well enough last night despite glitches. I tried to maquerade problematic scenes I had Identified through carefull mixing between my computer and my partners powerbook.

The real problem I faced was when my cpu didn't want to recognize my tascam fw1884 anymore. Good thing I had my fw1814 lying around, but I hope I'm not fucked.

I had the same problem DJ-ing out last night- audio dropping out & jumping despite low CPU usage. Never had it so badly in L4. V. embarrassing

ethios4,

did you get your ram?
any thing to report?

RAM got delayed from Tigerdirect. Should be here in a few days. I'll report back when I get it installed and tested.

Similarly, it happened to me.
They happen easily when many use the audio clip on V5.
Perhaps, it is believed that they are related to the consumption rate of RAM.
I confirmed the phenomenon of "D" lamp's lighting at Loop of the phenomenon and Clip Action that CPU meter jumps from 11 to 100% or more during Live the other day.
Another one..

I am confirming the phenomenon AudioClip's that keeps doing Loop not sounding it after 4Bar or more is reproduced.

PowerBook G4 1.25G/1024RAM MacOSX10.4.2 Live5.0.1

Hi folks,

would be nice if you can give the current beta of the upcoming bug fix update Live 5.0.2 a try to check if this kind problem is still there:
http://www.ableton.com/forum/viewtopic.php?t=25938

regards,
Alex

Hi

Will check the new beta today.
However, I've ben getting this problem a lot too.

Deleting prefs.cfg regularly sorts it out though. The longer I go since cleaning out prefs.cfg the glitchier things get. Very odd.

I use an echo indio or sometimes an rme digiface with a 2.4 P4 and 1 Gb RAM

Hi,

I tested Live 5.02b3.
However, this problem was not solved...

It happens by Clip that Play is done for the first time after Live Set is opened.
CPU% that my LiveSet uses is 24% on the average.
However, the DiskOverload lamp lights frequently.
I feel that I was steady more with Live4...

CPU% jumps from 24% to 56% when Clip that does Play for the first time after opening LiveSet is done in Trigger.

thx.

PowerBookG4 1.25G/1024MbRAM/MacOSX10.4.2/ESI QuataFire610/Live5.0.2b3

This is very unfortunate.

Got glitches, dropouts and cpu spikes too with the new beta.
Cpu jumps between 8 and 15% the whole time (up to 1500% sometimes) and the glitches also appear when I run a recorded arrangement everytime a clip starts.
In session it was fine, but after running the set for 3+ hours it startet to glitch too.

Greetings

I actually started getting this behaviour in Live 4!

My machine should definitely be up to the task though. In fact a friend of mine just got a brand new monstrous machine purely for running Live and is suffering the exact same problem.

I really really really hope it can get sorted. I really love Live as a piece of software but it's so stressful using it on stage at the moment.

Alex/any of the ableton crew: Have you observed any of these problems?

I have only just noticed that my live 5 has been having the same problem.
I never had any hard disk access trouble with live 4
I was messing about in impulse making a break and the red D constantly flashing
Ive never had this problem before

Powerbook 10.4.2 1GB

Got another stick of 512, so now I have 1GB of RAM.

I think the problem I had with audio dropping out when triggering clips was due to the Edirol UA-1/ASIO4All combo. I haven't experienced that since switching over to the Presonus Firebox.
I continue to experience crackly sounds sometimes when turning knobs, scrolling in a numerical box such as "Detune" on a clip, moving clips, etc. Also, there are occasions when Live sends out a horrible glitch sound when doing these things.
Friday night I experienced my first ever "Live has encountered a serious program error" message, while working with an mp3 clip while it was decoding.
So I haven't really noticed a difference in the frequency of glitchy sounds, or crackle sounds, since I installed the RAM. Obviously clips loaded into RAM are more responsive...I had an old Live4 track that always caused problems at a certain point, with Disk Overload light going off, cpu spikes, horrible glitches, etc. I loaded all the clips into RAM and was able to make it through the difficult part with no glitches at all. So that's a big improvement. CPU usage is higher in Live5 than Live4 for that part though.

At this point it's hard for me to pinpoint which problems are coming from Live5 and which are from my system. I recently discovered that my system use IRQ 21 for USB, Firewire, and Ethernet. This could be the cause of my glitchy sounds, since my new audio interface is Firewire, and the glitches and crackles seem to happen whenever I'm doing something in Live with my UC-33 (USB) or USB mouse. I'm experiencing audio glitches right now typing with my PS/2 keyboard while iTunes is playing, so who knows...
I'm getting a Centrino laptop in the next week or so, so I'll test all this out again, and see what happens.

I will say that I was having a lot of problems with glitchy sounds, crackles, and general instability with Live5 while I was still using my Audiophile 2496 pci soundcard, and the exact same setup I have now, except for only having 512MB RAM. Its the same setup I've used since Live3, which had absolutely no problems. Live4 started having some glitchy sounds. With Live5 the glitches have multiplied greatly.

Sorry for the rambling post...I should probably get some sleep.