Originally committed as revision 14973 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 14972 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 14971 to svn://svn.ffmpeg.org/ffmpeg/trunk

quickest way to find out if it is needed.

Originally committed as revision 14970 to svn://svn.ffmpeg.org/ffmpeg/trunk

The changes are verified and desired.

Originally committed as revision 14969 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 14968 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 14967 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 14966 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 14965 to svn://svn.ffmpeg.org/ffmpeg/trunk

Patch by Alexander Patrakov ($lastname <whirlpool> gmail.com)
Thread: dcadata.h: fir_32bands_perfect[] is wrong

Originally committed as revision 14964 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 14963 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 14962 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 14961 to svn://svn.ffmpeg.org/ffmpeg/trunk

just in case someone try to seek back after reaching the end of file

Originally committed as revision 14960 to svn://svn.ffmpeg.org/ffmpeg/trunk

when trying to seek past the last index entry, just parse more clusters to add them to the index, until an index entry match the desired position

Originally committed as revision 14959 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 14958 to svn://svn.ffmpeg.org/ffmpeg/trunk

each cluster that is read and that contains a video key frame is added
to the index

Originally committed as revision 14957 to svn://svn.ffmpeg.org/ffmpeg/trunk

matroska timestamps are unsigned

Originally committed as revision 14956 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 14955 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 14954 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 14953 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 14952 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 14951 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 14950 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 14949 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 14948 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 14947 to svn://svn.ffmpeg.org/ffmpeg/trunk

actual hostname. This functionality already exists (and always existed) in
url_split() and is therefore useless. See discussion in "[PATCH] tcp.c/udp.c
memleak?" thread on ffmpeg-devel.

Originally committed as revision 14946 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 14945 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 14944 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 14943 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 14942 to svn://svn.ffmpeg.org/ffmpeg/trunk

All these variables are used as left operands of a movd instruction,
which does accept only memory or register operands while the "g"
constraint also allows immediates. Use "rm" instead.
Patch by Alexis Ballier %alexis P ballier A gmail P com%

Originally committed as revision 14941 to svn://svn.ffmpeg.org/ffmpeg/trunk

order.

Originally committed as revision 14940 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 14939 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 14938 to svn://svn.ffmpeg.org/ffmpeg/trunk

Patch by Alexander Patrakov ($lastname at gmail.com)
Thread: dca.c: output scale is a bit off

Originally committed as revision 14937 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 14936 to svn://svn.ffmpeg.org/ffmpeg/trunk

Originally committed as revision 14935 to svn://svn.ffmpeg.org/ffmpeg/trunk

this leads to a runaway creation of timers. We never pass 0 currently
but it is safer to check for it explicitly as changes to the code can
easily lead to 0 being used.

Originally committed as revision 14934 to svn://svn.ffmpeg.org/ffmpeg/trunk