[Mplayer-cvslog] CVS: main cfg-common.h,1.106,1.107

[Alex Beregszaszi]

Hi,

>  > >  > >  > Settled to CONF_TYPE_IMGFMT which simplified lot of
>  > >  > >  > things. Now there's no need to add new img formats to the
>  > >  > >  > source, instead you can try it out by providing it in
>  > >  > >  > hexa format, and if it isn't supported by the card, you
>  > >  > >  > get a nice error message. That's all.
>  > >  > >  > 
>  > >  > >  > -	{"outfmt", &tv_param_outfmt, CONF_TYPE_STRING, 0, 0, 0,
>  > >  > >  > NULL},+	{"outfmt", &tv_param_outfmt, CONF_TYPE_IMGFMT, 0, 0, 0,
>  > >  > >  > NULL},
>  > >  > > 
>  > >  > > Is this man page entry still correct?
>  > >  > > 
>  > >  > >   outfmt=<value>
>  > >  > >        output format of the  tuner  (yv12,  rgb32,
>  > >  > >        rgb24, rgb16, rgb15, uyvy, yuy2, i420)
>  > >  > Yes and no ;)
>  > >  > Technically you can give everything as hexa and every csp
>  > >  > supported by mplayer, but only the above listed are supported
>  > >  > by the v4l driver. If it catches a non-supported csp, it
>  > >  > prints out a message, that this might be crash or break, but
>  > >  > it will continue. So you could test new formats without
>  > >  > hacking the source.
>  > > 
>  > > Is it worth adding this to the man page?
>  > Dunno, maybe a general description about CONF_TYPE_IMGFMT should be
>  > added (together with the 'help' option) and a tv_v4l specific info
> 
> I was thinking more along the lines of adding "... or an arbitrary
> format specified as hex value."  Is that OK?
yes

-- 
Alex Beregszaszi <alex at fsn.hu>
(MPlayer Core Developer -- http://www.mplayerhq.hu/)