Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001651]: ac3 passthrough not really work with ac3dec
Date: Wed, 14 Dec 2005 10:53:32 +0100	[thread overview]
Message-ID: <39379cbfe2a2dd85b9b8afa2458f2a67@bugtrack.alsa-project.org> (raw)


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1651> 
======================================================================
Reported By:                tycordinal
Assigned To:                
======================================================================
Project:                    ALSA - driver
Issue ID:                   1651
Category:                   PCI - emu10k1
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Distribution:               
Kernel Version:             2.4.31
======================================================================
Date Submitted:             12-14-2005 09:44 CET
Last Modified:              12-14-2005 10:53 CET
======================================================================
Summary:                    ac3 passthrough not really work with ac3dec
Description: 
using the following from alsa-tools to play ac3 as passthrough:
ac3dec -C oneac3file.ac3 


the ac3dec is able to "open" the spdif device "iec958:{AES...}" and did
not report any error and keep on running, but the ac3 decoder (creative
ddts-100), connected to the "spdif output" from the card, did not switch
to dolby mode, and no sound come out from speaker.

one interesting thing is, when I run this:
ac3dec -6 oneac3file.ac3 

As this is software decoding to PCM, I can hear the left/right channels
from the front stereo jacket, as they also output on the "spdif output".
Therefore, I believe the "spdif output" on the card is indeed working,
just that for this card we might need to write some different AES command
to open the spdif output?

I am not sure if the alsa config files in /usr/share/alsa have to change
or maybe some "switches" in emu10k1_main.c needs to apply for the "spdif
output" to  really behave as "iec958" device to passthough ac3 stream to
external decoder.

Thanks.





======================================================================

----------------------------------------------------------------------
 tycordinal - 12-14-05 10:31 
----------------------------------------------------------------------
interesting things:

when doing ac3dec -6 oneac3file.ac3 ,
there is sound coming out from the spdif output, and when i use alsamixer
to make "IEC958 Optical Raw" from "MM" to become "OO", the sound stop
coming out. When I make it as "MM", the sound come back again. In this
case, alsamixer can toggled the sound output, if spdif output is playing
digital stereo.

when doing ac3dec -C oneac3file.ac3,
alsamixer show "IEC958 Optical Raw" as "OO" , and there is no dolby light
on the decoder (creative DDTS-100). when I make it "MM", there is still no
dolby light.  when I exit alsamixer and run alsamixer again, "IEC958
Optical Raw" has become "OO". In this case, alsamixer cannot help to get
ac3 passthough from the spdif output, because it cannot really make
"IEC958 Optical Raw" as "MM", even though it seems it can. After ac3dec
finished, "IEC958 Optical Raw" back to "MM" again, as shown by running
alsamixer again.

----------------------------------------------------------------------
 pzad - 12-14-05 10:53 
----------------------------------------------------------------------
IEC958 Optical Raw - this is just multiplexer switch.
If there is MM - this means spdif output comes from DSP and from normal
playback device.
If there is OO - spdif output comes from iec958 (or spdif) device.

Please do, what I suggest you in previous note.
Your problem is "Audigy Analog/Digital Output Jack" control.

Issue History
Date Modified  Username       Field                    Change              
======================================================================
12-14-05 09:44 tycordinal     New Issue                                    
12-14-05 09:44 tycordinal     Kernel Version            => 2.4.31          
12-14-05 10:05 tycordinal     Note Added: 0007031                          
12-14-05 10:15 tycordinal     Note Added: 0007032                          
12-14-05 10:16 tycordinal     Note Added: 0007033                          
12-14-05 10:30 pzad           Note Added: 0007034                          
12-14-05 10:31 tycordinal     Note Added: 0007035                          
12-14-05 10:53 pzad           Note Added: 0007036                          
======================================================================




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

             reply	other threads:[~2005-12-14  9:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-14  9:53 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-23 16:45 [ALSA - driver 0001651]: ac3 passthrough not really work with ac3dec bugtrack
2006-07-23 16:44 bugtrack
2006-07-18 12:43 bugtrack
2005-12-14  9:31 bugtrack
2005-12-14  9:30 bugtrack
2005-12-14  9:16 bugtrack
2005-12-14  9:15 bugtrack
2005-12-14  9:05 bugtrack
2005-12-14  8:44 bugtrack

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=39379cbfe2a2dd85b9b8afa2458f2a67@bugtrack.alsa-project.org \
    --to=bugtrack@alsa-project.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox