All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Hofman <pavel.hofman@insite.cz>
To: Rainer Zimmermann <mail@lightshed.de>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: Maya44 revised patch - vu meters
Date: Thu, 14 Feb 2008 09:25:58 +0100	[thread overview]
Message-ID: <47B3FB16.6090906@insite.cz> (raw)
In-Reply-To: <47B37EE7.5000905@lightshed.de>

Hi,

The vu-meters in alsamixer are not changing, because alsamixer does not 
  refresh regularly their values. They reflect status of ice1724 
vu-meters at the moment of alsamixer start.

I have already raised the issue and I got a fair answer - alsamixer is a 
console mixer and should thus consume as little network bandwidth as 
possible.

Since the meaning of these read-only controls is clear only upon 
detailed study of the driver and Envy24 datasheet plus I encounter a lot 
of questins/complaints about them, I suggest to change their type from 
MIXER to PCM. They would still be readily accessible from amixer or API.

Here is my little vu-meter script I use for testing ice1724 cards:

while true; do amixer cget name="Multi Track Peak" | grep ": values";
sleep 0.5; done

Thanks for considering this minor change which would simplify life of a 
lot of users/admins.

Regards,

Pavel Hofman.


Rainer Zimmermann wrote:
> 
> This is the revised version of the ESI Maya44 patch.
> changes are mainly coding style, some cleanups and using a patch file 
> for ice1724.c .
> 
> The added code now (mostly) passes checkpatch.pl, except for some "#if 
> 0"'s which I'd leave in for the development phase.
> 
> Also, I changed the rate setting logic, which (for now) allows all rates 
> up to 192kHz even for capturing. As capturing actually only supports 96 
> kHz, while capturing & playback rates are linked, this is not really ok. 
> I'd appreciate suggestions about how this could be handled properly, 
> while still supporting playback up to 192 kHz...
> 
> 
> Again, feedback & testing is appreciated.
> 
> For more information, see doc/README.maya44 .
> 
> 
> -Rainer
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

-- 
-----------------

inSITE, s.r.o.

Rubesova 29, 326 00 Plzen
Tel., fax: +420 - 37 - 74 493 58
GSM: +420 - 603 - 163 973
Email: pavel.hofman@insite.cz

www.educity.cz, www.insite.cz
www.meetings.cz, www.hrzive.cz
www.comben.cz, www.hr-online.cz
-------------------------------
Navstivte www.educity.cz, server
s nejvetsi nabidkou profesniho
vzdelavani na ceskem internetu.

  reply	other threads:[~2008-02-14  8:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13 23:36 Maya44 revised patch Rainer Zimmermann
2008-02-14  8:25 ` Pavel Hofman [this message]
2008-02-14 12:03 ` Takashi Iwai
2008-02-14 12:29   ` Pavel Hofman
2008-02-14 12:35     ` Takashi Iwai
2008-02-14 17:05       ` Rainer Zimmermann
2008-02-19 15:25         ` Pavel Hofman
     [not found]       ` <47B47359.6030602@lightshed.de>
2008-02-15 17:02         ` 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=47B3FB16.6090906@insite.cz \
    --to=pavel.hofman@insite.cz \
    --cc=alsa-devel@alsa-project.org \
    --cc=mail@lightshed.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 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.