- 14 Feb, 2018 1 commit
-
-
Carl Eugen Hoyos authored
Reviewed-by: Muhammad Faiz
-
- 23 Feb, 2016 1 commit
-
-
Anton Khirnov authored
Currently, AVStream contains an embedded AVCodecContext instance, which is used by demuxers to export stream parameters to the caller and by muxers to receive stream parameters from the caller. It is also used internally as the codec context that is passed to parsers. In addition, it is also widely used by the callers as the decoding (when demuxer) or encoding (when muxing) context, though this has been officially discouraged since Libav 11. There are multiple important problems with this approach: - the fields in AVCodecContext are in general one of * stream parameters * codec options * codec state However, it's not clear which ones are which. It is consequently unclear which fields are a demuxer allowed to set or a muxer allowed to read. This leads to erratic behaviour depending on whether decoding or encoding is being performed or not (and whether it uses the AVStream embedded codec context). - various synchronization issues arising from the fact that the same context is used by several different APIs (muxers/demuxers, parsers, bitstream filters and encoders/decoders) simultaneously, with there being no clear rules for who can modify what and the different processes being typically delayed with respect to each other. - avformat_find_stream_info() making it necessary to support opening and closing a single codec context multiple times, thus complicating the semantics of freeing various allocated objects in the codec context. Those problems are resolved by replacing the AVStream embedded codec context with a newly added AVCodecParameters instance, which stores only the stream parameters exported by the demuxers or read by the muxers.
-
- 18 Feb, 2016 1 commit
-
-
Diego Biurrun authored
-
- 26 Dec, 2015 1 commit
-
-
Diego Biurrun authored
-
- 27 Jul, 2015 1 commit
-
-
Vittorio Giovara authored
Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-
- 19 Apr, 2015 1 commit
-
-
Vittorio Giovara authored
This applies to every library where performance is not critical.
-
- 09 Mar, 2015 1 commit
-
-
Vittorio Giovara authored
In this case len is always at least 3, since it is checked against RTP_HEVC_PAYLOAD_HEADER_SIZE + 1 before entering the switch block. Bug-Id: CID 1238784
-
- 24 Feb, 2015 8 commits
-
-
Martin Storsjö authored
This makes it clear that the individual parsing functions can't touch the parsed out value. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
This is the common style for such comments. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
This avoids implementing a full function just to set this one field. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 23 Feb, 2015 1 commit
-
-
Martin Storsjö authored
Only the first aggregation unit has 2 bytes (DONL) prepended, if such a field is in use. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 21 Feb, 2015 3 commits
-
-
Thomas Volkert authored
With significant changes by Martin Storsjö, to use the shared function instead of reimplementing it. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
For some reason, clang didn't warn about this prior to using the shared function. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 12 Feb, 2015 1 commit
-
-
Thomas Volkert authored
reported by tim dot yao at amlogic dot com Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 17 Jan, 2015 1 commit
-
-
Michael Niedermayer authored
Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 20 Oct, 2014 1 commit
-
-
Vittorio Giovara authored
len is always >=1 in that case. Bug-Id: CID 1238784
-
- 15 Oct, 2014 3 commits
-
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
These are assembled into extradata in the order vps/sps/pps/sei. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 24 Sep, 2014 1 commit
-
-
Vittorio Giovara authored
The RFC spec draft only specifies the "H265" name - there is no specification saying how to interpret "HEVC" (if such a packet format is specified it could be an entirely different format). Since this is a very new standard (still a draft), there is little need for compatibility with existing, broken implementations. Therefore remove the extra alias, to avoid the risk of encouraging incorrect usage. Intentionally keeping the ff_hevc_dynamic_handler name for the handler, to use "hevc" consistently as name for the codec instead of "h265" within the library internals as long as there only is one single variant in actual use. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 21 Sep, 2014 1 commit
-
-
Thomas Volkert authored
rtpdec_hevc: do not print an error message if the received packet has a valid header but lacks additional bytes as payload Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 03 Sep, 2014 1 commit
-
-
Thomas Volkert authored
As specified in draft-ietf-payload-rtp-h265-06. Signed-off-by: Luca Barbato <lu_zero@gentoo.org>
-
- 30 Aug, 2014 1 commit
-
-
Carl Eugen Hoyos authored
-
- 26 Aug, 2014 1 commit
-
-
ThomasVolkert authored
-