[MPlayer-dev-eng] [PATCH] man page: Where do you want to go tommorow?

[Arpi]

Hi,

> 1. eq intensity
> I don't know much about *_intensity, but I didn't find them in 
> cfg* and now I'm not sure if they exist at all and if the range

they were added by Nick at time of vidix but was removed by me
recently as it was not implemented at teh other end (driver side).

> really is from -1000 to 1000 (from manpage/html docs) and not
> from -100 to 100. Also I couldn't set eq settings to -vo xmga
> with mplayer (I had to use the device to change them) and they
> went from  -128 to 128. IMHO it's a big a mess and nobody is 
> sure if eq setting xy is supported for his vo/card...

eq values are -100 .. +100 everywhere, 0 is the 'normal' setting

it was a big mess, thanks to nick and otghers, but was recently fixed by
alex and others.

> 2. config files
> I'm not sure anymore where the system-wide config file is 
> stored. Is it /etc/mplayer.conf /etc/mplayer/mplayer.conf 
> /usr/local/share/mplayer/mplayer.conf or does it depend on 
> configuration?
yes, it's a configure option

  --confdir=DIR          use this prefix for installing configuration files
                         [same as datadir]

_prefix="/usr/local"
test -z "$_datadir" && _datadir="$_prefix/share/mplayer"
test -z "$_confdir" && _confdir="$_datadir"
DESTDIR =
CONFDIR = \$(DESTDIR)$_confdir
if (m_config_parse_config_file(conf, CONFDIR"/mplayer.conf") < 0)

=>  so unless you use configure options it will be
/usr/local/share/mplayer/mpalyer.conf

imho it's bad, should be /usr/local/etc/mplayer.conf or just
/etc/mplayer.conf or /etc/mplayer/mplayer.conf

> 3. aid range
> Can someone tell me about aid range? I'm absolutely unsure about 
it depends on file format / demuxer! same for vid, sid

> it. From patch:
>     MPG/RM/OGG: 0-31 AVI: 1-99 ASF: 0-127 VOB: 128-159 PCM: 160-191
> Is it AC3+PCM, VOB+PCM, just VOB and could those values be 
> correct (I got them from some source files, it was ac3 instead 
> of vob there)?
mpeg/vob has different layers for audio and video, so tehir numbering is
independent.

so video is numbered from 0..31
mpeg audio layer 1/2/3 (mpeg1, svcd, DV_B_ mpeg2) is numbered 0..31
lpcm/ac3/dts audio (VOB / DV_D_ mpeg2) is numbered 128..(128+31)
subtitles are numbered 0..31

> Is OGG/RM like MPG, like AVI or completely different?
like avi and asf

> 1. man page, html docs, tech docs
> IMHO (and some others) docs should be sthg like this:
>     syntax/option descriptions -> man page
>     practical use, guides, installation, etc -> html docs
>     tech/detailed docs -> tech/* -> simplified in manpage
> I therefore thought that many documentation sections should be 
> moved to the manpage: from 2.5 (tv input), over 2.6 (vop 
> filters), till end of 3 (controls) and more.  It's also easier 
> to maintain the docs this way. IMHO, the html docs should more 
> be like an accumulation of guides, donno...  Diego?

agree.
maybe we should review tech/ section, move options (like lavc-*, swscaler-*
etc) to manpage, and keep only developer files (interfaes, how does the
demuxer work, file format details etc) in tech/

maybe make a new section in manpage, so you don't haveto mix the detailed
explanation of -lavcopts etc to the common options.

like:

LIBAVCODEC options:
... (files from tech/libavc*.txt)

SWSCALER options: 
...

Michael, do you agree, or you want to keep them in .txt format?

> 2. examples/syntax
> I'm not sure at all, what to do with all the examples (see 1. 
> idea). Examples are very important for users. They can be:
>     - beside the described option in the manpage
>     - at the end of manpage (that's best choice and very 
>       practical IMHO)
>     - in the html docs (see syntax description of vcd too...)
> You can't move everything to the manpage as some things really 
> are related to the documentation (dvb for example) and the list 
> is already quite long (but this doesn't disturb much IMHO).
> Another idea was to structure the EXAMPLES section at the end
> into dvd/encoding/etc...

imho manpage should not have big complete examples, it's the job of the
tutorial-like docs. manpage may have simple example, like
-vop filter[=param[:param2]][,filter2...]
   ...
   example: 
   -vop scale=640:-2,rgb2bgr,pp=0x22

> 3. What about a more detailed TODO/IDEAS?
> IMHO more things would be done by users/ppl if they were 
> written down in a TODO (other: section for example ;).
do it :)

> 4. messages
> For me it just looks a bit messy: -quiet, -v (-v), normal 
> output, &>/dev/null </dev/null, etc... -quiet should at least 
> produce zero output IMHO, now it showed all pp changes with divx4 
> (autoq)! -> filled my terminal with messages...

no. -quiet just disables status display, but keep the startup messages.
and it's right imho.

> Nick's colored output looks good too IMHO, it's also easier to 
> read the important informations, especially for new users...
yes i found it a great idea.

> 5. TODO/some ideas (see 3.)
> sw hue,saturation,intensity eq filter?
intensity==brightness
saturation = contrast of U,V planes (easy to implement)
hue = hard to implement and who needs it?
the only use of hue is UV swapping, writing a simple U<->V swapper filter is
easier (using fourcc trick so it doesn't slow things down)

> Write down patch rule to separate cosmetics/spellcheck and real
>   changes, for general syntax changes: Write down procedure 
>   ('>' -> '&gt;').
huh?

> Apply Nick's vidix/mplayerxp changes?
any volunteers with ati cards? rage128 and radeon 8500 has known bugs.

> '-vo fbdev:device' instead of -vo fbdev -fb device?
good idea

> '-dvd 9-12' command line possible? (like chapters)
hmm, why not.

> pre7 today? ;)
with the above changes included :)

> Damn, I wanted to write a one line mail, now I've got over 50. 
no. it's just one line, but that shitty mailer wrapped it :)


A'rpi / Astral & ESP-team

--
Developer of MPlayer, the Movie Player for Linux - http://www.MPlayerHQ.hu