README

Introduction

powermated is a program which helps enable full use of the Griffin PowerMate from within the GNU/Linux operating system.

Powermated was created because I love the PowerMate, and it was a shame to have incomplete support in Linux.

With powermated, comes support that stomps all over the support for alternative operating systems. Powermated can display the CPU usage, or XMMS/BMP sound output on your PowerMate, amongst being able to control nearly any program.

Dependencies

powermated depends on ALSA, and X windows in order to be compiled. Optionally it can depend on XMMS/BMP, and libXOSD.

Installation

powermated used to be intended to be run with the EvRouter program, however it has since then outgrown its roots, and is now completely self-sufficient. Of course, it can still be used with EvRouter simply by turning off its event routing subsystem (--noinputrouting). Powermated is now capable of translating any input event to any other kind of event. It can even differentiate between the currently selected window and so forth. This allows different actions based on what application is active, and also based on modifier key presses (such as control, shift, etc).

powermated is a daemon that runs in the background. It watches the system ALSA mixer and updates the PowerMate's LED. It also sets the system mixer when requested (via the configurable event chain (/etc/powermated.conf, ~/.powermatedrc). Additionally, it has a selectable monitor path that allows for viewing of different system events on the PowerMate's LED, such as CPU usage, and XMMS/BMP sound output.

For more detailed instructions on getting the PowerMate to work in Linux, see my HOWTO on the gentoo-wiki:

http://gentoo-wiki.com/HOWTO_Griffin_PowerMate_with_UDEV_and_Kernel_2.6.x

Command Line Switches:

-c --card <card name> :: Defaults to "hw:0"

This is the name of the ALSA device to control

-m --mixer <mixer name> :: Defaults to "Master"

This is the name of the ALSA mixer control to monitor

-d --device <dev name> :: Defaults to "/dev/input/event*"

This is where your PowerMate is located. It autodetects this if you do not specify.

-p --cpudelay <delay> :: Defaults to "100000"

This affects the CPU monitor. Measured in microseconds. It is the time between polling the cpu for usage information.

    -y --cputwitchy         :: Enable the twitchy CPU monitor
        - Very accurate, but not as nice looking CPU monitor

-f --defmon <monitor> :: Defaults to "volume"

Set which monitor should be active on startup

    -t --novolumetrump      :: Disable Volume Trumps All mode
        - Disable the ability to watch the volume while watching another monitor
        
    -i --noinputrouting     :: Disable Input Event Routing Mode
        - Disable the event routing subsystem

-x --xdisplay <display> :: Watch Specified X Display

This is the desired X display to watch. Autodetected if not specified.

    -s --silent             :: Enable Silent Mode
        - This makes powermated completely silent (no output)
        - For correct functioning, this should be the first argument

    -z --trainingmode       :: Enable Training Mode
        - Enable training mode to gather information about the currently active window.  After starting powermated, focus the mouse on an application, and turn the knob, then look at the console messages provided by powermated.
        
    -o --noxosd             :: Disable XOSD (even if compiled in)
        - Turn off that lovely green glow
        
    -q --font               :: Defaults to "arial"
        - Set to "terminal" for some old school fun
        
    -r --fontsize           :: Defaults to "30"
        - If you're like me, you need to crank this.
    
    -u --fontcolor          :: Defaults to "Cyan"
        - Cyan is nice, so is LawnGreen, SteelBlue, and some others :o)
        - These are the standard X colors

    -g --debug              :: Enable Debug Mode
        - If reporting bugs, please turn on debug mode and send along a detailed report of what happened.

Known Bugs:

if the mouse cursor goes over flash in a web page, it causes powermated not to know it's over firefox any more (and thus scrolling stops working).
if the xserver restarts, powermated will crash when it tries to get the next foreground window properties. If anyone can think of a fix that will allow powermated to detect if the xserver has reset, and then re-attach itself to the new xserver... let me know!

To do:

more monitors!
absolute dial turning, where a delay can be specified that wont get triggers simply by making small movements.
if people want it, regular expressions for the Window Name matching.
other ways to match a window besides it title? (ie for window managerless kiosks)
man pages
more documentation
gui for the config file (if someone out there wants to do this, maybe then it'll get done :o))