From: Sergey <sergemp@mail.ru>
To: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: ALSA 1.0.28 release - Assertion failed
Date: Sat, 14 Jun 2014 16:11:04 +0400 [thread overview]
Message-ID: <1402747864.49543317@f431.i.mail.ru> (raw)
In-Reply-To: <539ACD9A.5040209@perex.cz>
Fri, 13 Jun 2014, Jaroslav Kysela wrote:
> ALSA 1.0.28 packages are available for testing at
>
> ftp://ftp.alsa-project.org/pub/testing/
>
> Please, report any issues. I expect to announce the release on Monday.
I get "Assertion failed" with plug for float data.
No patch yet. I'm still trying to understand how "plug" works.
The bug was in earlier alsa versions too. Was almost fixed by 2da7b0c2
(discussion http://thread.gmane.org/gmane.linux.alsa.devel/119358)
I first found it with a complex ladspa upmix config, like:
http://forums.gentoo.org/viewtopic-p-4528619.html#4528619
An easy way to see the assertion:
pcm.!default {
type plug
slave.pcm { type null }
ttable.0.0 1
}
# aplay -fFLOAT_LE /dev/zero
Playing raw data '/dev/zero' : Float 32 bit Little Endian, Rate 8000 Hz, Mono
aplay: pcm_plug.c:388: snd_pcm_plug_change_channels: Assertion `snd_pcm_format_linear(slv->format)' failed.
Aborted by signal Aborted...
--
Sergey
prev parent reply other threads:[~2014-06-14 12:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 8:15 [RFC PATCH] alsactl: Do not run udev rule before datadir is mounted David Henningsson
2014-06-13 8:26 ` Jaroslav Kysela
2014-06-13 9:05 ` David Henningsson
2014-06-13 9:11 ` Jaroslav Kysela
2014-06-13 9:20 ` Takashi Iwai
2014-06-13 9:33 ` David Henningsson
2014-06-13 10:08 ` ALSA 1.0.28 release - request for testing Jaroslav Kysela
2014-06-13 10:52 ` David Henningsson
2014-06-13 17:17 ` Jaroslav Kysela
2014-06-13 10:59 ` Alexander E. Patrakov
2014-06-13 17:19 ` Jaroslav Kysela
2014-06-13 11:02 ` David Henningsson
2014-06-13 17:19 ` Jaroslav Kysela
2014-06-14 12:11 ` Sergey [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=1402747864.49543317@f431.i.mail.ru \
--to=sergemp@mail.ru \
--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 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.