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

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

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

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

Fixes issue987.

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

blocksize.

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

thread "[PATCH] RTSP-MS 15/15: move packet_time_start zero value
assignment in asf.c".

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

requires this to be clear)

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

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

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

pixels, not (dst+pix)>>1.
This makes the mmx functions bitexact with the C functions.

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

trying to enable libamrnb support. The latter function is actually used.
patch by Martin Storsjö, martin martin st

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

Real wants OPTIONS) while the connection is idle, otherwise it will
be aborted after a short period (usually a minute). See the thread
"[PATCH] rtsp.c: keep-alive" on the mailinglist.

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

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

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

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

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

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

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

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

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

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

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

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

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

problems with padding.

Fix issue 959

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

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

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

qualification task, see "RTP/Vorbis payload implementation (GSoC qual
task)" thread on mailinglist.

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

Originally committed as revision 29180 to svn://svn.mplayerhq.hu/mplayer/trunk/libswscale

This fixes RGB32 (et al.) scaling.

Originally committed as revision 29179 to svn://svn.mplayerhq.hu/mplayer/trunk/libswscale

buffer size of the fmtp parameter buffer. For Vorbis RT(S)P, these
contain full Vorbis headers, which can be up to 12kb each, formatted
in base64, so 16kb total. Patch required for proper Vorbis/RTP playback,
submitted as GSoC qualification task in the thread "RTP/Vorbis payload
implementation (GSoC qual task)" by Colin McQuillan m.niloc googlemail
com.

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

This avoids a division by zero in '[in]fifo,scale[out]'

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

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

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

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

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

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

The bug[1] is exposed when gcc decides to put some data in a common
section (i.e. data that will be used by more than one object). It will
suggest the data to be aligned, but binutils >= 2.19 will fail to
properly align it. Thus if the data requires any alignment greater
than 4, the application will crash.
The workaround prevents gcc from putting data in a common section,
instead putting it in a properly aligned section.

[1] http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37216

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

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