From: Takashi Iwai <tiwai@suse.de>
To: manuel.jander@mat.utfsm.cl
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Volume Peak display
Date: Wed, 24 Sep 2003 18:34:34 +0200 [thread overview]
Message-ID: <s5hisnikuw5.wl@alsa2.suse.de> (raw)
In-Reply-To: <1064414023.1630.11.camel@localhost>
At Wed, 24 Sep 2003 10:33:43 -0400,
Manuel Jander wrote:
>
> Hi Takashi,
>
> I was thinking that wouldn't it be a good idea to have a "visualization"
> category for alsa controls ? Or at least some naming scheme that allows
> to identify controls that should just show some data, like VU meters, or
> the hardware EQ peak i'm implementing for the aureal vortex.
well, the volatile flag should be used for such a purpose.
if it's set, the control change won't be notified to the application.
the application which shows these controls must re-read the data
periodically (not passively like others).
the other flag name might be more obvious, though.
>
> > >
> > > - The peaks doesnt get updated by alsamixer nor alsamixergui.
> > > I set the "volatile" flag, but is doesnt have any effect.
> >
> > this is inteintional.
> > (otherwise it will be too heavy for terminals over a slow network
> > connection :)
> >
> > for these purposes, we'll need anyway a special mixer app like
> > envy24control.
>
> Ok. I got it. I'll start writing our "Vortex turbo mixer" as soon as i
> can :-)
>
> > > - Alsamixer shows only 4 of the peak control set (20 total), and other
> > > mixers just show 2 of them.
> >
> > maybe the result of abstraction by simple-mixer API.
> >
> > > - The controls are declared as read only, but i can change their value.
> > > This shouldn't be allowed.
> >
> > really? then it must be fixed.
> > could you elaborate how this can happen?
>
> This could be a problem of the mixer app. I mean that i can modify the
> sliders on alsamixer or alsamixergui. The alsalib doesnt try to invoke a
> "control_put()" function (which is correct), since that would yield a
> segfault (i didnt implemented the control_put(), because that would be
> nonsense).
>
> What i wanted to say, is that it shouldn't be possible in a mixer app to
> "Move" sliders from readonly controls. Their appearance should be
> different too. They should look like "progress bars" or something else.
> Or better than that, VU meters should look like VU meters :)
agreed. at least, showing the elements with volatile in alsamixer
doens't make sense unless alsamixer shows vu meter (hey, it's not bad
:)
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-09-24 16:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-20 5:11 Volume Peak display Manuel Jander
2003-09-23 14:27 ` Takashi Iwai
[not found] ` <1064414023.1630.11.camel@localhost>
2003-09-24 16:34 ` Takashi Iwai [this message]
2005-06-21 9:08 ` Raymond
2005-06-21 10:32 ` Takashi Iwai
2005-06-22 14:21 ` Raymond
2005-06-22 14:37 ` Takashi Iwai
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=s5hisnikuw5.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=manuel.jander@mat.utfsm.cl \
/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.