Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: edoardo <edoardo@lastorina.it>
To: edoardo <edoardo@lastorina.it>
Cc: Peter Zubaj <pzad@pobox.sk>,
	James Courtier-Dutton <James@superbug.co.uk>,
	alsa users list <alsa-user@lists.sourceforge.net>,
	alsa developers' list <alsa-devel@lists.sourceforge.net>
Subject: Re: [Alsa-devel] Re: Re: emu10k1, sound blaster audigy two zs and digital output
Date: Wed, 15 Jun 2005 23:15:03 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.63.0506152311440.20549@localhost> (raw)
In-Reply-To: <Pine.LNX.4.63.0506152227060.15735@localhost>


dolby digital works fine now, with the new 1.0.9 modules : ) i hadn't 
thought about havin' an old alsa version, since i was usin' the kernel 
builtin modules, and all the alsa packages were 1.0.9 already... really 
had forgotten about alsa-driver : ) the dolby digital led even gets 
turned on on my dolby digital external decoder! thankyou very much for 
all the assistance, i'll post again if i have any problems! 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

      reply	other threads:[~2005-06-15 21:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-14 17:52 emu10k1, sound blaster audigy two zs and digital output edoardo
2005-06-14 18:23 ` [Alsa-user] " 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             ` edoardo [this message]

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.0506152311440.20549@localhost \
    --to=edoardo@lastorina.it \
    --cc=James@superbug.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=alsa-user@lists.sourceforge.net \
    --cc=pzad@pobox.sk \
    /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