From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: Volume Peak display Date: Wed, 24 Sep 2003 18:34:34 +0200 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: <1064034672.10497.7.camel@localhost> <1064414023.1630.11.camel@localhost> Mime-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <1064414023.1630.11.camel@localhost> Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: manuel.jander@mat.utfsm.cl Cc: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org 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