I can easily squeeze a respectable 3 hours out of my battery with 100% brightness. This can be increased to at least 4 hours when working on a lower, but still workable brightness. I hope developers will continue to work on power management so that I can get to work 5 hours without plugging in the cord as in Windows. I believe work points are automation of powering down/off usb devices, hard disks, sound card and wireless network card, things that can be done manually in the console if you have the expertise.

Looking forward to the next stable gnome release 2.28 with hopefully some new power management features.

Install & configure ABS

First you will need to install the The Arch Build System (ABS) and the basic development tools:

pacman -Sy abs base-devel

Make sure the core, extra and community repository are enabled in /etc/abs.conf:

REPOS=(core extra community !testing)

Now grab all the PKGBUILDS with:

abs

Install & configure PulseAudio

Install pulseaudio with:

pacman -S pulseaudio

There’s a lot to say about configuring pulseaudio, things I’m not going put here. More info on configuring pulseaudio can be found at The Arch Wiki and The Official PulseAudio site. The must do things are installing alsa-plugins to maintain alsa compatibility, configuring .asoundrc, adding yourself to the pulse-rt and pulse-access groups and configuring gstreamer to use pulse. I also don’t recommend using PulseAudio as a system-wide daemon. Just use the per-user daemon.

Rebuild related Gnome packages

There are a few gnome packages that need to be rebuilt against pulseaudio in this order:

1. gnome-settings-daemon
2. gnome-applets
3. gnome-media

Grab the build files from abs one at the time. They are all located under /var/abs/abs/<packagename>. You can build and install the package with:

makepkg -si

gnome-settings-daemon – Remove the patch line (2nd line right after build) in the PKGBUILD.
gnome-applets – Just needs a rebuild, no need to change anything.
gnome-media – Add –enable-pulse to the ./configure line in the PKGBUILD.

That’s pretty much it. Next time you login using gnome, it will use pulseaudio. By default it adds a rather ugly volume slider to the panel (you can prevent it from starting by removing it under system > preferences > startup applications. You can add a better one by right clicking on the panel and adding the volume applet.

As a student Computer Science Engineer I very much appreciate the modular design. PulseAudio contains a lot of (module) plugins.  All audio from/to clients and audio interfaces goes through these modules. PulseAudio clients can send audio to “sinks” and receive audio from “sources”. A client can be GStreamer, xinelib, MPlayer or any other audio application. Only the device drivers/audio interfaces can be either sources or sinks (they are often hardware in- and out-puts). This diagram nicely illustrates the big picture.

With the integration of PulseAudio in GNOME, it will most likely become the dominant audio solution for linux. There are, unfortunately, many opposed to PulseAudio, mainly because of the poor implementation in Ubuntu Hardy Heron and Intrepid Ibex. For those interested in fixing PulseAudio on Ubuntu, I can warmly recommend this topic on the ubuntuforums. While I experienced this issue firsthand,  it remains  an unjustified reason as PulseAudio is not to blame here. Hopefully the general acceptance will improve in the near future.

Funny thing is that of all distros it is Arch Linux that decides not to implement PulseAudio. JDG, the gnome maintainer, patched gnome to its previous state mainly because of another unjustified misconception about PulseAudio. People generally believe that PulseAudio acts like a regular daemon and that it needs to be started in order to get any sound. This is however not true. Unless you want it to act like a central system-wide sound server, the daemon will be spawned when an application tries to play sound. You can follow  the discussion of gnome 2.26 on Arch linux here.

Therefore I had to rebuild a small part of gnome in order to get PulseAudio working. The packages involved were the unpatched gnome-settings-daemon, gnome-applets, gnome-media and gnome-control-center. To get every sound application working, I had to rebuild some of them with pulse support enabled as well. The result is very much worth it.

As you can see in the screenshots, the sound applet has received a new look. They now use a horizontal slider instead of a vertical one. In addition, they included a mute check box. Gnome continues with their tradition of minor but useful changes with this nice applet.

Thanks to PulseAudio, you can now also set the volume per application. You can mute for example the sound of MPlayer while  leaving mpd’s sound untouched or simply set custom volume levels for each application. You can create volume sliders for each channel as well. A welcome addition. Even more impressive is the way it graciously deals with multiple sound cards. It recognizes both my on board as my creative x-fi sound card and I can switch between them. If you want, you can simultaneously play sound through multiple audio cards or map specific channels to specific sound card outputs and create a so called “virtual surround sound card”. For example, use 2 outputs of sound card 1 for the front left/right channel and map the rear left/right channel to sound card 2.

PulseAudio comes with some optional extra applications depicted on the right most screenshot above: a volume meter, a volume manager and the pulseaudio manager. Not depicted is the device chooser where you choose the pulseaudio server, the used sink, etc…

In conclusion I can say PulseAudio is really worth having, giving you lots of possibilitiesn and tThe integration with GNOME is a great success.