From: Pavel Hofman <pavel.hofman@insite.cz>
To: Takashi Iwai <tiwai@suse.de>
Cc: ALSA Developers <alsa-devel@alsa-project.org>
Subject: Re: AK4114 - capturing spdif input stops the stream
Date: Fri, 14 Mar 2008 18:15:00 +0100 [thread overview]
Message-ID: <47DAB294.3090502@insite.cz> (raw)
In-Reply-To: <s5hfxuts2i6.wl%tiwai@suse.de>
Takashi Iwai wrote:
>> Takashi, thanks for the patch, it works flawlessly.
>
> OK, now committed to HG tree.
Thanks a lot. I will just resolve the conflicts now :)
>> Another issue - when the external clock changes rate and the stream is
>> running (typically when starting the source playback which switches the
>> source card (and its SPDIF-OUT) to a different frequency), the target
>> card detects the change and the capture stream is stopped in
>> snd_ak4114_check_rate_and_errors() by
>>
>> snd_pcm_stop(ak4114->capture_substream, SNDRV_PCM_STATE_DRAINING);
>>
>> How should recording applications behave with stream in this mode? I
>> would expect arecord to close, but it does nothing. Is this correct
>> behaviour?
>
> It's supposed to be drained then stopped. Maybe something wrong in
> the handling of DRAINING state in the capture direction.
>
> Anyway, it's a bit strange situation as is. Since the sample rate is
> changed, you can't call simply prepare again like normal errors...
I would expect arecord to quit with some relevant message. In larger
recording apps, e.g. Audacity, it should probably stop recording and
display a warning message. No idea if the controlled stop with an
appropriate error message is feasible with the existing API and code.
Thanks,
Pavel Hofman.
prev parent reply other threads:[~2008-03-14 17:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 22:50 AK4114 - capturing spdif input stops the stream Pavel Hofman
2008-03-13 7:50 ` Takashi Iwai
2008-03-13 12:49 ` Pavel Hofman
2008-03-13 13:57 ` Takashi Iwai
2008-03-13 14:11 ` Pavel Hofman
2008-03-13 19:18 ` Pavel Hofman
2008-03-14 16:18 ` Takashi Iwai
2008-03-14 17:15 ` Pavel Hofman [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=47DAB294.3090502@insite.cz \
--to=pavel.hofman@insite.cz \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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