Re: [Alsa-user] Re: es1370 latency and jackd

[Louis L. <lsh...@ya...>]

Hey, thanks for the reply!

 --- Ben Bell <bj...@de...> wrote: 
> On Wed, Sep 22, 2004 at 07:00:31AM +0100, Louis Lam wrote:
> > I was thinking of two possibilities of why this is happening:
> > 1. The Soundcard itself: I'm not sure whether the card can take the polling
> > period of 2 by design.
> I've certainly managed good performance from 4 periods and 128 frames. I
> think (but could be wrong) that I pushed it a little lower too. Not sure.

I was able to do that, sometimes i feel lucky and do 4nx64p...will have xruns sometimes. But 4x128
wasn't too bad for recording a single track. I can pretty much hear the line input and capture
"almost" together.

One question though? Did you notice see the "late driver wakeup" messages in the xruns output
while you were on 4nx128p?
 

> > 2. The Driver. But I've not seen any report on this in the linux-audio-users or alsa list. Can
> this have impact on the late driver wakeup issue?
> 
> Some pointers:
> Are you running a low-latency kernel with the realtime-lsm module inserted?
Low-latency? Yes I'm running DeMuDi 1.2.0-rc3. That kernel has low-latency enabled.
realtime-lsm? Ok, that one I'm not sure, but how to check for that?

> The es1370 doesn't seem very happy in duplex mode. For what I was doing I
> found that switching it to playback only was fine.

Thats an option :) Playback only when adding guitar amp simulators like CAPs plugins. Normally I
record dry guitar tracks and tweak the sounds later (because i can't decide which sounds good 
;-P). But only until I try to solve the "late driver wakeup".

The xruns usually occurs during: 
1. When I exit Ardour...
2. When I have added effects to tracks in ardour (CAPs plugins like tube amp/preamp, impulse
convolver), saved the file, quit ardour, then reopen that file again in ardour.

Jack complains that Ardour wasn't "fast enough" or something like that then denied ardour. I
usually have to pull out all the plugins, save the file, then open it again for it to play in
ardour.

> Check PCI latencies -- this is what hurt me. Make the audio card the highest
> latency_timer value -- e.g. 128, and make sure everything else is down aroudn
> 32. http://www.affenbande.org/~tapas/wiki/index.php?PCI-Latencies is worth
> reading and indeed the whole wiki is very useful.

I usually set the latency_timer value to 248 for my soundcard via:
setpci -s 03:02.0 latency_timer=FF

In relation to the rest of the stuff: I have latency_timer of 32 on my AGP graphics card(RivaTNT).
I only have the sound card on my PCI slots.

I've turned off all ACPI, APICs so i'm pretty much using traditional PICs. My es1370 sound card is
using IRQ 9. 

When I started setting up this system I was using SBLive...it was placed at the same slot where I
could get irq 9. I don't recall seeing the "late driver wakeup" or xruns at that time. I was using
2nx512p. But because I was lucky enough to find the es1370 card at one of those repair stores and
paid S$5.00 for it, i decided to try it and i actually like the sound better :) Well, now this
latency thing.

I've forgotten to provide some more info, i'm using:
kernel 2.4.25x (can't recall the exact name but the one that came with DeMuDi)
jack version 0.94.0
alsa 1.0.5

Whats the version of alsa/jack you're using? 
Would an upgrade to an updated alsa driver (1.0.6)help in this case?

> 
> -- 
> +-----Ben Bell - "A song, a perl script and the occasional silly sig.-----+
>   ///      email: bj...@de...            www: http://www.deus.net/~bjb/
>   bjb    Don't try to drive me crazy... 
>   \_/                                        ...I'm close enough to walk. 
>  

Thanks a lot,
Louis

________________________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping" 
your friends today! Download Messenger Now 
http://uk.messenger.yahoo.com/download/index.html