- 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.
-
- 27 Jul, 2015 1 commit
-
-
Vittorio Giovara authored
Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-
- 09 May, 2015 1 commit
-
-
wm4 authored
APIC tags always have a description. Tag writers obviously leave it empty if there is no description. In this case, libavformat would export "" as title. Do not set the title instead.
-
- 24 Feb, 2015 1 commit
-
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 14 Jan, 2015 3 commits
-
-
Anton Khirnov authored
In v2.2, the picture type is not a zero-terminated string, but has a constant size of 3 bytes.
-
Anton Khirnov authored
Some of them are not immediately obvious.
-
Anton Khirnov authored
Those functions should not ever modify it.
-
- 03 May, 2013 1 commit
-
-
Luca Barbato authored
Prevent a serious out of buffer bound write. Reported-by: Mateusz "j00ru" Jurczyk and Gynvael Coldwind CC:libav-stable@libav.org
-
- 02 May, 2013 1 commit
-
-
Luca Barbato authored
Signed-off-by: Diego Biurrun <diego@biurrun.de>
-
- 30 Apr, 2013 1 commit
-
-
Diego Biurrun authored
-
- 04 Apr, 2013 1 commit
-
-
Anton Khirnov authored
Reported-by: Mateusz "j00ru" Jurczyk and Gynvael Coldwind CC: libav-stable@libav.org
-
- 08 Mar, 2013 1 commit
-
-
Anton Khirnov authored
This will allow us to avoid copying the packets in many cases. This breaks ABI.
-
- 22 Nov, 2012 1 commit
-
-
Anton Khirnov authored
Current code would incorrectly process e.g. 'ff 00 ff 00 ff' to 'ff ff ff', while it should be 'ff ff 00 ff'. Fixes Bug 395. CC: libav-stable@libav.org
-
- 17 Sep, 2012 2 commits
-
-
Clément Bœsch authored
It would have been done anyway in the av_dict_set() call. This simplifies the code and avoid a warning because of assigning a const string from ff_id3v1_genre_str to a non-const variable. Signed-off-by: Anton Khirnov <anton@khirnov.net>
-
Clément Bœsch authored
This also avoids a memleak. Signed-off-by: Anton Khirnov <anton@khirnov.net>
-
- 12 Aug, 2012 1 commit
-
-
Mohammad Alsaleh authored
Some files' embedded art seems to have the mimetype 'image/JPG' instead of 'image/jpg'. Libav fails to parse those because it matches case-sensitively. Use av_strncasecmp() to fix this behaviour. Signed-off-by: Mohammad Alsaleh <msal@tormail.org> Signed-off-by: Anton Khirnov <anton@khirnov.net>
-
- 08 Aug, 2012 1 commit
-
-
Mohammad Alsaleh authored
id3 v2.2 uses image format ("JPG","PNG") instead of mimetypes. Currently, the attached picture is skipped because the format string does not match a known picture mimetype. This patch fixes this behaviour. Signed-off-by: Mohammad Alsaleh <msal@tormail.org> Signed-off-by: Anton Khirnov <anton@khirnov.net>
-
- 07 Aug, 2012 1 commit
-
-
Anton Khirnov authored
-
- 07 Jul, 2012 1 commit
-
-
Anton Khirnov authored
-
- 01 Apr, 2012 1 commit
-
-
Anton Khirnov authored
In v2.4, the length includes the length field itself.
-
- 29 Mar, 2012 1 commit
-
-
Kostya Shishkov authored
-
- 20 Mar, 2012 1 commit
-
-
Anton Khirnov authored
-
- 29 Feb, 2012 3 commits
-
-
Anton Khirnov authored
Rename ff_id3v2_read_all to ff_id3v2_read().
-
Anton Khirnov authored
-
Anton Khirnov authored
-
- 10 Dec, 2011 1 commit
-
-
Diego Biurrun authored
-
- 02 Nov, 2011 1 commit
-
-
Anton Khirnov authored
-
- 13 Oct, 2011 2 commits
-
-
Diego Biurrun authored
-
Diego Biurrun authored
-
- 11 Oct, 2011 1 commit
-
-
Anton Khirnov authored
Bug found by Laurent Aimar fenrir at videolan org
-
- 03 Oct, 2011 3 commits
-
-
Anton Khirnov authored
-
Anton Khirnov authored
Read the key in the first, value in the second. This allows to avoid pointless strdups and simplify decode_str() by dropping two of its parameters.
-
Anton Khirnov authored
While they're technically invalid, it's better to skip them and try to read the rest of the tag.
-
- 21 Sep, 2011 1 commit
-
-
David Goldwich authored
This extends the ID3v2 parser to allow for reading of non-text (i.e. other than T***) meta tag frames providing a ff_id3v2_read_all() function. An additional data structure 'ID3v2ExtraMeta' is introduced for these tags since AVDictionary is string oriented and unsuitable for binary data. A parser for tag frames of type GEOB is implemented, which is needed to extract keyring information from encrypted OMA files. GEOB data is parsed into 'ID3v2ExtraMetaGEOB' data structures. The routine to decode characters from different encodings to UTF-8, formerly part of the read_ttag() function, is moved to its own function. Because some tag frames contain subparts of unknown length, the function is now also able to read until a null character is found. In addition, the function now takes care of allocating a buffer long enough to hold the decoded characters. Signed-off-by: David Goldwich <david.goldwich@gmail.com> Signed-off-by: Anton Khirnov <anton@khirnov.net>
-
- 08 Jun, 2011 1 commit
-
-
Anton Khirnov authored
-
- 26 May, 2011 2 commits
-
-
Alex Converse authored
-
Alex Converse authored
-
- 22 Mar, 2011 2 commits
-
-
Anton Khirnov authored
fixes issue2649.
-
Anton Khirnov authored
It's pointless, since there's a seek to the end of tag later.
-
- 21 Mar, 2011 1 commit
-
-
Anton Khirnov authored
Signed-off-by: Ronald S. Bultje <rsbultje@gmail.com>
-