[MPlayer-DOCS] [PATCH] update -channels to match observed behavior
Guillaume POIRIER
poirierg at gmail.com
Fri Sep 2 10:17:24 CEST 2005
Hi,
On 9/2/05, Corey Hickey <bugfood-ml at fatooh.org> wrote:
> Corey Hickey wrote:
> > +To directly control the number of output channels independantly of how many
> ^
> Oops, I can't spel rite. New patch.
>
> -Corey
>
>
> Index: DOCS/man/en/mplayer.1
> ===================================================================
> RCS file: /cvsroot/mplayer/main/DOCS/man/en/mplayer.1,v
> retrieving revision 1.1077
> diff -u -r1.1077 mplayer.1
> --- DOCS/man/en/mplayer.1 31 Aug 2005 16:23:07 -0000 1.1077
> +++ DOCS/man/en/mplayer.1 2 Sep 2005 03:09:10 -0000
> @@ -866,22 +866,15 @@
> .
> .TP
> .B \-channels <number>
> -Change the number of playback channels (default: 2).
> -If the number of output channels is bigger than the number of input channels
> -empty channels are inserted with the help of the channels audio filter (unless
> -mixing from mono to stereo, then the mono channel is repeated in both
> -output channels).
> -The routing will be the default routing for the channels filter.
> -If the number of output channels is smaller than the number of input channels,
> -results depend on the audio decoder (\-afm).
> +Request the number of playback channels (default: 2).
> MPlayer asks the decoder to decode the audio into as many channels as
> specified.
> Now it's up to the decoder to fulfill the requirement.
> -If the decoder outputs more channels than requested, the exceeding channels
> -are truncated.
> This is usually only important when playing videos with AC3 audio (like DVDs).
> In that case liba52 does the decoding by default and correctly downmixes the
> audio into the requested number of channels.
> +To directly control the number of output channels independently of how many
> +channels are decoded, use the channels filter.
> .br
> .I NOTE:
> This option is honored by codecs (AC3 only), filters (surround) and audio
Thanks Corey for taking the time to investigate on this. I don't quite
know what to do here. Should MPlayer behave as stated on the docs
(because maybe there has been a regression lately, but MPlayer used to
behave like the doc says), or should the doc be changed to reflect
MPlayer's behaviour?
I truely don't know what do do about it.
Guillaume
--
Reading doesn't hurt, really!
-- Dominik 'Rathann' Mierzejewski
More information about the MPlayer-DOCS
mailing list