Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Lars Hagström" <lars@update.uu.se>
To: alsa-devel@lists.sourceforge.net
Subject: Re: Creative Mp3+ USB and SPDIF passthrough
Date: Tue, 11 Nov 2003 14:18:04 +0100	[thread overview]
Message-ID: <3FB0E18C.7040309@update.uu.se> (raw)
In-Reply-To: <Pine.LNX.4.53.0311111315120.1303@pnote.perex-int.cz>

Okay! Two responses, I'll try them as soon as I can!

Lars

Jaroslav Kysela wrote:

> On Tue, 11 Nov 2003, [ISO-8859-1] Lars Hagström wrote:
> 
> 
>>Hi,
>>
>>I've sent this mail once before, but since I've received no response I
>>send it again (only this once, I wont keep spamming...).
>>
>>I've scoured the net, the alsa-user list and this mailing list for
>>information about how to enable AC3/DTS passthrough on the S/PDIF
>>connector on my new Creative Mp3+ USB box.
>>The only thing I've been able to find is a vague reference saying
>>something that spdif passthrough is not available in usb-audio. Is this
>>the truth? If it is the truth, will it remain so forever, or is anyone
>>working on it?
>>If it is not true, what am I doing wrong? I can get regular stereo
>>output on the digital out. I've got the box set to digital only, which
>>I've worked out is a requirement in windows. I have tried playing stuff
>>both with "aplay -Dspdif" (is this correct?)  and with "mplayer -ac hwac3".
> 
> 
> You have wrong tests. Get alsa-tools, compile ac3dec and try this command:
> 
> ac3dec -Dhw:0,0 -C <your_ac3_file>
> 
> The volumes (probably PCM and Master) should be set to 0dB (you need
> probably trial and error path to determine the good values), otherwise
> the stream will be modified and the receiver will not understand. Simply,
> you need bit-to-bit copy without any modification of outgoing samples.
> 
> Anyway, it might be possible, that your receiver does rely on the
> non-audio bit set in the s/pdif protocol. In this case, we cannot help you
> until someone discover, how this settings can be applied to your hardware.
> 
> 						Jaroslav
> 
> -----
> Jaroslav Kysela <perex@suse.cz>
> Linux Kernel Sound Maintainer
> ALSA Project, SuSE Labs
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by: ApacheCon 2003,
> 16-19 November in Las Vegas. Learn firsthand the latest
> developments in Apache, PHP, Perl, XML, Java, MySQL,
> WebDAV, and more! http://www.apachecon.com/
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-devel



-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/

  reply	other threads:[~2003-11-11 13:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-11 11:34 Creative Mp3+ USB and SPDIF passthrough Lars Hagström
2003-11-11 12:09 ` karsten wiese
2003-11-11 12:19 ` Jaroslav Kysela
2003-11-11 13:18   ` Lars Hagström [this message]
2003-11-12 18:58   ` Lars Hagström
  -- strict thread matches above, loose matches on Subject: below --
2003-11-03 10:00 Lars Hagström

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=3FB0E18C.7040309@update.uu.se \
    --to=lars@update.uu.se \
    --cc=alsa-devel@lists.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox