From: "Marcus Weigelt" <noize007@gmx.de>
To: alsa-devel@alsa-project.org
Subject: Re: User-space control elements in ext PCM plugin
Date: Wed, 07 Apr 2010 13:54:33 +0200 [thread overview]
Message-ID: <20100407115433.60020@gmx.net> (raw)
In-Reply-To: <hphqhb$839$1@dough.gmane.org>
Hi Colin,
thanks for your answer. In general the pulse plugin does more or less what I want - present controls in userspace, right.
But the PulsePlugin actually consists of two plugins, a PCM plugin (pcm_pulse.c) and control plugin (ctl_pulse.c).
As far as I understand, the control events/messages from the user space sliders are directed to the pulse audio server via the ctl_plugin. My question is actually, how to make use of them directly in the pcm plugin?
As I told, a similiar request was done three years ago:
http://article.gmane.org/gmane.linux.alsa.devel/50181
That´s where I got the idea of creating the user-space control elements directly inside of the PCM plugin, or did I get it wrong?
Marcus
-------- Original-Nachricht --------
> Datum: Wed, 07 Apr 2010 12:32:59 +0100
> Von: Colin Guthrie <gmane@colin.guthr.ie>
> An: alsa-devel@alsa-project.org
> Betreff: Re: [alsa-devel] User-space control elements in ext PCM plugin
> 'Twas brillig, and Marcus Weigelt at 07/04/10 11:01 did gyre and gimble:
> > Hi,
> >
> > I´m having an external PCM plugin that should do some processing on
> > the audio. That part works fine. Now I´d like to have some way to
> > modify the way to give some parameters to the plugin to tell it how
> > the processing is done (eg. set delay time, pan, attack time, ...).
> > I´ve searched the web for days and hours, but could not really find
> > something. On the alsa mailing list there was a similiar question
> > three years ago, and the answer was, that one could create user-space
> > control elements in the plugin. How is that done? I could not find
> > examples or good documentation about it. Did I miss something out?
> > Can anyone give me a hint, maybe a link to some docs about it or
> > source of a PCM plugin creating/using user space control elements?
> > Thanks a lot.
>
> Try looking at the PulseAudio plugin. It presents userspace sliders to
> control the volume. If I've not misunderstood your request this should
> do what you need.
>
> Col
>
> --
>
> Colin Guthrie
> gmane(at)colin.guthr.ie
> http://colin.guthr.ie/
>
> Day Job:
> Tribalogic Limited [http://www.tribalogic.net/]
> Open Source:
> Mandriva Linux Contributor [http://www.mandriva.com/]
> PulseAudio Hacker [http://www.pulseaudio.org/]
> Trac Hacker [http://trac.edgewall.org/]
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
next prev parent reply other threads:[~2010-04-07 11:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 10:01 User-space control elements in ext PCM plugin Marcus Weigelt
2010-04-07 11:32 ` Colin Guthrie
2010-04-07 11:54 ` Marcus Weigelt [this message]
2010-04-07 11:58 ` Jaroslav Kysela
2010-04-07 12:22 ` Marcus Weigelt
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=20100407115433.60020@gmx.net \
--to=noize007@gmx.de \
--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.