From: edoardo <edoardo@lastorina.it>
To: alsa users list <alsa-user@lists.sourceforge.net>,
alsa developers' list <alsa-devel@lists.sourceforge.net>
Subject: emu10k1, sound blaster audigy two zs and digital output
Date: Tue, 14 Jun 2005 19:52:10 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.63.0506141947300.17981@localhost> (raw)
hi gals and dudes,
i'm postin' to both users and developers lists because both were tryin' to
solve my problem. i think i solved it. but i'm not sure, so here's what
i've done. i got my self an analogic stereo cable, and a converter jack
that converts it to rca. on the converter there's a label sayin' mono. i
plugged the stereo analogic cable into the digital output, and the other
rca converted end into the spdif in of my creativ dolby digital system.
now the system has the 'digital in' led turned on.
did i do somethin' that makes sense? cause my dolby digital system don't
have an optical in. everythin' seems to work digitally now. i'm a bit
confused do. did i do somethin' right? help! : ) thankyou! : )
ciao! : )
edoardo
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next reply other threads:[~2005-06-14 17:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-14 17:52 edoardo [this message]
2005-06-14 18:23 ` [Alsa-user] emu10k1, sound blaster audigy two zs and digital output James Courtier-Dutton
2005-06-14 22:22 ` edoardo
2005-06-14 22:42 ` James Courtier-Dutton
2005-06-14 23:50 ` edoardo
2005-06-14 23:59 ` edoardo
2005-06-15 19:33 ` Peter Zubaj
2005-06-15 20:37 ` [Alsa-user] " edoardo
2005-06-15 21:15 ` [Alsa-devel] " edoardo
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=Pine.LNX.4.63.0506141947300.17981@localhost \
--to=edoardo@lastorina.it \
--cc=alsa-devel@lists.sourceforge.net \
--cc=alsa-user@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