From: Takashi Iwai <tiwai@suse.de>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: Gregoire Favre <greg@ulima.unil.ch>, alsa-devel@lists.sourceforge.net
Subject: Re: How to put 16bit none audio PCM data stream into a 32bit none audio S/P-DIF transport stream?
Date: Tue, 08 Apr 2003 17:50:48 +0200 [thread overview]
Message-ID: <s5hn0j1q97r.wl@alsa2.suse.de> (raw)
In-Reply-To: <E192u0x-0007pF-00@sc8-sf-list1.sourceforge.net>
At Tue, 08 Apr 2003 10:28:09 -0400,
Paul Davis wrote:
>
> >I have an AC3 receiver which uses the bit flags of the S/P-DIF transport
> >stream for identifying none audio, and I use the cs46xx driver for my
> >Hercules Digifire 7.1 (under windows, using the included DVD player I
> >could have a real 5.1).
> >
> >Under linux using ALSA, all I get is a cliking sound... does anyone know
> >how I could solve this (without changing my hardware of course)?
> >
> >I have looked at the source, but it's far too complicated for me...
>
> define a new plughw PCM device in ~/.asoundrc, and use
> that. unfortunately, i don't know how to do that, i just know that you
> can do it.
i'm afraid that it's not so easy as it sounds. it strongly depends
on the hardware driver implementation...
about AC3, 32bit spdif is likely irrelevant. A52 (AC3) is usally
packed into normal 16bit frames.
does the click happen even if you use alsa-tool's ac3dec?
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb:
Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
next prev parent reply other threads:[~2003-04-08 15:50 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 14:02 How to put 16bit none audio PCM data stream into a 32bit none audio S/P-DIF transport stream? Gregoire Favre
2003-04-08 14:28 ` Paul Davis
2003-04-08 15:50 ` Takashi Iwai [this message]
2003-04-08 16:42 ` Gregoire Favre
2003-04-08 20:30 ` James Courtier-Dutton
2003-04-08 20:44 ` Gregoire Favre
2003-04-09 10:34 ` James Courtier-Dutton
2003-04-09 11:06 ` Gregoire Favre
2003-04-09 16:50 ` James Courtier-Dutton
2003-04-09 17:58 ` Gregoire Favre
2003-04-10 17:43 ` James Courtier-Dutton
2003-04-08 21:39 ` Benny Sjostrand
2003-04-08 20:55 ` Gregoire Favre
2003-04-08 21:28 ` James Courtier-Dutton
2003-04-08 21:55 ` Gregoire Favre
2003-04-09 6:59 ` Benny Sjostrand
2003-04-09 8:28 ` Gregoire Favre
2003-04-09 11:09 ` Takashi Iwai
2003-04-09 11:43 ` Gregoire Favre
2003-04-09 13:11 ` Takashi Iwai
2003-04-09 17:58 ` Gregoire Favre
2003-04-10 11:21 ` James Courtier-Dutton
2003-04-10 11:26 ` Gregoire Favre
2003-04-13 11:41 ` Benny Sjostrand
2003-04-13 17:05 ` Gregoire Favre
2003-04-13 18:21 ` Benny Sjostrand
2003-04-13 18:30 ` Gregoire Favre
2003-04-13 23:23 ` Benny Sjostrand
2003-04-14 19:06 ` Gregoire Favre
2003-04-14 22:20 ` Benny Sjostrand
2003-04-14 21:27 ` Gregoire Favre
2003-04-14 23:00 ` Benny Sjostrand
2003-04-14 22:14 ` Gregoire Favre
2003-04-09 21:17 ` Benny Sjostrand
2003-04-09 20:38 ` Gregoire Favre
-- strict thread matches above, loose matches on Subject: below --
2003-04-08 23:33 Peter Heatwole
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=s5hn0j1q97r.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=greg@ulima.unil.ch \
--cc=paul@linuxaudiosystems.com \
/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.