Ableton Forum

yes it works, but it's still not how things should be working...

edit: actually it still happens if the sample hasn't been played for a while!!!

edit2: and sometimes there's a hikup in the audio when i start a new sample, wich is very short, but there's no cpu spike or flashing d light...

samething is happenigg to me as well.i cant even dj tonite with ableton live 5 i have to go back to 4.this is really crap.im getting really close to selling my copy of live and trying sonar 5.this version has been out since july and its still full of bugs.bs

s[riteboy,

[quote]I loaded up my set and I was still getting spikes.

The spikes only happening on the initial lauch of some clips. So what I've done is before I started my set I made sure to launch each session down through my set which only took a few moments. When I went back to the start all clips seem to play fine without any spikes/glitches.[/quote]
Basically this sounds like a memory issue as if some data have to be loaded from disk or swap file.

Some more question (please note that these question should not mention any kind of workaround but a way to reproduce this)

1)
What happens when you open a Live set, then doing your workaround and firing all clips. Then you quit Live and load again the same set.
Does it happen then again?

2)
Does it makes a difference if all clips have the RAM switch on compared to no clip has the RAM switch on?


regards,
Alex

I'm having these kinds of problems too. Live 4 sets that I was working on, which played fine, have CPU shortage problems when I try to work on them in Live 5. In general it feels like v5 is slower. I haven't tried the bugfix update yet.

I only tried the demo version of live5 and i'm having the same problem. At first i thought my mac is to slow. i will try somethings and i hope it's gonna work because i want to by live5

Alex wrote:s[riteboy,

I loaded up my set and I was still getting spikes.

The spikes only happening on the initial lauch of some clips. So what I've done is before I started my set I made sure to launch each session down through my set which only took a few moments. When I went back to the start all clips seem to play fine without any spikes/glitches.

Basically this sounds like a memory issue as if some data have to be loaded from disk or swap file.

Some more question (please note that these question should not mention any kind of workaround but a way to reproduce this)

1)
What happens when you open a Live set, then doing your workaround and firing all clips. Then you quit Live and load again the same set.
Does it happen then again?

2)
Does it makes a difference if all clips have the RAM switch on compared to no clip has the RAM switch on?


1)yes it happens again.
2)it happens either way on this end

I've noticed this as well. A few audio clips playing at the same time sends Live 5 (any version) into digital overload. And it varies...sometimes the clips will play fine for a bit, other times it happens right away. This did not happen in Live 4.

Are there new settings in Live 5 that may be causing this? It's driving me nuts as I can't really get into anything using Live 5 before it overloads and I have to reboot it.

Even weirder and more frustrating is the CPU spikes (well over 100%) that occur when Live 5 is just sitting there with no audio playing.

I have a song which has two audio clips, and Absynth 3>CamelPhat3. The CPU hits in the 50% while the clips are playing and I'm playing live into Absynth/Phat, which is to be expected. The odd thing is after I hit stop to take a phone call, after a few minutes the CPU just started to climb, hitting around 183% for no reason at all. This is not the first time I've noticed this either.

Something is def wrong with Live 5 somewhere.

I am experiencing these same problems with 5.02 ( just audio clips firing sending the cpu load into orbit ! ) .

i'm having the same problem.

playing the clip the first time causes the CPU to jump and the sound to drop but next time round its ok.

after having not played a clip for a while it does it again.

Alex wrote: If the CPU usage goes to such a high value it is clear that it will produce dropouts too. As you write it did not happen with the same Set in Live 4 I would really like to get hands on such a set.

So is this behavior always reproducible in Live 5? Everytime you play certain clip in some certain tracks you get this high CPU usage?

regards,
Alex

thanks for the help, alex. i'm not really concerned with the dropouts, because that can be expected for such high CPU usage. the major problem here is the CPU usage! there is no way that three or four simple audio tracks playing simultaneously should max my system out! this didn't happen with L4, but it's happening with L5. (which really sucks, cause the bones of L5 are pretty damn sweet) but this is rendering the program unusable!

others have noticed that the cpu usage of L5 just sitting there is high. when i have live open, but playing nothing, activity monitor measures Live as taking up 30-40% of my system resources! doing nothing! yikes!

i guess this is more widespread of a problem than i thought. well, at least it's not my system. back to L4. too bad.

same problem here.. still happens with 5.0.2

my conf: powerbook g4 1.5, 17", 1.5Gb RAM (also happens when i took out the new 1GB RAM module)

i already made a post about this here: http://www.ableton.com/forum/viewtopic.php?t=27652 ... i'll live thatone and will keep monitoring thisone...

really hope that there is some fix... it seems impossible to play live with this problem... (and thats the only reason why i bought ableton live)

i'm also getting drop outs when stopping some clips, how can that be?

I may as well add my bit to this Ableton debarcle too! I've had enough of LIVE 5 tonight. I've had to re-start too many times to remember.
I do not perform with LIVE - just compose. Quiet, sedate studio work.
My CPU meter rockets off to 200% regularly during playback. Songs have a couple of audio tracks & few MIDI tracks. No big deal. LIVE 4 caused no problems.
No CPU activity while LIVE is dormant though, as mentioned in previous post..
Very frustrating! Quick fix from Ableton required before we all mutiny.

Hi folks,

please try at least to answer my questions. To post "there are clicks and the audio goes to 200%" does not help us to find the problem for this.

There are already several different scenarios reported in this thread:

1)
Getting high CPU usage when starting Live and fire several clips for he first time of this Live run. After these clips are fired once it behaves "normal" again.

Question for this issue:
----------------------------
- a) Does it also happen when you quit Live, reopen Live and fire such a clip again?
- b) Does it makes a different if 'RAM' switch for all audio clips is on or if the 'RAM' switch for all clips is off
- c) Does it makes a difference when disable all effect in a track where it can happen.


2)
munn,

there is no way that three or four simple audio tracks playing simultaneously should max my system out! this didn't happen with L4, but it's happening with L5. (which really sucks, cause the bones of L5 are pretty damn sweet) but this is rendering the program unusable!

So you have a Live set you can play in Live 4 but the same set already max out the CPU in Live 5? Does this happen always when playing this set or is this also related to the "happens only when starting some clips for the first time" issue? Could you send me such a Live set?


3)
gvhull,

My CPU meter rockets off to 200% regularly during playback.

Does this happen at a certain position in the set?
Does it happen for a certain clip or track?
Does it happen when playing after Live was dormant for a while?
Does it happen after you minimized and then maximized Live?




As this is a complex issue, feel free to mail me directly which would it make easier to keep the overview.

regards,
Alex