[PlanetCCRMA] announcing envy24control, mudita (*) edition.

Takashi Iwai tiwai at suse.de
Mon Jul 26 01:47:51 PDT 2010

At Sun, 25 Jul 2010 12:10:44 -0700,
Niels Mayer wrote:
> Summary of updates from envy24control 0.6.0 (GIT HEAD) to "1.0.0":
> (0) After a decade, incremented version to 1.0.0 (**)
> (1) Implemented missing "Peak Hold" functionality in meters and
> reimplemented meters for increased efficiency and lower X resource
> usage. (see http://www.linuxaudio.org/mailarchive/lad/2010/7/12/171535
> & https://bugzilla.redhat.com/show_bug.cgi?id=602903 )
> (2) All volumes are represented as decibels, including the 0 to -48dB
> range of the hardware peak-meters, the 0 -to- -144dB attenuation for
> all inputs to the digital mixer, the 0 -to- -63dB attenuation of the
> analog DAC, and the +18 -to- -63dB attenuation/amplification of the
> analog ADC.
> (3) All gtk "scale" widgets have dB legends; the "PageUp" "PageDown"
> keys allow rapid movement between the marked levels.
> (4) Got rid of myriad compile warnings and other minor fixes across codebase.
> Some screenshots:
> http://nielsmayer.com/envy24control/Screenshot-Envy24Control-AnalogVolume.png
> http://nielsmayer.com/envy24control/Screenshot-Envy24Control-MonitorInputs.png
> http://nielsmayer.com/envy24control/Screenshot-Envy24Control-MonitorPCM.png
> ------------
> To the ALSA project: please consider this patch to alsa-tools'
> envy24control (**):
> http://nielsmayer.com/envy24control/envy24control-0.6-to-1.0.patch
> (patch to 'envy24control' from GIT trunk/head of alsa-tools)
> http://nielsmayer.com/envy24control/envy24control-1.0.README
> (summary of changes from 0.6.0 to 1.0.0)

Great.  I'd love to merge it to the upstream tree after code review.

Could you simply post your patch(es) to alsa-devel ML (and Cc to
maintainers)?  Then we can check your changes.

At best, please give incremental patches containing the proper
changelog and your sign-off in the patch comments to be applicable via

Also, avoid to change version numbers.  If you take over the whole
project, then yes, it's fine to change the major version number as you 
like.  But, as long as the upstream is alive, this may bring much more
confusion than needed.



More information about the PlanetCCRMA mailing list