Bug#413671: More information required
adi at drcomp.erfurt.thur.de
Thu Mar 26 14:41:15 UTC 2009
On Wed, Mar 25, 2009 at 07:23:10PM +0200, David Baron wrote:
> > For me, this looks like a broken soundcard (ADC and DAC should not
> > differ) and/or a detuned audio clock in case of external synchronization
> > (I don't know your setup).
> I am using an older en1371 (since I hae no support for my pro-card, also an
I've googled a bit on the net, the en1371 is known to be broken, at
least with the ALSA driver. Other en1371 users have this 44099Hz
Here is what Paul Davis (jackd author) says:
15:14 < las> adi: its the ALSA driver and the h/w *design*
15:15 < las> adi: you could view it two ways. (1) the device doesn't run at the
correct rate, and unlike other devices, actually tells you this
(2) like most comparable devices, it doesn't run at the correct
rate, and unlike them it tells you about it
> I cannot say if a replacement card would fare and better here.
It probably would, almost every other card you can get. ;)
But there might be another way to give you a working setup: run jackd
with the dummy driver and use alsa_in and alsa_out to bridge to the
This way, your jackd will report 44100 to your application, alsa_out
then resamples to 44009.
Unfortunately, the current jackd package (0.116.1-4) doesn't come with
alsa_in and alsa_out, it'll be included in the next release.
If you need it right now, you can still grab the jackd source from
jackaudio.org, run configure (--prefix=/usr) and make, don't install
anything but copy the alsa_in and alsa_out binaries to /usr/local/bin
or somewhere else (to your home).
You then use jackd's dummy driver, either from qjackctl or directly,
i.e. jackd -d dummy -r 44100, start alsa_in, alsa_out and tapestrea,
rewire according to your needs and that's it.
Does this work?
mail: adi at thur.de http://adi.thur.de PGP/GPG: key via keyserver
More information about the pkg-multimedia-maintainers