Good bug reports are a very valuable contribution to the development of any software project. But just like writing good software, good problem reports @@ -21,7 +21,7 @@ instructions in this document closely.
-If you feel have the necessary skills you are invited to have a go at fixing the bug yourself. Or maybe you already did that? Please read @@ -31,15 +31,15 @@ mailing list will assist you if you have questions.
-First of all please try the latest CVS version of MPlayer as your bug might already be fixed there. Development moves extremely fast, most problems in official releases are reported within days or even hours, so please use only CVS to report bugs. CVS instructions can be found at the bottom of this page or in the - README. If this did not help please refer to - the list of known bugs and the + README. If this did not help please refer to the + list of known bugs and the rest of the documentation. If your problem is not known or not solvable by our instructions, then please report the bug.
@@ -69,7 +69,7 @@ problem or even an answer. -Subscribe to the mplayer-users mailing list:
http://mplayerhq.hu/mailman/listinfo/mplayer-users
@@ -86,9 +86,17 @@
subscribe to actually receive your answer.
You may need to include log, configuration or sample files in your bug + report. If some of them are quite big then it is better to upload them to our + FTP server in a compressed + format (gzip and bzip2 preferred) and include only the path and file name in + your bug report. Our mailing lists have a message size limit of 80k, if you + have something bigger you have to compress or upload it.
+ + +configure.log.
-Please include the output of MPlayer at verbosity level 1, but remember to not truncate the output when you paste it into your mail. @@ -214,13 +222,14 @@ sufficient.
-You have to run MPlayer inside gdb and send us the complete
output or if you have a core dump of the crash you can extract useful
information from the Core file. Here's how:
Please create the following command file:
@@ -255,16 +264,7 @@ gdb mplayer --core=core -batch --command=command_file > mplayer.bug
If something is quite big (logs for instance) then it is better to upload - it to the FTP server in a compressed format (gzip and bzip2 preferred) and - include only the path and filename in your bug report. Our mailing lists - have a message size limit of 80k, if you have something bigger you have to - compress or upload it.
- - -If you created a proper bug report following the steps above and you are confident it is a bug in MPlayer, not a compiler problem or broken diff -r a51f55c5a5a1 -r 636c1e894a27 DOCS/documentation.html --- a/DOCS/documentation.html Thu Jan 09 09:35:01 2003 +0000 +++ b/DOCS/documentation.html Thu Jan 09 09:37:53 2003 +0000 @@ -214,29 +214,17 @@ -
-
This section is about how to enable watching/grabbing from V4L compatible TV tuner. See the man page for a description of TV options and keyboard controls.
-./configure will autodetect
@@ -1118,7 +1132,7 @@
xawtv.Dummy output, to AAlib :)
mplayer -tv on:driver=dummy:width=640:height=480 -vo aa
@@ -1228,7 +1242,7 @@
in the horizontal direction due to a hardware limitation.
The edit decision list (EDL) system allows you to automatically skip or mute
sections of videos during playback, based on a movie specific EDL
@@ -1248,12 +1262,12 @@
If you happen to need more, change the #define MAX_EDL_ENTRIES
in the edl.h file.
Include the -edl <filename> flag when you run MPlayer,
with the name of the EDL file you want applied to the video.
The current EDL file format is:
@@ -1812,6 +1826,10 @@ +There are some public mailing lists on MPlayer. Unless explicitly @@ -2006,5 +2024,9 @@