From: "Dr. Alexander K. Seewald" <alex@seewald.at>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Status of Dolby Digital on-the-fly encoding? (via a52 plugin)
Date: Tue, 18 Dec 2007 15:52:30 +0100 [thread overview]
Message-ID: <20071218145230.GA3861@sdg.at> (raw)
In-Reply-To: <s5hsl20xlce.wl%tiwai@suse.de>
On Tue, Dec 18, 2007 at 01:01:53PM +0100, Takashi Iwai wrote:
> > Problem seems to lie deeper...
> Sounds so. Which hardware and driver is it?
* NVidia CK804 (integrated into the motherboard MSI K8N Neo4 Platinum)
aplay -l:
card 0: CK804 [NVidia CK804], device 0: Intel ICH [NVidia CK804]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: CK804 [NVidia CK804], device 2: Intel ICH - IEC958 [NVidia
CK804 - IEC958]
Subdevices: 1/1
Subdevice #0: subdevice #0
* Alsa drivers 1.0.8-7 (= latest stable version on Debian Sarge)
[2.6.11 kernel, Debian sarge]
I used to have a wav-file which played 5.1 audio using these drivers,
but have misplaced it. But I think it was encoded into DTS 96/24 (96kHz,
24bit samples) which is IMHO not supported by any plugin. This means
that the connection probably works, but the internal hardware Dolby
Digital decoder is not happy with the format, right?
Best,
Alex
--
Dr. Alexander K. Seewald +43(664)1106886
Seewald Solutions
------------------------------------------------
Information wants to be free;
Information also wants to be expensive (S.Brant)
--------------- alex.seewald.at ----------------
next prev parent reply other threads:[~2007-12-18 14:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 13:22 Status of Dolby Digital on-the-fly encoding? (via a52 plugin) Dr. Alexander K. Seewald
2007-12-17 10:30 ` Takashi Iwai
2007-12-17 21:03 ` Dr. Alexander K. Seewald
2007-12-18 12:01 ` Takashi Iwai
2007-12-18 14:52 ` Dr. Alexander K. Seewald [this message]
2007-12-18 13:14 ` Takashi Iwai
2007-12-18 17:02 ` Dr. Alexander K. Seewald
2007-12-18 15:20 ` 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=20071218145230.GA3861@sdg.at \
--to=alex@seewald.at \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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.