From: Pavel Hofman <pavel.hofman@insite.cz>
To: Demian Martin <demianm@attglobal.net>
Cc: alsa-devel@alsa-project.org
Subject: Re: Via VT82xx VT1708 ICE1724HT and higher
Date: Tue, 26 Feb 2008 21:47:52 +0100 [thread overview]
Message-ID: <47C47AF8.1070005@insite.cz> (raw)
In-Reply-To: <004401c878a2$6cade570$d450a8c0@PDSMain2>
Demian Martin wrote:
> Pavel:
> Thanks for the insight. I thought I was doing something wrong since no one
> else has noticed.
I was surprised too I could not google any complaints.
> I tried your suggestion to use plughw:0,1 and the verbose output looks
> fine, the data rate shifts fine (I'm watching the L/R clock on the input to
> the DAC on an external DAC) but no audible sound comes out the converter
> unless it's a 16 bit 44.1 file. The 24 bit stuff is not getting converted
> into something useful to the DAC. Should I check to see if the data clock is
> 48X the LR clock?
>
> What info do you need from me to look deeper?
Which card are you using? Juli driver in alsa is not really functional.
E.g. Prodigy 192 (standard clock arrangement) has no problem with 24bit
SPDIF-OUT.
>
> I looked at the Plug plugin but have not been able to figure out how to
> configure it for my needs. There is way too much marginal information on the
> web and little that directs me to an optimum setting.
> -Demian
>
I do not think the plug plugin needs any configuration. It compares
input stream parameters with the card capabilities supplied by the
driver and does appropriate conversions.
Pavel.
next prev parent reply other threads:[~2008-02-26 20:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2073.1204045163.2095.alsa-devel@alsa-project.org>
2008-02-26 18:07 ` Via VT82xx VT1708 ICE1724HT and higher Demian Martin
2008-02-26 20:47 ` Pavel Hofman [this message]
2008-02-27 6:46 ` Demian Martin
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=47C47AF8.1070005@insite.cz \
--to=pavel.hofman@insite.cz \
--cc=alsa-devel@alsa-project.org \
--cc=demianm@attglobal.net \
/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.