On 2009/03/06 08:34, Avuton Olrich avu...@gmail.com wrote:
Well, that was not intentional. Not exactly what you asked for, but
hopefully this will float the boat.
That's better, thanks.
configure.ac needs a *lot* of further cleanup:
- for every feature, let the default be auto (auto-detect if
On 09/03/06 10:30 +0100, Max Kellermann wrote:
On 2009/03/06 10:24, Jerome Quelin jque...@gmail.com wrote:
definitely sure: i had to update the test-suite of the perl modules
audio::mpd and poe::component::client::mpd to take this into account.
i'm not saying it's right or wrong, but it
Hi,
This behavior has been introduced in MPD 0.14: When MPD returns an empty
value, it doesn't mean that the tag is empty but that the tag is unknown
(not set in the music file). As a client developer I find this behavior very
useful for example if you want to build a tree like this:
The Doors
Was that change made on purpose, or is it accidental?
I guess this is due to the difference between no genre specified and
genre specified, it's an empty string. Do you have one or more
files which have an empty string defined there?
I don't think distinguishing between there's an empty tag
This patch introduces the mixer for the pulse output.
Technically speaking, the pulse index is needed to get or set
the volume. You must define callback fonctions to get this index since
the pulse output in mpd is done using the simpe api. The pulse simple api
does not provide the index of the
Sorry. I forgot to do the make after minor changes...
I resend the patch wich compiles cleanly.
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open
This patch introduces the mixer for the pulse output.
Technically speaking, the pulse index is needed to get or set
the volume. You must define callback fonctions to get this index since
the pulse output in mpd is done using the simpe api. The pulse simple api
does not provide the index of the
Hi max,
Please pull from my tree, a few fixes you've asked for, a few that
seemed logical to me. configure.ac is still in complete disarray, but
these are some steps forward, I believe. The only one that seems iffy
to me is 'don't include a help string with the --enable-mp3', if I
don't include