Anybody experiencing clicks and pops?
I am exchanging e-mails with Ableton support team about this problem, I'll let you know about it 
monosite.Hongkong
www.moneme.com
www.moneme.com
I'm on a pentium iv 2.5 gh/512 mb ram/winxp/live 4.0.3 and 4.0.4.D K wrote:i am having the same problem
seems to only be on the aux sends, the volume faders work clean.
this is crap- very limiting...
hope that4.5 is a fix...
btw, i'm on mac...
any of you pc users?
dk
Nothing strange happens when turning the knob, even switching the effect on and off (both in audio/midi tracks and return tracks).
Seems like it's a mac issue?
all the best and stay groovy
-
Turboschpeck
- Posts: 5
- Joined: Mon Dec 20, 2004 8:49 pm
I've found out important stuff about this topic
I don't know about mac, perhaps the problem is fixed with live 4.0.3 &
4.0.4 versions, thanx for the info. Clicks & pops aren't hardware's fault
pure software- this is what ableton support told me, patches should do the work if there are any
4.0.4 versions, thanx for the info. Clicks & pops aren't hardware's fault
pure software- this is what ableton support told me, patches should do the work if there are any
hi,
I have found a +solution+ for the clip(drop ...etc) and the high cpu use for macosx.
The problem come from the general latency.
With my rme for 44000 if I put 256 buffer sample(6ms lat), Live use 50-60 % cpu, for 512 (11ms) live use 30-35 % cpu, and for 1024 (23ms) live use 25-28% cpu... the drop out disappear.
I have made test for 48000 and 92000 .... the buffer is little more (1500-1600 sample) but also for 23ms.....
I dont no, If is the right way....( i am not one audio hardware specialist) but that's work for me.
Now, i go to test with jack server, for check if the problem comes with the core audio-midi and live.
see ya
fil
I have found a +solution+ for the clip(drop ...etc) and the high cpu use for macosx.
The problem come from the general latency.
With my rme for 44000 if I put 256 buffer sample(6ms lat), Live use 50-60 % cpu, for 512 (11ms) live use 30-35 % cpu, and for 1024 (23ms) live use 25-28% cpu... the drop out disappear.
I have made test for 48000 and 92000 .... the buffer is little more (1500-1600 sample) but also for 23ms.....
I dont no, If is the right way....( i am not one audio hardware specialist) but that's work for me.
Now, i go to test with jack server, for check if the problem comes with the core audio-midi and live.
see ya
fil
--> for info: http://www.music0films.info
--> Material:
--> Material:
- Macpro, Yamaha 01X, APC 40, Novation Nocturn 25 , Ableton Live + Max4live + Serato Scratch Live
- Macbook pro, RME multiface, Korg nanoPAD, nanoKeys, Ableton Live + Max4live
-
Turboschpeck
- Posts: 5
- Joined: Mon Dec 20, 2004 8:49 pm
By-pass wrote
The problem come from the general latency.
Which is not correct or this topic's concern, we are discussing about dropout problem which is not combined with cpu load, overall latency should be the smallest, the better sound- I use terratec phase 22, 64 sample- 96 khz, 0,7 ms latency. When using a smaller latency the overall dynamic range is better and micro dynamics are better. With smaller latency real punch sounds like real punch, not like slowed down unreal punch.
my cpu load is 10% when playing 4 tracks at the same time. The tracks are 32 bit, 96 khz, so the dropout is a software matter like the ableton support told me
The problem come from the general latency.
Which is not correct or this topic's concern, we are discussing about dropout problem which is not combined with cpu load, overall latency should be the smallest, the better sound- I use terratec phase 22, 64 sample- 96 khz, 0,7 ms latency. When using a smaller latency the overall dynamic range is better and micro dynamics are better. With smaller latency real punch sounds like real punch, not like slowed down unreal punch.
my cpu load is 10% when playing 4 tracks at the same time. The tracks are 32 bit, 96 khz, so the dropout is a software matter like the ableton support told me
which cpu?
the cpu you see in live or the cpu in the activity monitor?
When I speak about cpu is in the activity monitor.
My cpu monitor in live is around 5% .......... and in the activity monitor is around 50-60% use only for live with 256 buffer sample , this not really change if i am 44000 or 96000
see ya
the cpu you see in live or the cpu in the activity monitor?
When I speak about cpu is in the activity monitor.
My cpu monitor in live is around 5% .......... and in the activity monitor is around 50-60% use only for live with 256 buffer sample , this not really change if i am 44000 or 96000
see ya
--> for info: http://www.music0films.info
--> Material:
--> Material:
- Macpro, Yamaha 01X, APC 40, Novation Nocturn 25 , Ableton Live + Max4live + Serato Scratch Live
- Macbook pro, RME multiface, Korg nanoPAD, nanoKeys, Ableton Live + Max4live
-
Turboschpeck
- Posts: 5
- Joined: Mon Dec 20, 2004 8:49 pm
o.k, Live team is working on this problem and hopes to provide a solution soon. 
monosite.Hongkong
www.moneme.com
www.moneme.com
Hey and jezz!sniffio wrote:i don't think so.
I use 7200rpm.
I once consider using 15000rpm,
but this is a whole different issue.
When you shift the audio into effects so suddenly,
yes, there is a glitch.
Therefore, you should prepare your effects and audio before you move
either of them.
I'm wishing the same thing as you are.
I wish there weren't any glitches even when I move the
played clips into different tracks.
Hey, some day.
cheers
snif
Changing the drive to a faster one is a whole different issue. But it's not a bad idea anyway:
I switched from 7200 to 10000 rpm on my "Active Audio"-drive (s-ata), and that helped a lot when it comes to buffering samples/audiofiles - the cpu-spike's history from that very day! (but my "system"-drive is s-ata: 7200 rpm)
But i experience glitches when moving played clips into different tracks as well!
DAW: P4 Prescott (L2-1Mb) - 3.2Ghz - P875NEO (MSI) - 2Gb 400mhz rammo - XP Pro SP2 - mLAN2 (Firestation) running just sweet, and UAD-1 dsp-cards.
As you say, Sniff - some day..
Regs,
Jo