Le 11-01-2014 11:14, Joachim Reichel a écrit :
Hi Mathieu,
why do think that this behavior is a bug?
normalize-audio operates on .wav files (as stated in the
documentation). If
support for libmad is enabled, then is also supports .mp3 files
directly. For
all other file types it is required to decode/encode before/after
using
normalize-audio. This is what normalize-mp3 and normalize-ogg are
doing.
Joachim
Hi Joachim,
I guess I was fooled by the doc and name.
I tend to use --help more than the manpage (my bad) and --help never
ever mention wav but talks only about audio files. Probably because the
author first thought of a multiple format tool (hence the weirdness of
having the wav tool supporting mp3 aside from the -mp3 wrapper).
After this, when you look at the manpage a bit too fast you read things
like "normalize-audio - adjusts volume levels of audio files" (mp3, ogg,
whatever, are all as much audio files than wav, are they not?) and a bit
confusing statements like "In the first phase, it analyzes the
specified files as wav audio files" (why "an analyze as wav audio files"
instead of "it analyzes wav audio files..."?).
I guess it would make sense to name normalize-audio to normalize-wav -
but it is probably a bit late for that.
I looked for this issue on the web beforehand and found lot of pages of
people asking the same question, it is probably a matter of RTFMing more
carefully, but I wonder if maybe a simple update of the --help or a
highlighted warning in the manpage (if the first is annoying to do)
would not be worth.
For the story, I had a script using normalize-ogg. A while later, while
rereading it, I changed it to normalize-audio thinking *hey, why not
using the "audio" general bin instead of the ogg specific".
Regards,
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
