From: Charles Eidsness <charles.eidsness@ieee.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: External Plugin Non-Interleaved
Date: Wed, 21 May 2008 08:12:41 -0400 [thread overview]
Message-ID: <483411B9.5040204@ieee.org> (raw)
In-Reply-To: <s5htzgsvtbh.wl%tiwai@suse.de>
> At Tue, 20 May 2008 15:33:03 -0400,
> Charles Eidsness wrote:
>> I'm working on a small ALSA pcm/ctl plugin to add support for LADSPA modules
>> that include real-time controls (unless I'm missing something it looks like the
>> native ALSA LADSPA module doesn't include real-time adjustable controls). I want
>> to use it as a system wide equalizer. I'm using snd_pcm_extplug, I want to force
>> access to be non-interleaved only but I can't figure out how. Is there some way
>> to force non-interleaved access for an extplug?
Takashi Iwai wrote:
> No, extplug itself cannot restrict the access format, so far.
> It's possible to add a new restriction to extplug, though...
>
>
> Takashi
>
It would be a nice feature to have. I noticed that ioplug has that restriction,
could
the restriction code some ioplug just be pulled into extplug?
Charles
prev parent reply other threads:[~2008-05-21 12:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 19:33 External Plugin Non-Interleaved Charles Eidsness
2008-05-21 10:34 ` Takashi Iwai
2008-05-21 12:12 ` Charles Eidsness [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=483411B9.5040204@ieee.org \
--to=charles.eidsness@ieee.org \
--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