22 Sep
2004
22 Sep
'04
11:33 p.m.
Hi Jan, how are u? any new songs recorded from your band?
Hello to everyone.
--- Jan Depner <eviltwin69(a)cableone.net> wrote:
Louis,
I've used this card before and it works well. A couple of questions -
are you running 2.4 or 2.6 kernel? Are you running as root? One
important thing with the ens1370/71 - always use -r 48000! The card
will produce tons of xruns at 44100 because it's native mode is 48K.
I'm running as root the whole time. 2.4.25-multimedia kernel from Agnula/DeMuDi.
I did try to run jackd at 48Khz rate initially, but at that point of time I didn't
notice the
xruns because I was only trying to test the card (maybe 2 weeks ago...). So I can't
recall the
behaviour of this card at 48khz...not much impression.
What I can remember from the time I ran jackd@48Khz and ardour was this: Ardour thinks
that the
card is sampling at 47Khz! It shows up on the Ardour window. I find this odd because most
of the
time I see common sampling rate 44khz,48khz but not 47khz. I asked this question on one of
the IRC
channels and was told that no card really samples exactly at 48khz. For this
"odd" sampling rate
reason and also most of the drum samples I use are at 44khz. I just set myself to record
everything at 44khz and didn't look at 48khz. So i kind of refrained from it for a
while :)
But thanks for the tip... perhaps I should try that again.
When i'm not having XRuns, I do have quite a number of "late driver wakeup"
messages when running
with this card though. They appear quite frequently. I don't quite understand what
this means
though. So far I can't find information/explanation for this. I was still able to
record with
Ardour a track at a time while playing back the recorded stuff at the same time for 2
minutes
without pops, hisses and dropouts. I'm quite sure I can record more than 2 minutes
under this
situation(2 minutes because I start to run out of ideas... not because the system
can't take it
;-P).
I have also tried to record with ardour with plugins on (don't have a guitar amp so
using the CAPS
ladspa plugins), when I do that sometimes I get xruns and jack complains ardour is not
"fast"
enough or something like that. For dry signals normally its not much of an issue.
Thanks a lot,
Louis
Jan
On Wed, 2004-09-22 at 01:48, Louis Lam wrote:
________________________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping"
your friends today! Download Messenger Now
http://uk.messenger.yahoo.com/download/index.html
Hi All,
No reply so far to this post, but its alright... maybe you guys are busy.
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.
Couldn't find any previous post on this.
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?
Thank you guys, my experience in Linux Audio has been pleasant so far.
Many Thanks,
Louis
--- Louis Lam <lshoujun(a)yahoo.com> wrote:
> Hello All,
>
> I have a bunch of old consumer sound cards. SBLive, Vibra128 and ensoniq
1370(es1370). I
went
> through quite a number of rounds trying out
these cards and found that IMHO the es1370 gave
me
> the
> best sound amongst these cards. So i went ahead and try to start jack according to
the
> capabilities of this card.
>
> With this card, i find that once i start jackd like this:
>
> jackd -v -R -d alsa es1370 -r 44100
>
> I get lots of xruns immediately.
>
> Then i tried with the n=4 (ie 4 periods per hardware buffer), i.e "jackd -v -R
-d alsa
es1370 -n
> 4" and I am able to get rid of the
xruns. But i see lots of "late driver wakeup: nframes to
> process=2048" on the jackd output. What does this message mean?
>
> For recording into ardour, n=4 and the default frames per period (1024) gives me
quite
> significant
> latency when recording. e.g when I pluck a note on the electric bass i can hear it
on the
> line-in
> monitor first and then from the capture slightly later.
>
> As a compromise, i set the frames per period to either 64, 128 or 256. But I still
get the
> "late
> driver wakeup" message and occasional xrun when i quit ardour or sometimes even
hydrogen. I
> notice
> that when quitting jackd programs there will sometimes be a few xruns. Is this
normal?
>
> Seems like ideal to start n=2 but this card don't seem to allow me to do that. I
could be
wrong
> but i think for low latency n=2 is ideal.
>
> If i have saved an ardour project with Tim Goetze's plugin activated in some
tracks, ardour
may
> report that it is too slow or (something
like that) when i reload that project file. I
suspect
> this is to do with some ladspa plugins
requiring low latency which my setup is not able to
give.
>
> I know this card is old, but it does give a great sound. I used SBLive previously
and don't
seem
> to have these latency issues (able to start
jack with n=2). For owners of this card, any
sound
advice to
get the most out of it?
Thank You very much,
Louis
________________________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping"
your friends today! Download Messenger Now
http://uk.messenger.yahoo.com/download/index.html
________________________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping"
your friends today! Download Messenger Now
http://uk.messenger.yahoo.com/download/index.html