ANNOUNCE: xfce4-volumed 0.1.4 released

[Steve Dodier-2]

xfce4-volumed 0.1.4 is now available for download from
 
  http://archive.xfce.org/src/apps/xfce4-volumed/0.1/xfce4-volumed-0.1.4.tar.bz2
  http://archive.xfce.org/src/apps/xfce4-volumed/0.1/xfce4-volumed-0.1.4.tar.bz2.md5
  http://archive.xfce.org/src/apps/xfce4-volumed/0.1/xfce4-volumed-0.1.4.tar.bz2.sha1

  SHA1 checksum: c4fff691c7a131064bf7a2353ac4b8638e2a1559
   MD5 checksum: 34f009d3272050ef72c32f491152f6bd


What is xfce4-volumed?
======================

This daemon is responsible of making the volume up/down and mute keys of
the keyboard work automatically, and uses the XFCE 4 mixer's card
setting for chosing which card to act on. It also provides volume change
/ mute toggle notifications if the notification server used supports
x-canonical-icon-only and x-canonical-synchronous notifications.

Website:
  https://launchpad.net/xfce4-volumed


Release notes for 0.1.4
=======================

* Volume initialisation now includes mute check
 * Fixed a bug in volume calculation due to float truncating
 * Replaced g_utf8_collate by g_strcmp0. Less accurate but at least
doesn't corrupt strings
 * Removed obsolete code
 * Fixed an error preventing from building without libnotify
 * Code refactoring (xvd_mixer and xvd_xfconf)
 * Making sure that nothing wrong is done if the card exists but is
trackless
_______________________________________________
Xfce mailing list
Xfce@...
http://foo-projects.org/mailman/listinfo/xfce
http://www.xfce.org

[David Mohr-8]

On Fri, Sep 4, 2009 at 11:29 AM, <sidnioulz@...> wrote:
> xfce4-volumed 0.1.4 is now available for download from

Cool! I didn't know this existed! Too bad my current keyboard is
lacking these keys, but for a ton of people this is a great app :-)

~David
_______________________________________________
Xfce mailing list
Xfce@...
http://foo-projects.org/mailman/listinfo/xfce
http://www.xfce.org

[Steve Dodier-2]

I still didn't code what's needed to allow custom keyboard shortcuts, but if you mail me the keys you want i can cook you a patch for it ;)

_______________________________________________
Xfce mailing list
Xfce@...
http://foo-projects.org/mailman/listinfo/xfce
http://www.xfce.org

[Yves-Alexis Perez-2]

On ven, 2009-09-04 at 23:11 +0200, Steve Dodier wrote:
> I still didn't code what's needed to allow custom keyboard shortcuts,
> but if you mail me the keys you want i can cook you a patch for it ;)

It seems the volume keys on my ThinkPad aren't detected:

corsac@hidalgo: src/xfce4-volumed
XCB: RaiseVolume ok, keycode=123 mod=0x0000
XCB: RaiseVolume ok, keycode=123 mod=0x0000
XCB: RaiseVolume ok, keycode=123 mod=0x0000
XCB: LowerVolume ok, keycode=122 mod=0x0000
XCB: LowerVolume ok, keycode=122 mod=0x0000
XCB: LowerVolume ok, keycode=122 mod=0x0000
XCB: Mute ok, keycode=121 mod=0x0000
XCB: Mute ok, keycode=121 mod=0x0000
XCB: Mute ok, keycode=121 mod=0x0000
** (<unknown>:20958): DEBUG: The card HDAIntelAlsamixer was found and
set as the current card.

** (<unknown>:20958): DEBUG: There is no track label stored in xfconf

** (<unknown>:20958): DEBUG: The wanted track could not be found, using
the first one instead.

** (<unknown>:20958): DEBUG: Xfconf volume step: 5


And then nothing.

But:

corsac@hidalgo: sudo input-events 1
/dev/input/event1
   bustype : BUS_I8042
   vendor  : 0x1
   product : 0x1
   version : 43860
   name    : "AT Translated Set 2 keyboard"
   phys    : "isa0060/serio0/input0"
   bits ev : EV_SYN EV_KEY EV_MSC EV_LED EV_REP

waiting for events
00:22:39.554341: EV_MSC code=4 value=28
00:22:39.554361: EV_KEY KEY_ENTER released
00:22:39.554367: EV_SYN code=0 value=0
00:22:41.759661: EV_MSC code=4 value=176
00:22:41.759683: EV_KEY KEY_VOLUMEUP pressed
00:22:41.759690: EV_SYN code=0 value=0
00:22:41.903354: EV_MSC code=4 value=176
00:22:41.903376: EV_KEY KEY_VOLUMEUP released
00:22:41.903382: EV_SYN code=0 value=0
00:22:42.149259: EV_MSC code=4 value=174
00:22:42.149279: EV_KEY KEY_VOLUMEDOWN pressed
00:22:42.149286: EV_SYN code=0 value=0
00:22:42.268782: EV_MSC code=4 value=174
00:22:42.268805: EV_KEY KEY_VOLUMEDOWN released

Hope that helps,

--
Yves-Alexis


_______________________________________________
Xfce mailing list
Xfce@...
http://foo-projects.org/mailman/listinfo/xfce
http://www.xfce.org

[Brian J. Tarricone-3]

Any particular reason you're depending on xcb-keysyms 0.3.5?  I only
have 0.3.3 on my system (which is the latest marked stable).

        -brian

On 09/04/2009 10:29 AM, sidnioulz@... wrote:

> xfce4-volumed 0.1.4 is now available for download from
>  
>   http://archive.xfce.org/src/apps/xfce4-volumed/0.1/xfce4-volumed-0.1.4.tar.bz2
>   http://archive.xfce.org/src/apps/xfce4-volumed/0.1/xfce4-volumed-0.1.4.tar.bz2.md5
>   http://archive.xfce.org/src/apps/xfce4-volumed/0.1/xfce4-volumed-0.1.4.tar.bz2.sha1
>
>   SHA1 checksum: c4fff691c7a131064bf7a2353ac4b8638e2a1559
>    MD5 checksum: 34f009d3272050ef72c32f491152f6bd
>
>
> What is xfce4-volumed?
> ======================
>
> This daemon is responsible of making the volume up/down and mute keys of
> the keyboard work automatically, and uses the XFCE 4 mixer's card
> setting for chosing which card to act on. It also provides volume change
> / mute toggle notifications if the notification server used supports
> x-canonical-icon-only and x-canonical-synchronous notifications.
>
> Website:
>   https://launchpad.net/xfce4-volumed
>
>
> Release notes for 0.1.4
> =======================
>
> * Volume initialisation now includes mute check
>  * Fixed a bug in volume calculation due to float truncating
>  * Replaced g_utf8_collate by g_strcmp0. Less accurate but at least
> doesn't corrupt strings
>  * Removed obsolete code
>  * Fixed an error preventing from building without libnotify
>  * Code refactoring (xvd_mixer and xvd_xfconf)
>  * Making sure that nothing wrong is done if the card exists but is
> trackless
> _______________________________________________
> Xfce mailing list
> Xfce@...
> http://foo-projects.org/mailman/listinfo/xfce
> http://www.xfce.org

_______________________________________________
Xfce mailing list
Xfce@...
http://foo-projects.org/mailman/listinfo/xfce
http://www.xfce.org

[Brian J. Tarricone-3]

On 09/04/2009 03:23 PM, Yves-Alexis Perez wrote:

> corsac@hidalgo: sudo input-events 1
> /dev/input/event1
>    bustype : BUS_I8042
>    vendor  : 0x1
>    product : 0x1
>    version : 43860
>    name    : "AT Translated Set 2 keyboard"
>    phys    : "isa0060/serio0/input0"
>    bits ev : EV_SYN EV_KEY EV_MSC EV_LED EV_REP
>
> waiting for events
> 00:22:39.554341: EV_MSC code=4 value=28
> 00:22:39.554361: EV_KEY KEY_ENTER released
> 00:22:39.554367: EV_SYN code=0 value=0
> 00:22:41.759661: EV_MSC code=4 value=176
> 00:22:41.759683: EV_KEY KEY_VOLUMEUP pressed
> 00:22:41.759690: EV_SYN code=0 value=0
> 00:22:41.903354: EV_MSC code=4 value=176
> 00:22:41.903376: EV_KEY KEY_VOLUMEUP released
> 00:22:41.903382: EV_SYN code=0 value=0
> 00:22:42.149259: EV_MSC code=4 value=174
> 00:22:42.149279: EV_KEY KEY_VOLUMEDOWN pressed
> 00:22:42.149286: EV_SYN code=0 value=0
> 00:22:42.268782: EV_MSC code=4 value=174
> 00:22:42.268805: EV_KEY KEY_VOLUMEDOWN released

Probably more useful would be xev output when pressing the keys.  X
keysyms and console/kernel keycodes are unrelated.

        -brian
_______________________________________________
Xfce mailing list
Xfce@...
http://foo-projects.org/mailman/listinfo/xfce
http://www.xfce.org

[Steve Dodier-2]

2009/9/5 Yves-Alexis Perez <corsac@...>

On ven, 2009-09-04 at 23:11 +0200, Steve Dodier wrote:
> I still didn't code what's needed to allow custom keyboard shortcuts,
> but if you mail me the keys you want i can cook you a patch for it ;)

It seems the volume keys on my ThinkPad aren't detected:

corsac@hidalgo: src/xfce4-volumed
XCB: RaiseVolume ok, keycode=123 mod=0x0000
XCB: RaiseVolume ok, keycode=123 mod=0x0000
XCB: RaiseVolume ok, keycode=123 mod=0x0000
XCB: LowerVolume ok, keycode=122 mod=0x0000
XCB: LowerVolume ok, keycode=122 mod=0x0000
XCB: LowerVolume ok, keycode=122 mod=0x0000
XCB: Mute ok, keycode=121 mod=0x0000
XCB: Mute ok, keycode=121 mod=0x0000
XCB: Mute ok, keycode=121 mod=0x0000
** (<unknown>:20958): DEBUG: The card HDAIntelAlsamixer was found and
set as the current card.

** (<unknown>:20958): DEBUG: There is no track label stored in xfconf

** (<unknown>:20958): DEBUG: The wanted track could not be found, using
the first one instead.

** (<unknown>:20958): DEBUG: Xfconf volume step: 5


And then nothing.

But:

corsac@hidalgo: sudo input-events 1
/dev/input/event1
  bustype : BUS_I8042
  vendor  : 0x1
  product : 0x1
  version : 43860
  name    : "AT Translated Set 2 keyboard"
  phys    : "isa0060/serio0/input0"
  bits ev : EV_SYN EV_KEY EV_MSC EV_LED EV_REP

waiting for events
00:22:39.554341: EV_MSC code=4 value=28
00:22:39.554361: EV_KEY KEY_ENTER released
00:22:39.554367: EV_SYN code=0 value=0
00:22:41.759661: EV_MSC code=4 value=176
00:22:41.759683: EV_KEY KEY_VOLUMEUP pressed
00:22:41.759690: EV_SYN code=0 value=0
00:22:41.903354: EV_MSC code=4 value=176
00:22:41.903376: EV_KEY KEY_VOLUMEUP released
00:22:41.903382: EV_SYN code=0 value=0
00:22:42.149259: EV_MSC code=4 value=174
00:22:42.149279: EV_KEY KEY_VOLUMEDOWN pressed
00:22:42.149286: EV_SYN code=0 value=0
00:22:42.268782: EV_MSC code=4 value=174
00:22:42.268805: EV_KEY KEY_VOLUMEDOWN released

Hope that helps,

--
Yves-Alexis

On the application's point of view, everything is fine. It did grab XF86AudioRaiseVolume, XF86AudioLowerVolume and XF86AudioMute. But it looks like the keys on your keyboard aren't labelled that way. The problem is that your keyboard is probably not correctly recognised by X (Xcb directly uses Xlib). 

2009/9/5 Brian J. Tarricone <brian@...>

Any particular reason you're depending on xcb-keysyms 0.3.5?  I only
have 0.3.3 on my system (which is the latest marked stable).

       -brian

When testing xvd, Lionel noticed that it wasn't working correctly on Debian unstable, and he found out that it was because of an API change in xcb (that of course what announced only in a commit mailing list). That change happened on 2009-04-11, so if XCB keysyms 3.3 has been released after (i didn't manage to find a list of tarballs for keysyms on the web), then it's likely to work, so feel free to change the version number in configure.ac and to let me know ;)

Otherwise, I have a branch that works for older versions of xcb keysyms that didn't have this change. I didn't upload it in git because I have no idea how to create remote branches :) But it's available on bzr : 'bzr co lp:~sidi/xfce4-volumed/jaunty'

SD.

_______________________________________________
Xfce mailing list
Xfce@...
http://foo-projects.org/mailman/listinfo/xfce
http://www.xfce.org

[Yves-Alexis Perez-2]

On ven, 2009-09-04 at 16:59 -0700, Brian J. Tarricone wrote:
> Probably more useful would be xev output when pressing the keys.  X
> keysyms and console/kernel keycodes are unrelated.

They doesn't seem to output anything about keys in xev:

FocusOut event, serial 33, synthetic NO, window 0x4800001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 33, synthetic NO, window 0x4800001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 33, synthetic NO, window 0x0,
    keys:  28  0   0   0   0   0   0   0   0   0   0   0   0   0   0   0  
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0  

FocusOut event, serial 33, synthetic NO, window 0x4800001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 33, synthetic NO, window 0x4800001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 33, synthetic NO, window 0x0,
    keys:  2   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0  
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0  

FocusOut event, serial 33, synthetic NO, window 0x4800001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 33, synthetic NO, window 0x4800001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 33, synthetic NO, window 0x0,
    keys:  2   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0  
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0  

Though I can bind them in xfwm4, and they are detected as:

XF86AudioLowerVolume
XF86AudioRaiseVolume
XF86AudioMute

Cheers,

--
Yves-Alexis


_______________________________________________
Xfce mailing list
Xfce@...
http://foo-projects.org/mailman/listinfo/xfce
http://www.xfce.org

[Yves-Alexis Perez-2]

On sam, 2009-09-05 at 12:29 +0200, Steve Dodier wrote:
> On the application's point of view, everything is fine. It did grab
> XF86AudioRaiseVolume, XF86AudioLowerVolume and XF86AudioMute. But it looks
> like the keys on your keyboard aren't labelled that way. The problem is that
> your keyboard is probably not correctly recognised by X (Xcb directly uses
> Xlib).

xfwm4 (in the keyboard settings) correctly detects them as these keys,
so I wonder why xcb-keysims doesn't. This is a bit weird.

--
Yves-Alexis


_______________________________________________
Xfce mailing list
Xfce@...
http://foo-projects.org/mailman/listinfo/xfce
http://www.xfce.org

[Brian J. Tarricone-3]

On 09/04/2009 10:29 AM, sidnioulz@... wrote:
> xfce4-volumed 0.1.4 is now available for download

Hey Steve,

I had a chance to revisit xfce4-volumed (which I'd like to use full
time), but I have a question about the libnotify support: why are you
only supporting notify-osd?  It's certainly nice to have a pretty
percentage bar with icon over having a text label for the percentage,
but I'd rather have the latter than having absolutely no idea at all how
loud my volume is when I press the keys (without waiting for a
possibly-embarrassing loud noise at work to tell me exactly how loud it is).

Also, please *please* don't do implementation specific detection.  As
maintainer of a (different) notification daemon, it's very frustrating
to see people write apps that use a cross-desktop technology in such a
way that discriminates against different implementations.  If you were
doing sniffing to work around a bug in a particular implementation,
fine, that sucks, but you gotta do what you gotta do.  If you're
checking capabilities in order to provide *more* features for
implementations that support the optional stuff, that's great.  But
making use of non-standard extensions to a public specification and
leaving out support for degrading gracefully just strikes me as bad form.

Anyhow, if I get around to it I'll likely write a patch to fix these
deficiencies...  in the meantime I'm sadly back to keybinds that run my
mixer-set script and (annoyingly) pollute the screen with multiple
notifications if I tap the key several times in quick succession.

        -brian
_______________________________________________
Xfce mailing list
Xfce@...
http://foo-projects.org/mailman/listinfo/xfce
http://www.xfce.org

[Steve Dodier-2]

Hi Brian,

The main reason why I only support notify-osd (more accurately, notification daemons that implement x-canonical-synchronous) is that with other notification daemons, we were ending up with a lot of bubbles being created in the case of pressing the volume button till its 0 or 100%, because they stack notifications. If you find interest in having an async notification updating itself, I surely can write the code for that and make it available when x-canonical-synchronous isn't supported by the daemon.

2009/10/26 Brian J. Tarricone <brian@...>

On 09/04/2009 10:29 AM, sidnioulz@... wrote:

> xfce4-volumed 0.1.4 is now available for download

Hey Steve,

I had a chance to revisit xfce4-volumed (which I'd like to use full
time), but I have a question about the libnotify support: why are you
only supporting notify-osd?  It's certainly nice to have a pretty
percentage bar with icon over having a text label for the percentage,
but I'd rather have the latter than having absolutely no idea at all how
loud my volume is when I press the keys (without waiting for a
possibly-embarrassing loud noise at work to tell me exactly how loud it is).

Also, please *please* don't do implementation specific detection.  As
maintainer of a (different) notification daemon, it's very frustrating
to see people write apps that use a cross-desktop technology in such a
way that discriminates against different implementations.  If you were
doing sniffing to work around a bug in a particular implementation,
fine, that sucks, but you gotta do what you gotta do.  If you're
checking capabilities in order to provide *more* features for
implementations that support the optional stuff, that's great.  But
making use of non-standard extensions to a public specification and
leaving out support for degrading gracefully just strikes me as bad form.

Anyhow, if I get around to it I'll likely write a patch to fix these
deficiencies...  in the meantime I'm sadly back to keybinds that run my
mixer-set script and (annoyingly) pollute the screen with multiple
notifications if I tap the key several times in quick succession.

       -brian

_______________________________________________
Xfce mailing list
Xfce@...
http://foo-projects.org/mailman/listinfo/xfce
http://www.xfce.org

--
Steve Dodier
Student at École Nationale Supérieure d'Ingénieurs de Bourges
Free Software Developer
OpenPGP : 1B6B1670

_______________________________________________
Xfce mailing list
Xfce@...
http://foo-projects.org/mailman/listinfo/xfce
http://www.xfce.org

[Steve Dodier-2]

I implemented support for all libnotify daemons via notify_notification_update in xfce4-volumed 0.1.5. I reckon I should have done it from the beginning and apologize for not having thought about people who were not using the apps I used.

My decision was first based upon the fact that with non-sync daemons, the notification wouldn't always be shown synchronously if there are a lot of notifications stacked, and upon the fact that anyway there was the mixer's panel plugin. I must say that if this is true in Xubuntu, it's not for every XFCE users. Thus, I was wrong.

Thanks Brian for having brought this problem to my attention. I hope you'll enjoy xfce4-volumed with real libnotify support :)

_______________________________________________
Xfce mailing list
Xfce@...
http://foo-projects.org/mailman/listinfo/xfce
http://www.xfce.org

[Brian J. Tarricone-3]

On Tue, Oct 27, 2009 at 17:11, Steve Dodier <sidnioulz@...> wrote:
> I implemented support for all libnotify daemons via
> notify_notification_update in xfce4-volumed 0.1.5. I reckon I should have
> done it from the beginning and apologize for not having thought about people
> who were not using the apps I used.

Thanks so much!

> My decision was first based upon the fact that with non-sync daemons, the
> notification wouldn't always be shown synchronously if there are a lot of
> notifications stacked, and upon the fact that anyway there was the mixer's
> panel plugin. I must say that if this is true in Xubuntu, it's not for every
> XFCE users. Thus, I was wrong.

Actually the synchronize hint supported by ubuntu serves something of
a different purpose than its name would seem to indicate.  All it
really does is determine whether notify-osd treats it as a
confirmation or notification.

AFAICT (not tested, just going by Canonical's spec at
https://wiki.ubuntu.com/NotifyOSD), you should actually not have to do
any sniffing at all... you can probably just set the hints all the
time, and notification daemon's that don't support them will just
ignore them.  I guess it doesn't really matter much for your code tho.

> Thanks Brian for having brought this problem to my attention. I hope you'll
> enjoy xfce4-volumed with real libnotify support :)

Yay, I'll give it a try tonight or tomorrow ^_^

     -brian
_______________________________________________
Xfce mailing list
Xfce@...
http://foo-projects.org/mailman/listinfo/xfce
http://www.xfce.org