Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Soto <soto@informatik.uni-kl.de>
To: alsa-devel@lists.sourceforge.net
Subject: Re: plug:iec958 problems
Date: Wed, 21 Apr 2004 20:57:37 +0200	[thread overview]
Message-ID: <1082573856.1244.11.camel@masoft> (raw)
In-Reply-To: <s5hfzazq6li.wl@alsa2.suse.de>

Hello Takashi!

On Tue, 2004-04-20 at 12:36, Takashi Iwai wrote:
> At Sat, 17 Apr 2004 22:58:57 +0200,
> Martin Soto wrote:
> > As an additional note, this only seems to happen when using plug:iec958.
> > Software decoding the AC3 sound and plying through ALSA, works
> > flawlessly, despite of the fact that the machine load is higher.
> 
> is there any different if you get rid of plug: ?
> as long as the h/w support 16bit LE data, AC3 should work without
> plug.

I just tested. There seems to be no difference. I tried with iec958: and
spdif: instead of plug:iec958:. The problem persists. 

As I said, putting the process in SCHED_FIFO mode doesn't make any
difference at all. Almost any machine activity (any process being active
for more than a fraction of a second) is enough to interrupt the sound.
Does the library use some auxiliary process to play through spdif?

M. S.
-- 
Martin Soto <soto@informatik.uni-kl.de>



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

  reply	other threads:[~2004-04-21 18:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-17 20:58 plug:iec958 problems Martin Soto
2004-04-20 10:36 ` Takashi Iwai
2004-04-21 18:57   ` Martin Soto [this message]
2004-04-22 10:03     ` 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=1082573856.1244.11.camel@masoft \
    --to=soto@informatik.uni-kl.de \
    --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