From: Sergey <sergemp@mail.ru>
To: alsa-devel <alsa-devel@alsa-project.org>
Cc: "Raymond Yau" <superquad.vortex2@gmail.com>
Subject: Re: alsa-lib: pcm_plug: fix float conversion for user specified ttable
Date: Tue, 17 Jun 2014 20:19:43 +0400 [thread overview]
Message-ID: <1403021983.990267259@f229.i.mail.ru> (raw)
In-Reply-To: <CAN8cciZvcjLTyOFSB-=Ret7FrG7ASGbkJSNo0xRVOZF7+et4sg@mail.gmail.com>
June 17 2014 Raymond Yau wrote:
>> Move custom ttable with equal channels case from a separate ttable_last
>> exception into a common plugins insertion loop.
>> Fixes plug with ttable for float pcms (jack, ladspa).
>> Example: aplay -fFLOAT_LE /dev/zero
>> pcm.!default {
>> type plug
>> slave.pcm { type null }
>> ttable.0.0 1
>> }
>
> Any reason to use type null in your test case since type null seem can
> support all format ?
It was the shortest test to reproduce the bug.
A more restricted config:
# aplay -fFLOAT_LE /dev/zero
pcm.!default {
type plug
slave.pcm { type null }
slave.format FLOAT_LE
ttable.0.0 1
}
But that test was enough to reproduce "Assertion failed" bug too.
Actually I've hit this bug with a complex ladspa upmixing code:
pcm.upmix {
type plug
slave.pcm {
type ladspa
slave.pcm {
type plug
slave.pcm "..."
ttable { ... }
}
plugins [ ... ]
}
ttable { ... }
}
similar to this:
http://forums.gentoo.org/viewtopic-p-4528619.html#4528619
This bug crashed the application for me (it generates SIGABRT)
so I thought that it should be fixed.
--
Sergey
next prev parent reply other threads:[~2014-06-17 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 15:52 alsa-lib: pcm_plug: fix float conversion for user specified ttable Sergey
2014-06-17 2:23 ` Raymond Yau
2014-06-17 16:19 ` Sergey [this message]
2014-06-17 13:06 ` Jaroslav Kysela
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=1403021983.990267259@f229.i.mail.ru \
--to=sergemp@mail.ru \
--cc=alsa-devel@alsa-project.org \
--cc=superquad.vortex2@gmail.com \
/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.