Signed-off-by: NMartin Storsjö <martin@martin.st>

Prefix the functions atrac_generate_tables, atrac_iqmf, dct_quantize_c.
Signed-off-by: NMartin Storsjö <martin@martin.st>

Signed-off-by: NMartin Storsjö <martin@martin.st>

Signed-off-by: NMartin Storsjö <martin@martin.st>

Prefix the functions/tables brktimegm, pcm_read_seek,
dv_offset_reset, voc_get_packet, codec_movaudio_tags,
codec_movvideo_tags.

After this, lavf has no global symbols without the proper prefix.
Signed-off-by: NMartin Storsjö <martin@martin.st>

Signed-off-by: NMartin Storsjö <martin@martin.st>

Signed-off-by: NMartin Storsjö <martin@martin.st>

Since quantisation matrices are stored in context, decoding slices with
different quantisers in parallel leads to unpredictable content of
aforementioned matrices and wrong output picture thereof.

Signed-off-by: NPaul B Mahol <onemda@gmail.com>
Signed-off-by: NDiego Biurrun <diego@biurrun.de>

Signed-off-by: NMartin Storsjö <martin@martin.st>

Signed-off-by: NMartin Storsjö <martin@martin.st>

Signed-off-by: NMartin Storsjö <martin@martin.st>

Keep the old protocol name around for backwards compatibility
until the next bump.

Deprecate the method of implicitly assuming the nested protocol.
For applehttp://server/path, it might have felt logical, but
supporting hls://server/path isn't quite as intuitive. Therefore
only support hls+http://server/path from now on.

Using this protocol at all is discouraged, since the hls demuxer
is more complete and fits into the architecture better. There
have been cases where the protocol implementation worked better
than the demuxer, but this should no longer be the case.
Signed-off-by: NMartin Storsjö <martin@martin.st>

Signed-off-by: NMartin Storsjö <martin@martin.st>

When this demuxer was created, there didn't seem to be any
consensus of a common short name for this protocol. Now
the consensus seems to be to call it hls.
Signed-off-by: NMartin Storsjö <martin@martin.st>

This is different from the "modern" RTP payload formats for H263
as defined by RFC 4629, 2429 and 3555. According to the newer RFCs,
this old one is to be considered deprecated and only be used for
interoperating with legacy systems.
Signed-off-by: NMartin Storsjö <martin@martin.st>

Prevents crashes with the fuzzed samples from bugs 88, 89 and 125 after
"golomb: avoid infinite loop on all-zero input".

Signed-off-by: NPaul B Mahol <onemda@gmail.com>
Signed-off-by: NJustin Ruggles <justin.ruggles@gmail.com>

Signed-off-by: NMartin Storsjö <martin@martin.st>

This is required when stream copying VC1 in ismv - there's one
global header in the moov atom, but keyframes have a separate
sequence header prepended.
Signed-off-by: NMartin Storsjö <martin@martin.st>

Factors all context dynamic memory handling to its own functions.
Fixes bug 220.

Also adds an error message.

It is used as bitfield with 16 entries.

This allows easily differentiating between both implementations within the build
system and combining the native implementation for plain RTMP with librtmp for
the RTMPE, RTMPS, RTMPT, RTMPTE protocol variants.

Signed-off-by: NMartin Storsjö <martin@martin.st>

Signed-off-by: NPaul B Mahol <onemda@gmail.com>
Signed-off-by: NDiego Biurrun <diego@biurrun.de>

They were introduced in an earlier commit that introduced use of named
arguments. One cause was a typo, a second cause appears to be a bug in
x264asm that I work around by not using named arguments.

Signed-off-by: NJanne Grunau <janne-libav@jannau.net>

If muxing into mpegts, 4 byte startcodes for the first NAL
of an access unit is required. Thus it is simplest for the
RTP depacketizer to just use 4 byte startcodes everywhere.
Signed-off-by: NMartin Storsjö <martin@martin.st>

This avoids unused variable warnings when zlib/bzlib are not available.

This allows dropping the av_unused argument from them.

Recent versions of gcc (4.4+) no longer give false positive warnings.

Signed-off-by: NMartin Storsjö <martin@martin.st>