The result of a few hours of hacking:
pavucontrol cannot only control the volume of hardware devices of the Polypaudio sound server but also of all playback streams seperately, much like the new Windows Vista volume control application.
Get the Polypaudio Volume Control while it is hot.
On a side note I released updated versions of both the Polypaudio Volume Meter and the Polypaudio Manager which are compatible with Polypaudio 0.8.
The reports of Polypaudio's death are greatly exaggerated.
We are proud to announce the release of Polypaudio 0.8, our networked sound daemon for Linux, other Unix-like operating systems, and Microsoft Windows. Since the last official release, 0.7, more than a year has passed. In the meantime Polypaudio experienced major improvements. Major contributions have been made by both Pierre Ossman and me. Pierre is being payed by Cendio AB to work on Polypaudio. Cendio distributes Polypaudio along with their ThinLinc Terminal Server.
Some of the major changes:
Sounds good, doesn't it? But that's not all!
We're really excited about this new Polypaudio release. However, there are more very exciting, good news in the Polypaudio world. Pierre implemented a Polypaudio plugin for alsa-libs. This means you may now use any ALSA-aware application to access a Polypaudio sound server! The patch has already merged upstream, and will probably appear in the next official release of alsa-plugins.
Due to the massive internal changes we had to make a lot of modifications to the public API. Hence applications which currently make use of the Polypaudio 0.7 API need to be updated. The patches or packages I maintain will be updated in the next weeks one-by-one. (That is: xmms-polyp, the MPlayer patch, the libao patch, the GStreamer patch and the PortAudio patch)
A side note: I wonder what this new release means for Polypaudio in Debian. I've never been informed by the Debian maintainers of Polypaudio that it has been uploaded to Debian, and never of the removal either. In fact I never exchanged a single line with those who were the Debian maintainers of Polypaudio. Is this the intended way how the Debian project wants its developers to communicate with upstream? I doubt that!
Polypaudio does everything what ESOUND does, and much more. It is a fully compatible drop-in replacement. With a small script you can make it command line compatible (including autospawning). ESOUND clients may connect to our daemon just like they did to the original ESOUND daemon, since we implemented a compatibility module for the ESOUND protocol.
Support for other well known networked audio protocols (such as NAS) should be easy to add - if there is a need.
For a full list of the features that Polypaudio has over ESOUND, see Polypaudio's homepage.
Some people might ask whether there still is a need for a sound server in times where ALSA's dmix plugin is available. The answer is: yes!
Firstly, Polypaudio is networked, which dmix is not. However, there are many reasons why Polypaudio is useful on non-networked systems as well. Polypaudio is portable, it is available not just for Linux but for FreeBSD, Solaris and even Microsoft Windows. Polypaudio is extensible, there is broad range of additional modules available which allow the user to use Polypaudio in many exciting ways ALSA doesn't offer. In Polypaudio streams, devices and other server internals can be monitored and introspected freely. The volume of the multiple streams may be manipulated independently of each other, which allows new exciting applications like a work-alike of the new per-application mixer tool featured in upcoming Windows Vista. In multi-user systems, Polypaudio offers a secure and safe way to allow multiple users to access the sound device simultaneously. Polypaudio may be accessed through the ESOUND and the ALSA APIs. In addition, ALSA dmix is still not supported properly by many ALSA clients, and is difficult to setup.
A side node: dmix forks off its own simple sound daemon anyway, hence there is no big difference to using Polypaudio with the ALSA plugin in auto-spawning mode. (Though admittedly, those ALSA clients that don't work properly with dmix, won't do so with our ALSA plugin as well since they actually use the ALSA API incorrectly.)
Everytime people discuss sound servers on Unix/Linux and which way is the right to go for desktops, JACK gets mentioned and suggested by some as a replacement for ESOUND for the desktop. However, this is not practical. JACK is not intended to be a desktop sound server, instead it is designed for professional audio in mind. Its semantics are different from other sound servers: e.g. it uses exclusively floating point samples, doesn't deal directly with interleaved channels and maintains a server global time-line which may be stopped and seeked around. All that translates badly to desktop usages. JACK is really nice software, but just not designed for the normal desktop user, who's not working on professional audio production.
Since we think that JACK is really a nice piece of work, we added two new modules to Polypaudio which can be used to hook it up to a JACK server.
Get Polypaudio 0.8, while it is hot!
BTW: We're looking for a logo for Polypaudio. Feel free to send us your suggestions!
Update: The Debian rant is unjust to Jeff Waugh. In fact, he had informed me that he prepared Debian packages of Polypaudio. I just never realized that he had actually uploaded them to Debian. What still stands, however, is that I've not been informed or asked about the removal.
The result of stitching six photos together with Hugin, autopano-sift, and enblend:
The St.-Pauli-Landungsbrücken with the Queen Mary 2 in the drydock, Hamburg, Germany in November 2005. Photographed from the Stintfang. The full image has a size of 9256x2240.
The result of stitching 16 photos together with Hugin, autopano-sift, and enblend:
The Massif du Soreiller with the Aiguille du Plat de la Selle near Les Deux Alpes, France. Photographed from the Dôme de Puy Salié. The full image has a size of 14443x2156. More pictures from Les Deux Alpes.
In response to mjg59's rant about controlling the LCD brightness on laptops, I invested some time to reverse engineer the Windows driver of my MSI S270 laptop which implements changing LCD brightness. It requires some ugly fiddling with registers of the "embedded controller" on ports 0x62 and 0x66. The result of my work is s270ctrl, a small userspace utility. I'm planning to turn this into a proper kernel module soon.
If you have access to the current issue (03/06) of the german Linux Magazin make sure to read the two extensive articles about Avahi (p.64 and p.90). Daniel S. Haischt wrote the second article, I wrote the other. Both are a worthy read!
Due to the great work of Sebastien Estienne there are now Debian packages of mod_dnssd and mod_mime_xattr available from my little Debian package repository. They've been uploaded to Ubuntu as well, but we are still looking for some Debian developer who would be willing to upload them to Debian proper. Feel free to contact me if you are interested!
It has been pretty cold in Hamburg the last days. There's now a thick but holey ice cover on the Elbe river:
I updated my little Apache module mod_mime_xattr to be compatible with Apache 2.0.
What is it useful for? Linux (2.4 with patch, 2.6 out-of-the-box) has been supporting extended attributes for files (EAs) for ages, but very few applications use them. To change that I wrote a small module for Apache which interpretes the EA user.mime_type and uses its value as MIME type for all files served by Apache. The EA has been standardized by the XDG MIME system, but apparently neither Gnome nor KDE support it right now.
Usage of mod_mime_xattr is simple. To enable interpretation of the EA on the entire tree use something like this in your Apache configuration file:
<Directory /> XAttrMimeType On </Directory>
That's all that is required to make use of user.mime_type on all files where it is set. To set the EA use a command like this one:
setfattr -n "user.mime_type" -v "text/html" foo.txt
And foo.txt will become a file with the MIME type of text/html, although its suffix is .txt!
The first release of mod_dnssd is now available. It adds DNS-SD based Zeroconf support to Apache 2.0 using Avahi.
This work has been inspired by Sander Temme's and Sebastien Estienne's mod_zeroconf module, but supersedes it in every way. MacOSX ships with mod_rendezvous/mod_bonjour, but mod_dnssd is much more powerful than this piece of software as well. In short: mod_dnssd is definitely the greatest way to add Zeroconf support to Apache available today.
A few examples just to show how great mod_dnssd is:
DNSSDEnable On
This is everything you need to enable DNS-SD support in Apache after loading the module. It will publish all virtual hosts and all existing mod_userdir directories (i.e. ~/public_html) as services of type _http._tcp.
In case you want to publish some subdirectory of the web server as service, just place DNSSDServiceName inside a <Location> section for that path:
<Location /foobar> DNSSDServiceName "A special service called foobar" </Location>
You can even use it to publish WebDAV shares using Apache's mod_dav module:
<Location /webdav> Dav On DNSSDServiceName "A WebDAV folder" DNSSDServiceTypes _webdav._tcp </Location>
This especially cool since we now have a free software server counterpart for Gnome's and KDE's WebDAV client functionality.
Or to publish your blog as RSS service:
<Location /blog.cgi?rss> DNSSDServiceName "The blog" DNSSDServiceTypes _rss._tcp </Location>