From: mike start <mike.start@ntlworld.com>
To: alsa-devel@alsa-project.org
Subject: ice1712 and jack
Date: Mon, 29 Dec 2008 23:22:54 +0000 [thread overview]
Message-ID: <49595BCE.9050603@ntlworld.com> (raw)
I've been having difficulty getting an ews88MT (ice1712 chipset) to work
in full duplex using the jack audio server (jackd). Capture only mode
works fine, even down to 64 samples latency, Playback only mode works
fine down to 64 samples latency. Duplex mode causes 'xruns' at even
2048 samples latency. Looking at the interrupt handler, if I add some
diagnostics to tell me the difference between the capture and playback
DMA counters timing out I see what appears to be clock drift between the
playback and capture halves of the ice1712. I also added some debug
messages to show what sample rate the alsa driver was setting the
hardware to and it agrees with the rate set in my jackd invocation
(jackd -R -d alsa -n 2 -p 1024 - r 48000 -d hw:0,0)
Also adding diagnostics to jackd to show the time spent in poll waiting
for the capture and playback interrupts shows that they start in sync
and gradually drift until an 'xrun' occurs when they are '-p' samples
apart. According to the ice1712 data sheet the 'professional'
multitrack part of this chip (the part my soundcard is using) runs its
inputs and outputs from the same master clock so I'm puzzled as to why
they are drifting. Does anybody have any more information relating to
the ews88mt? - I think the drivers are working fine but the problems
are being caused by the capture and playback not being quite in sync
which renders it almost useless for professional recording. Anyone have
any suggestions?
next reply other threads:[~2008-12-29 23:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 23:22 mike start [this message]
2009-01-07 11:49 ` ice1712 and jack Takashi Iwai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49595BCE.9050603@ntlworld.com \
--to=mike.start@ntlworld.com \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.