@item Electronic Arts CMV @tab @tab X
@tab Used in NHL 95 game.
@item Electronic Arts TGV @tab @tab X
+@item Electronic Arts TGQ @tab @tab X
@item FFmpeg Video 1 @tab X @tab X
@tab experimental lossless codec (fourcc: FFV1)
@item Flash Screen Video @tab X @tab X
@tab fourccs: QPEG, Q1.0, Q1.1
@item RealVideo 1.0 @tab X @tab X
@item RealVideo 2.0 @tab X @tab X
+@item RealVideo 3.0 @tab @tab X
+ @tab still far from ideal
+@item RealVideo 4.0 @tab @tab X
@item Renderware TXD @tab @tab X
@tab Texture dictionaries used by the Renderware Engine.
@item RTjpeg @tab @tab X
@section Audio Codecs
-@multitable @columnfractions .4 .1 .1 .1 .7
+@multitable @columnfractions .4 .1 .1 .4
@item Name @tab Encoding @tab Decoding @tab Comments
@item 4X IMA ADPCM @tab @tab X
@item 8SVX audio @tab @tab X
@item Musepack @tab @tab X
@tab SV7 and SV8 are supported.
@item Nellymoser ASAO @tab X @tab X
+@item QCELP / PureVoice @tab @tab X
@item Qdesign QDM2 @tab @tab X
@tab There are still some distortions.
@item QT IMA ADPCM @tab X @tab X
@section Subtitle Formats
-@multitable @columnfractions .4 .1 .1 .4
+@multitable @columnfractions .4 .1 .1 .1 .1 .1
@item Name @tab Muxing @tab Demuxing @tab Encoding @tab Decoding @tab Rendering
@item ASS/SSA @tab X @tab X
@item DVB @tab X @tab X @tab X @tab X @tab X
@itemize
@item bash 3.1
@item msys-make 3.81-2 (note: not mingw32-make)
-@item w32api 3.12
+@item w32api 3.13
@item mingw-runtime 3.15
@end itemize
@enumerate
@item
Do the regression tests pass with the patch applied?
+@item
+ Does @code{make checkheaders} pass with the patch applied?
@item
Is the patch a unified diff?
@item
Have you checked that the patch does not introduce buffer overflows or
other security issues?
@item
- If you add a new demuxer or decoder, have you checked that it does not
- crash with damaged input (see tools/trasher)?
+ Did you test your decoder or demuxer against damaged data? If no, see
+ tools/trasher and the noise bitstream filter. Your decoder or demuxer
+ should not crash or end in a (near) infinite loop when fed damaged data.
@item
Is the patch created from the root of the source tree, so it can be
applied with @code{patch -p0}?
improves readability.
@item
Did you provide a suggestion for a clear commit log message?
-@item
- Did you test your decoder or demuxer against damaged data? If no, see
- tools/trasher and the noise bitstream filter. Your decoder or demuxer
- should not crash or end in a (near) infinite loop when fed damaged data.
@end enumerate
@section Patch review process