From: Jaroslav Kysela <perex@perex.cz>
To: alsa-devel@alsa-project.org
Subject: Re: bug in alsa-utils 1.0.28 - arecord
Date: Tue, 21 Oct 2014 08:39:41 +0200 [thread overview]
Message-ID: <5445FFAD.1050107@perex.cz> (raw)
In-Reply-To: <CAC_TXnmZcBcXSgGH6JgsjwhN9jeruo3YbEzcrbGSxb-M5Mq5oQ@mail.gmail.com>
Dne 20.10.2014 v 21:33 Jordan Kagan napsal(a):
> Hello,
>
> I encountered an issue with using the arecord binary in this most recent
> version. When using the '-d' duration flag, the program will continue to
> open files AFTER the duration has expired. The issue occurs when the
> capture() while loop hits the break due to a value returned by pcm_read().
> When the while loop is exited, the program hits the do-while loop and
> continues to open files indefinitely. If rcount is returned from
> pcm_read() instead of "result", the problem does not occur.
Yes, I fixed it here:
http://git.alsa-project.org/?p=alsa-utils.git;a=commit;h=8f361d83cfcb39887f5fc591633e68d9448e3425
I'm going to release 1.0.29 soon.
Jaroslav
--
Jaroslav Kysela <perex@perex.cz>
Linux Kernel Sound Maintainer
ALSA Project; Red Hat, Inc.
prev parent reply other threads:[~2014-10-21 6:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 19:33 bug in alsa-utils 1.0.28 - arecord Jordan Kagan
2014-10-21 6:39 ` Jaroslav Kysela [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=5445FFAD.1050107@perex.cz \
--to=perex@perex.cz \
--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