Page 1 of 2
NEW OSX UPDATE NEEDED URGENTLY!!!!!
Posted: Mon Nov 01, 2004 10:06 pm
by vince watson
ABleton, please read the forums like you have in the past......there are tons of poeple having serious issues with A4 on Panther...me for one......i chucked my live 4 in the wastebasket tonight and started again.......my problems of audio dropping out are still there..... SORT IT OUT!!!!
Lots of us have gigs and need this software on a regular basis.
Anyone else agree??
Posted: Mon Nov 01, 2004 10:16 pm
by bensuthers
no. it all works great over here. and at all my friends.
so that covers
400MHz G4 Powerbook
400MHz G4
Dual 867 G4
1GHz Powerbook
1.2 G5
Dual 2.0 G5
all panther, 10.3.5 etc. audio interfaces include Echo Indigo DJ, MOTU828, DIGI001, internal.
Posted: Mon Nov 01, 2004 10:19 pm
by vince watson
then how do you get rid of audio drop outs on a brand new PB17 1.5?
im desperate now...
Posted: Mon Nov 01, 2004 11:05 pm
by kent_sandvik
The first obvious place is to check out your latency settings in the Preferences, and increase the buffer sizes. If you do playback or mixing, it's quite OK to increase it, if you record, it's a bummer to calculate latencies while recording a guitar...
Why there are latencies? HW setup, CPU speed, driver quality, the A/D box you are using, USB latencies, a large part has to do with your HW setup and the drivers involved. It always helps to at least try to get the latest drivers for your A/D box or card if possible, maybe old bugs have been fixed.
--Kent
Posted: Mon Nov 01, 2004 11:05 pm
by kovacs
Hm. I have no problems on my PB 1 Ghz.
Posted: Mon Nov 01, 2004 11:06 pm
by kent_sandvik
Oh, I forgot to mention, Live 4.0.x (including 4.0.4) has worked with no flaws so far with my 2x867Mhz 10.3.5 PowerMac. --Kent
Posted: Mon Nov 01, 2004 11:45 pm
by bensuthers
> then how do you get rid of audio drop outs on a brand new PB17 1.5?
ok. just installed the demo on a new PB17 1.5 here at work and no problems at all.
so...more information.....what precisely are you doing? how many tracks? plugins? what plugins? what audio interface?
Posted: Tue Nov 02, 2004 12:04 am
by noisetonepause
No (new) problems here, either. iBook G3 900, 384 MB RAM, EMI 2/6/Built-in (depending on location).
-Paws
Posted: Tue Nov 02, 2004 1:05 am
by vince watson
seems the few poeple i have been speaking to are the unlucky ones here......i aint using no plug ins, no input audio, only samples on NO HiQ mode and some ableton fx(not reverb).
i should not be having any problems either
im running
maudio audiophile firewire
panther 10.3.5
17" PB 15.gz
4.0.4 live
Posted: Tue Nov 02, 2004 1:07 am
by bensuthers
it seems as if everybody I talk to who is experiencing dropouts is using m-audio products.
Posted: Tue Nov 02, 2004 1:08 am
by kent_sandvik
I'm using M-Audio FireWire 410 and I don't see dropouts, unless the latency settings are really low. --Kent
Posted: Tue Nov 02, 2004 1:13 am
by vince watson
yeah....the console errors that im reading are apparently external soundcard errors....looks like m-audio is not soooo reliable
maybe i jumped the gun a little shouting abuse at ableton after all

im getting very frustrated at this problem.....
any suggestions for an alternative external soundcard??
thanks guys
Posted: Tue Nov 02, 2004 1:16 am
by kent_sandvik
Start with, try to get the latest drivers. If it still fails, save all output from the console and make an M-Audio support email over at the
www.m-audio.com web site. It might help to post the output here too, in case someone else has seen it and could point out what's going on. - -KIent
Posted: Tue Nov 02, 2004 1:18 am
by vince watson
the messages are on the other post i made....
here is a brief one
localhost kernel: IOAudioStream[0x148cc00]::clipIfNecessary() - Error: attempting to clip to a position more than one buffer ahead of last clip position (416c9,219)->(416ce,69).
all drivers are upto date......
Posted: Tue Nov 02, 2004 1:26 am
by kent_sandvik
That's funny, a Google search showed source code from Darwin showing where the error is triggered:
http://www.opensource.apple.com/darwins ... Stream.cpp
All I could think of is that it's a buffer overrun, something is pumping in too much data... Maybe the driver. Try to run with a lower sampling rate, if that works, then maybe there's a clue what's going on. Or try to set fewer buffers in Live so see what happens. I would still be wary about the driver itself... --Kent