All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sebastian H." <vand2@gmx.de>
To: Raymond Yau <superquad.vortex2@gmail.com>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: Alsamixer-Qt 0.4.1 available
Date: Thu, 12 Aug 2010 12:09:01 +0200	[thread overview]
Message-ID: <4C63C83D.2000304@gmx.de> (raw)
In-Reply-To: <AANLkTin_exCQw8RG2Mhc-NBff+kTmRCeejtLZyTcVDZ7@mail.gmail.com>

Am 12.08.2010 02:10, schrieb Raymond Yau:
> 2010/8/11 Sebastian H. <vand2@gmx.de>
> 
>> Hello again
>>
>> This is a bugfix release. Not all issues have been addressed, but
>> hopefully the most annoying ones.
>>
>> 1.)
>> https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3678
>>
>> The "EQ Peaks" mixer element gets skipped since there's not way to
>> display it correctly at the moment.
>> Also the mixer now looks for all element channels from 0 up to
>> SND_MIXER_SCHN_LAST (= 31). Formerly it was only for the first 9 channels.
>>
>>
> 
>   control.12 {
>          comment.access read
>          comment.type INTEGER
>          comment.count 20
> 
> The main problem  is this EQ peak control is read only and your
> alsamixer-qt4-0.4.0 generate a lot of error messages when the user try to
> move the slider , so the only way is to skip the volume control or implement
> the equalizer peak using 10 qt4 vumeter widgets
> 
> [EE] EQ Peaks: snd_mixer_selem_set_playback_
> volume_all: Operation not permitted

In 0.4.1 the "EQ peak" should be hidden. But that's a temporary
solution. I just don't have a card right now with "EQ peak" and
implementing a feature/widget that I can't test is not too much fun.

> 
> For CMI8788 , there is only one Master volume control controls with 8
> channels volume control but it seem only has one mute switch

Ok, then I don't see a any problem there.

Sebastian

      reply	other threads:[~2010-08-12 10:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-11 15:50 Alsamixer-Qt 0.4.1 available Sebastian H.
2010-08-12  0:10 ` Raymond Yau
2010-08-12 10:09   ` Sebastian H. [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=4C63C83D.2000304@gmx.de \
    --to=vand2@gmx.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=superquad.vortex2@gmail.com \
    /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.