Ableton Forum

Hi folks,

this topic might be related to 'Clips won't work through set' by Pheek, but I'm not really sure...

After working on a live set for several hours, some clips started to behave strangely. Without any efx or envelopes active some clips played only their beginning (say approx. the first 2 beats) and then stopped. (the turning pie symbol running on)
This happened first when I added 16-bit .wav files (whilst working with 24-bit wav and aiff files). I saw the clip waveforms but couldn't hear them.

Later on I got dropouts on other tracks in my arrangement, sounding like randomly muted and unmuted.
After I quit Live and start the same set again, it works properly again.

My setup: G5 2.5DP (1.5 gigRAM) with RME DIGI9652 on OSX 10.3.8
CPU load meter around 30%, Beat Repeater on 1 track

the good things: It didn't happen on stage. no crashes until now. stable as always.

cheers,
Stefan

Yes, I still have the problem. At first I thought the problem was solved in 5.0.2, but no. I was explaining my problem to my friend Cabanne who said had the same problem recently.

I'm trying to see whats going on in my set, there's nothing special...

Also, a new problem: sometimes, some clips are stuttering. The beginning of the clip will be repeated 3-4 times... hard to explain, its weird.

it's really upsetting to still see major problems with 5.02. I really hope it all gets worked out. I know they are working hard on all these problems but it's a little upsetting that the problems are even there in a program that is so pricey and should work right off the shelf...

-shrug-
oh well.

yesterday i thought about upgrading to 5.0.2 but while testing the demo i have some serious audio dropouts. three within 10 minutes. i don't know where the problem is, but with such kind of problems live 5.0.2 isn't really usable for live perfomances.

my setup is latest powerbook g4, 1gb ram, os 10.4.3. the cpu load was around 30-40. also i used the internal soundcard of the book.

hope that this problem is located as fast as possible, that a fix can be done.

I too am experiencing the occassional 100ms drop-out roughly at least once every hour during Live 5.02 playback during jamming sessions. As a rule I endevour to keep Live's CPU usage meter below 40%.

Although it's not stopping me from preparing works I am concerned about drop outs occuring during a live performance (although it wouldn't be a total disaster it would be better of course if it didn't happen). Live 4.1.4 didn't have this issue ....

Cheers

I am having the same problems...drop outs, clicks, pops... Additionally, as of tonight, Live 5.0.2 won't even launch??!! i sent this to folks at Ableton:

ableton live 5.0.2 strangely stopped launching.

computer: HP laptop 3.2 GHZ Intel 4, 2 GIG RAM, windows XP.

Live message: 'A serious program error has occurred. You should try to save your work under a new name using the Save As command from the file menu and restart the application.'

occurs: when i try to launch Ableton Live

I bought the 5.0 upgrade and also downloaded the 5.0.2 upgrade 2 months ago or so.

for no clear reason Live isn't launching. it begins to launch, it cycles through my plug-ins and then the above message appears. I click 'OK' (my only option) and the Ableton launch page clears and doesn't finish booting up..

I wondered about one possible plug-in i had (re)loaded earlier today: Waves IR 5.0 -over a month ago i had some strange experiences with apparent conflicts (not necessarily with Live...i can't remember the specifics) .. so i uninstalled it along with Waves 5.0 diamond bundle. But i did eventually reinstall waves 5.0 diamond bundle and had been using ableton just fine. Today i reinstalled the IR plug-in to use in Sound Forge and when i relaunched Ableton i experienced the above problem. So..I again, uninstalled Waves IR...that didn't help, i again unistalled Waves Diamond Bundle, that didn't help.

and quite honestly, i have had a lot of problems this weekend using ableton. I had recorded and mixed a song in Live 4.0 using around 17 recorded audio tracks, 6 reason rewire tracks and tonz of plug-ins that does not render (or play back) correctly in 5.0.2.(first off it takes forever ...like 4 hours to render, secondly the final rendered file has digital 'clicks/spikes' all throughout the song...sometimes it doesn't even finish rendering before crashing)...this song played back and rendered just fine in 4.1. After fighting it for 3 days, today i compromised and tried a different approach: my thought was to strip the song down multiple times deleting certain tracks, rendering a mix...then relaunching the original file, deleting recently rendered tracks, then rendering what is left, repeating this until i have the entire song cleanly rendered with 4 or 5 different 'submixes'. i hoped i could just take the 'sub grouped' rendered mixes and open a brand new als, drag those mixes onto empty tracks (no fx at all) and render that...i was not able to finish this process before ableton quit launching...which is very frustrating...

i would love to uninstall ableton 5.0.2 and reinstall it from scratch but know my installs are limited.

i also want to know what is going on that is causing these problems...has anyone mentioned this?

is there any way to open a file in 4.1 that had been later launched and saved in 5.0.2?

datalyst studio wrote: i would love to uninstall ableton 5.0.2 and reinstall it from scratch but know my installs are limited.
saved in 5.0.2?

Use Windows file searching tools to locate a file on your system hard drive titled "unlock.cfg".

Make a note of where it lives ....
Make a copy of unlock.cfg elsewhere on your system.

Uninstall Live completely from your system. Delete Application Data folders associated with Live 5 (c:\Documents And Settings\[your name]\Application Data\Ableton ..... etc, etc,) ....

Reinstall Live directly from the 5.02 updater.

Instead of having to unlock again you'll be able to put the unlock.cfg file in its correct place .... m

The unlock.cfg file will remain relevant so long as you aren't also reinstalling Windows XP from scratch and other elements of your system remain static.

Maybe worth a shot?

cHEERS

having exactly the same annoying problem in L 5.0.2, and after trying everything that I thought possible, from reducing tracks (9 by now), deleting following actions, running the set from an external and faster hard drive(7200 rpm firewire 800), converting as much I could stereo files to mono (6 tracks from the 9), deleting the few live effects that I had in my set, to contact the ableton support whit out any feedback until the moment.
and seems that nothing works even when the cpu shows 20 % ( but every time that I switch scenes climb until 100, 200 or even 400%)and the situation is getting really frustrating.
but a few days ago, following the advice of a friend I delete every single .asd file related to the audio files involved in the proyect closing it and reopening it again seems that reduce at list 80 % of the problem, but after re work in the project, gradually the problems star to happen again, glitches and drop outs in every scene launched, and even worse, clips playing the first bar and after as if there was volume envelopes written no audio at all. so to this point I don't know what else should I do.
every time that I delete the .asd files every thing goes back to normal, so the only momentary solution that I see until some new update give us a real solution to this bug is to work until I get finish the set and before play it , trash those files one more time and pray to not have any problems for at list one Hour....

just to tell you guys that, after some time workin seriously with 5.0.2
(upgraded to Tiger in the meantime...) I still experience the same problems with mostly the more extensive tracks (one had about 9 audio tracks, Impulse and one external midi track, activity ~30% - with ~450 mB of samples loaded and 1.5 gig of RAM) when audio tracks disappear from the audio.

did some testing ---(more like intuitive twiddling - I would be the worst beta-tester...)

my finding is: placing (mostly bigger) audio files in RAM causes a lot of these drop-outs. If I switch off the RAM option for my audio clips everything is kinda normal.

When I switch computers working on the same track - my G5 and my G4 laptop I have to manually switch the RAM parameters.
On my Powerbook I put some smaller clips in RAM and the bigger ones go from disk.

- this works ok for the time being.


it seems that my expensive 100% mac-tested, mac-expensive RAM is too fucking slow!!!??? or who's eating up all this RAM? OSX?

shame to admit but for the recording-heavier stuff I turn to the old Logic with Live as rewire slave.

....and I'd love to hear a specialist about that...

greetings,

Bang