From: Takashi Iwai <tiwai@suse.de>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: mulix@mulix.org, linux-kernel@vger.kernel.org
Subject: Re: looping S/PDIF data
Date: Mon, 02 Jun 2008 10:00:49 +0200 [thread overview]
Message-ID: <s5h4p8cb70u.wl%tiwai@suse.de> (raw)
In-Reply-To: <20080531112606.5884a1c9@mjolnir.drzeus.cx>
At Sat, 31 May 2008 11:26:06 +0200,
Pierre Ossman wrote:
>
> I have a minor annoyance with the snd_trident driver that I was hoping
> you might have a fix for:
>
> Pausing the output does not seem to take on the S/PDIF output. Analog
> outputs properly stop in their tracks, but the S/PDIF port keeps
> looping the current data buffer, which gives a rather unpleasant end
> result. :)
>
> Also, I was wondering if the hardware is capable of automatically
> shuffling data from the line in ADC to the S/PDIF port? The driver
> doesn't expose anything, but I don't know if that's because of missing
> code or missing hardware.
AFAIK, there is no analog loopback for SPDIF on trident. At least,
the driver doesn't support it.
The easiest way would be a software solution, e.g. use JACK, I
suppose.
Takashi
next prev parent reply other threads:[~2008-06-02 8:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-31 9:26 Pierre Ossman
2008-06-02 8:00 ` Takashi Iwai [this message]
2008-06-17 19:55 ` Pierre Ossman
2008-06-18 7:24 ` Rene Herman
2008-06-19 10:05 ` [alsa-devel] " Takashi Iwai
2008-06-19 12:39 ` Jaroslav Kysela
2008-06-19 12:48 ` Takashi Iwai
2008-06-20 19:45 ` Pierre Ossman
2008-06-20 19:52 ` Rene Herman
2008-06-20 22:00 ` Pierre Ossman
2008-06-20 22:23 ` Rene Herman
2008-06-20 23:09 ` Pierre Ossman
2008-06-21 12:14 ` Rene Herman
2008-06-30 17:11 ` Pierre Ossman
2008-06-30 18:21 ` Rene Herman
2008-06-30 19:22 ` Pierre Ossman
2008-07-01 10:16 ` Takashi Iwai
2008-06-19 23:02 ` Pierre Ossman
2008-06-19 10:05 ` 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=s5h4p8cb70u.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=mulix@mulix.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
all inboxes | Powered by JetHome®