Dear Greg,
thank you very much for your email and bug issue. I have read
carefully what you have written and I wanted to ask you for your
proposal in solving the manpage disinformation. What will be the
optimal information to be written in the manpage? Have you found any
other issues? How often do you use mpg321? Are you combining it with
any other applications? Why do you prefer it from any other relevant
applications, like mplayer or madplay? Any future wishlist? Are you
using it in any embedded system? For now it is the only application
that compiles cleanly and uses the less CPU from any other relevant
program, tested in avr32, blackfin and other embedded platforms. I
would appreciate it if you answer my questions. I agree with you about
the ALSA team but don't forget that some changes have to be done cause
they just follow up the Linux kernel changes.
Best regards,
Chris.
On 24 Απρ 2011, at 18:47, Greg Alexander <gredeb...@galexander.org>
wrote:
Package: mpg321
Version: 0.2.13-2
Severity: normal
This is a repeat of bug #286176, which was either never fixed or
broken
immediately thereafter.
The mpg321 man page says, of -a:
For -o alsa, specify card:device; defaults to 0:0.
Without -o, the default is ao_default_driver_id(). With -o alsa, it
is
ao_driver_id("alsa") with no arguments. In neither case is the
default
ever 0:0. So that is disinformation. The true default is an out-of-
band
value which cannot be specified with the -a option.
But more to the point, the format -a 0:0 is bogus in every way. The
actual format is -a alsa:hw:0 for the default, or -a alsa:hw:1 for the
second card. Prefixing with "alsa:" was a wild-assed guess on my
part,
and may not be the preferred option (though it is the only working one
that I found).
It is lame that this is still misdocumented. When I first started
ALSA
programming 10 years ago, I found that the API had changed radically
from
the date of documentiation to the current date. Funny that this would
still be true today for high-level features of maintained packages
that
derive from ALSA. Could someone please tell the ALSA&libao guys that
their inability to stick with anything that works is screwing up the
end-user experience as well as the programmer and package maintainer
experience? They deserve a little unpleasantness and disgratitude for
their wankery. The act of repeatedly breaking an API or command-line
interface is not productive upkeep of an open source project. It is
not
a contribution but rather a subtle form of sabotage in the service of
ego.
Thanks,
- Greg
-- System Information:
Debian Release: squeeze/sid
APT prefers oldstable
APT policy: (500, 'oldstable'), (500, 'unstable')
Architecture: i386 (x86_64)
Kernel: Linux 2.6.32.16 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages mpg321 depends on:
ii libao4 1.1.0-1 Cross Platform Audio
Output Librar
ii libc6 2.11.2-6 Embedded GNU C Library:
Shared lib
ii libid3tag0 0.15.1b-10 ID3 tag reading library
from the M
ii libmad0 0.15.1b-4 MPEG audio decoder
library
Versions of packages mpg321 recommends:
ii libaudio-scrobbler-perl 0.01-2.1 perl interface to
audioscrobbler.c
mpg321 suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
