From: Rene Herman <rene.herman@keyaccess.nl>
To: Pierre Ossman <drzeus@drzeus.cx>
Cc: ALSA devel <alsa-devel@alsa-project.org>,
linux-kernel@vger.kernel.org, mulix@mulix.org
Subject: Re: looping S/PDIF data
Date: Wed, 18 Jun 2008 09:24:59 +0200 [thread overview]
Message-ID: <4858B84B.4030800@keyaccess.nl> (raw)
In-Reply-To: <20080617215504.3203a5ed@mjolnir.drzeus.cx>
On 17-06-08 21:55, Pierre Ossman wrote:
> Ping
>
> On Sat, 31 May 2008 11:26:06 +0200
> Pierre Ossman <drzeus-list@drzeus.cx> 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. :)
Try the alsa-devel list...
Rene.
WARNING: multiple messages have this Message-ID (diff)
From: Rene Herman <rene.herman@keyaccess.nl>
To: Pierre Ossman <drzeus@drzeus.cx>
Cc: mulix@mulix.org, linux-kernel@vger.kernel.org,
ALSA devel <alsa-devel@alsa-project.org>
Subject: Re: looping S/PDIF data
Date: Wed, 18 Jun 2008 09:24:59 +0200 [thread overview]
Message-ID: <4858B84B.4030800@keyaccess.nl> (raw)
In-Reply-To: <20080617215504.3203a5ed@mjolnir.drzeus.cx>
On 17-06-08 21:55, Pierre Ossman wrote:
> Ping
>
> On Sat, 31 May 2008 11:26:06 +0200
> Pierre Ossman <drzeus-list@drzeus.cx> 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. :)
Try the alsa-devel list...
Rene.
next prev parent reply other threads:[~2008-06-18 7:24 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-31 9:26 looping S/PDIF data Pierre Ossman
2008-06-02 8:00 ` Takashi Iwai
2008-06-17 19:55 ` Pierre Ossman
2008-06-18 7:24 ` Rene Herman [this message]
2008-06-18 7:24 ` Rene Herman
2008-06-19 10:05 ` Takashi Iwai
2008-06-19 10:05 ` [alsa-devel] " Takashi Iwai
2008-06-19 12:39 ` Jaroslav Kysela
2008-06-19 12:39 ` [alsa-devel] " Jaroslav Kysela
2008-06-19 12:48 ` Takashi Iwai
2008-06-19 12:48 ` [alsa-devel] " Takashi Iwai
2008-06-20 19:45 ` Pierre Ossman
2008-06-20 19:45 ` [alsa-devel] " Pierre Ossman
2008-06-20 19:52 ` Rene Herman
2008-06-20 19:52 ` [alsa-devel] " Rene Herman
2008-06-20 22:00 ` Pierre Ossman
2008-06-20 22:00 ` [alsa-devel] " Pierre Ossman
2008-06-20 22:23 ` Rene Herman
2008-06-20 22:23 ` [alsa-devel] " Rene Herman
2008-06-20 23:09 ` Pierre Ossman
2008-06-20 23:09 ` [alsa-devel] " Pierre Ossman
2008-06-21 12:14 ` Rene Herman
2008-06-21 12:14 ` [alsa-devel] " Rene Herman
2008-06-30 17:11 ` Pierre Ossman
2008-06-30 17:11 ` [alsa-devel] " Pierre Ossman
2008-06-30 18:21 ` Rene Herman
2008-06-30 18:21 ` [alsa-devel] " Rene Herman
2008-06-30 19:22 ` Pierre Ossman
2008-06-30 19:22 ` [alsa-devel] " Pierre Ossman
2008-07-01 10:16 ` Takashi Iwai
2008-07-01 10:16 ` [alsa-devel] " Takashi Iwai
2008-06-19 23:02 ` Pierre Ossman
2008-06-19 23:02 ` [alsa-devel] " Pierre Ossman
2008-06-19 10:05 ` Takashi Iwai
2008-06-19 10:05 ` [alsa-devel] " 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=4858B84B.4030800@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=alsa-devel@alsa-project.org \
--cc=drzeus@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.