audio glitches - not good.

UHE is now closed. For Technical Support from Ableton, please go here: http://www.ableton.com/support
Locked
elemental
Posts: 930
Joined: Sun Jun 20, 2004 7:42 pm
Location: London
Contact:

audio glitches - not good.

Post by elemental » Mon Oct 11, 2004 11:27 am

I'm getting very annoying audio glitches, and CPU meter is not super-high... about 50-70% although when it goes higher than 70-75% it gets really annoying.

I have a two-bar loop, and every time it does 4 bars theres a noticeable glitch at the beginning of the bar. It ruins the whole flow of the tune!

I'm using: Sony Vaio P4 2.4Ghz, 512Mb, Carillon external firewire drive (7200rpm) and MOTU 828 Mk1.

jardim do mar
Posts: 25
Joined: Mon Jul 12, 2004 11:47 pm

Re: audio glitches - not good.

Post by jardim do mar » Mon Oct 11, 2004 4:17 pm

elemental wrote:I'm getting very annoying audio glitches, and CPU meter is not super-high... about 50-70% although when it goes higher than 70-75% it gets really annoying.

I have a two-bar loop, and every time it does 4 bars theres a noticeable glitch at the beginning of the bar. It ruins the whole flow of the tune!

I'm using: Sony Vaio P4 2.4Ghz, 512Mb, Carillon external firewire drive (7200rpm) and MOTU 828 Mk1.

As a test ,,did you try using audio files that are in your internal drive?

if you're using mme or dx drivers have you tried adjusting the input and output latency sliders?

George
Posts: 23
Joined: Fri Jul 09, 2004 4:18 am

Me too

Post by George » Tue Oct 12, 2004 4:40 pm

I getting this type of glitches too! :cry:
MacBook Pro I7 2.2 Ghz / 16Gb ram
Live 9.7 64-bit
RME Hammefall DSP Multiface
Mackie HR824
Korg Taktile 49 / M-Audio trigger Finger / Behringer BCR 2000

monarkeys
Posts: 35
Joined: Tue Oct 12, 2004 10:31 pm
Location: Pacifica, CA

Glitches are common

Post by monarkeys » Tue Oct 12, 2004 10:37 pm

I am running on a 1GHz Powerbook with either MOTU 896 or Mbox and often see glitches when running at around 60% CPU bandwidth.

This happens in DP as well as in Live.

This is worse when running at low buffer settings (low latency).

I am guessing that the time it takes to shuffle data in and out of the buffers is not reflected in the CPU bandwidth display (?) - either that, or there is a "peak" in the CPU usage that is too fast to show up on the meter.

Locked