Update of /cvsroot/mplayer/main In directory mail:/var/tmp.root/cvs-serv19786 Modified Files: cfg-common.h Log Message: 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. Index: cfg-common.h =================================================================== RCS file: /cvsroot/mplayer/main/cfg-common.h,v retrieving revision 1.106 retrieving revision 1.107 diff -u -r1.106 -r1.107 --- cfg-common.h 13 Aug 2003 16:29:00 -0000 1.106 +++ cfg-common.h 13 Aug 2003 18:56:02 -0000 1.107 @@ -302,7 +302,7 @@ {"width", &tv_param_width, CONF_TYPE_INT, 0, 0, 4096, NULL}, {"height", &tv_param_height, CONF_TYPE_INT, 0, 0, 4096, NULL}, {"input", &tv_param_input, CONF_TYPE_INT, 0, 0, 20, NULL}, - {"outfmt", &tv_param_outfmt, CONF_TYPE_STRING, 0, 0, 0, NULL}, + {"outfmt", &tv_param_outfmt, CONF_TYPE_IMGFMT, 0, 0, 0, NULL}, {"fps", &tv_param_fps, CONF_TYPE_FLOAT, 0, 0, 100.0, NULL}, {"channels", &tv_param_channels, CONF_TYPE_STRING_LIST, 0, 0, 0, NULL}, {"brightness", &tv_param_brightness, CONF_TYPE_INT, CONF_RANGE, -100, 100, NULL},
Alex Beregszaszi writes:
Modified Files: cfg-common.h Log Message: 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) Diego
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.
-- Alex Beregszaszi <alex@fsn.hu> (MPlayer Core Developer -- http://www.mplayerhq.hu/)
Alex Beregszaszi writes:
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? Diego
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
-- Alex Beregszaszi <alex@fsn.hu> (MPlayer Core Developer -- http://www.mplayerhq.hu/)
Alex Beregszaszi writes:
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? Diego
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@fsn.hu> (MPlayer Core Developer -- http://www.mplayerhq.hu/)
participants (3)
-
Alex Beregszaszi -
Alex Beregszaszi -
Diego Biurrun