alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Paul Menzel <paulepanter@users.sourceforge.net>
To: alsa-devel@alsa-project.org
Subject: Re: ALC892 optical SPDIF not working
Date: Sat, 31 Jul 2010 19:22:52 +0200	[thread overview]
Message-ID: <1280596972.4074.1.camel@mattotaupa> (raw)
In-Reply-To: <AANLkTin+BUQr0iVq3MT+O-dA6PYyZZF_QVcEdoM-xK9p@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1833 bytes --]

Am Freitag, den 30.07.2010, 14:03 +0200 schrieb Manuel Lauss:
> On Fri, Jul 30, 2010 at 1:59 PM, Takashi Iwai <tiwai@suse.de> wrote:
> > At Fri, 30 Jul 2010 13:32:40 +0200,
> > Manuel Lauss wrote:

> >> On Fri, Jul 30, 2010 at 12:24 PM, Manuel Lauss
> >> <manuel.lauss@googlemail.com> wrote:
> >> > On Fri, Jul 30, 2010 at 11:13 AM, Takashi Iwai <tiwai@suse.de> wrote:
> >> >> At Fri, 30 Jul 2010 10:00:13 +0200,
> >> >> Manuel Lauss wrote:
> >> >>>
> >> >>> Hello,
> >> >>>
> >> >>> I have a Gigabyte 890GX-based board with an ALC892 codec.
> >> >>> The optical SPDIF output does not work at all (i.e. no red light on
> >> >>> the cable), and the kernel prints
> >> >>> "ALSA hda_codec.c:407: Too many connections"
> >> >>> messages whenever sound is played (analog works, but I need
> >> >>> digital).
> >> >>
> >> >> Could you try the latest alsa-driver-snapshot?
> >> >>    ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
> >> >>
> >> >> I fixed a few things regarding digital I/O handling of Realtek codecs
> >> >> now, and fixed the too-many-connections bug there, too.
> >> >
> >> > I pulled from your tree: AC3/DTS passthrough works now, however "normal" audio
> >> > only works with 48kHz rate.
> >>
> >> Is there a way to insert an initial playback delay?  Under linux, the
> >> first 2-2.5 seconds
> >> of anything played are just silence; on windows audible playback
> >> starts immediately.
> >
> > It's the time for synchronization your digital receiver takes, I guess.
> > Maybe changing SPDIF status makes it resync, which happens at each
> > opening / closing the stream.
> 
> Yes, seems so. I've found a workaround in meantime.

Could you elaborate on the workaround please, so others having this
issue know it.


Thanks,

Paul

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2010-07-31 17:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-30  8:00 ALC892 optical SPDIF not working Manuel Lauss
2010-07-30  9:13 ` Takashi Iwai
2010-07-30 10:24   ` Manuel Lauss
2010-07-30 11:32     ` Manuel Lauss
2010-07-30 11:59       ` Takashi Iwai
2010-07-30 12:03         ` Manuel Lauss
2010-07-31 17:22           ` Paul Menzel [this message]
2010-07-31 23:32             ` Manuel Lauss
2010-08-02  8:02               ` Takashi Iwai
2010-08-02 16:03                 ` Takashi Iwai
2010-08-05 18:52                   ` Manuel Lauss
2010-08-05 20:11                     ` Takashi Iwai
2010-08-07  8:11                       ` Manuel Lauss
2010-08-09  6:13                         ` Takashi Iwai

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=1280596972.4074.1.camel@mattotaupa \
    --to=paulepanter@users.sourceforge.net \
    --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;
as well as URLs for NNTP newsgroup(s).