- 14 Jan, 2015 1 commit
-
-
Vittorio Giovara authored
Previously the image sequence was always starting from the minimum number rather than the requested one. CC: libav-stable@libav.org
-
- 09 Jan, 2015 2 commits
-
-
Anton Khirnov authored
-
Anton Khirnov authored
Fixes possible invalid reads. CC:libav-stable@libav.org
-
- 08 Jan, 2015 3 commits
-
-
Martin Storsjö authored
The latest version added support for a new option for enabling a signal level limiter, which adds some extra delay. In fdk-aac, this is enabled by default, but disable it by default here since we'd rather have zero-delay decoding. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Also move the .long_name entry to below the .name entry. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 07 Jan, 2015 3 commits
-
-
Alexandre Colucci authored
These have a DXSA tag and contain alpha in addition to color values for palette. Signed-off-by:
Jean-Baptiste Kempf <jb@videolan.org> Signed-off-by:
Luca Barbato <lu_zero@gentoo.org>
-
Luca Barbato authored
-
Luca Barbato authored
A failure in segment_end() or segment_start() would lead to freeing a dangling pointer and in general further calls to seg_write_packet() or to seg_write_trailer() would have the same faulty behaviour. CC: libav-stable@libav.org Reported-By: luodalongde@gmail.com
-
- 06 Jan, 2015 6 commits
-
-
Martin Storsjö authored
Compared to existing, common opensource H264 encoders, this can be useful since it has got a different license (BSD instead of GPL). Performance- and qualitywise it is comparable to x264 in ultrafast mode. Hooking it up as an encoder in libavcodec also simplifies comparing it against other common encoders. This requires OpenH264 1.3 or newer. Since the OpenH264 API and ABI changes frequently, only releases are supported. To take advantage of the OpenH264 patent offer, the OpenH264 library must not be redistributed, but downloaded at runtime at the end-user's system. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
This was removed accidentally as part of 847bf598. This could cause groundless warning logging. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Justin Ruggles authored
As referenced in the CoreMedia API docs. Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
Bug-Id: CID 1257781
-
Vittorio Giovara authored
This is the order that the caller uses in the rest of the file. Variables are modified to reflect the order above too and their initialization is merged with their declarationt. No behavioral change. Bug-Id: CID 732286
-
- 05 Jan, 2015 10 commits
-
-
Vittorio Giovara authored
The log level is already a warning.
-
Vittorio Giovara authored
-
Vittorio Giovara authored
-
Vittorio Giovara authored
Based on a patch by Michael Niedermayer <michaelni@gmx.at>.
-
Agostino Sarubbo authored
Reduce the chance of introducing a class of bugs quite hard to track.
-
Stefano Pigozzi authored
On some video samples, VDA silently fails to decode frames and returns kVDADecoderNoErr. Error out in these cases to avoid producing AVFrames with empty planes. Signed-off-by:
Stefano Pigozzi <stefano.pigozzi@gmail.com>
-
Diego Biurrun authored
libavcodec/ffv1enc.c:922:53: warning: passing argument 5 of ‘encode_rgb_frame’ discards ‘const’ qualifier from pointer target type
-
Diego Biurrun authored
libavcodec/ffv1dec.c:898:36: warning: cast discards ‘const’ qualifier from pointer target type
-
Vittorio Giovara authored
CC: libav-stable@libav.org Bug-Id: CID 1257779
-
Vittorio Giovara authored
CC: libav-stable@libav.org Bug-Id: CID 1257771
-
- 04 Jan, 2015 5 commits
-
-
Martin Storsjö authored
Being able to write editlists properly is one of the main points in the delay_moov flag. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
CC: libav-stable@libav.org Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
This comment can be traced back to the initial commit from 2001, and it seemed to be misleading/incorect already back then. (It was used for normal, non-raw file formats already then.) Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
This allows using libraries that are detected via pkg-config with msvc. (The libraries themselves may have to be built with MSVC though.) Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Johan Andersson authored
Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 03 Jan, 2015 1 commit
-
-
Martin Storsjö authored
There shouldn't be any need to add the loaded libraries to the global symbol namespace. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 02 Jan, 2015 9 commits
-
-
Martin Storsjö authored
When we don't adjust the Period start time, we don't need to parse the earliest_presentation_time from the sidx boxes either. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
This was only necessary to get playback to start with dash.js 1.2.0, it has been fixed in the git version. The previous behaviour was incorrect - the Period's start time is irrespective of the actual first timestamp of the contents within the period. The Period start time only says when, within the global timeline, this particular piece should start to be played back. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
This should be more correct. This also should give more sensible switching between video streams with different amount of b-frame delay. The current dash.js release (1.2.0) fails to start playback of such files from the start (if the start pts is > 0), but this has been fixed in the current git version of dash.js. Also enable the use of edit lists, so that streams in many cases start at pts=0. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Use the more generic approach with the delay_moov flag, instead of having a update mechanism specific to this one single atom. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
This delays writing the moov until the first fragment is written, or can be flushed by the caller explicitly when wanted. If the first sample in all streams is available at this point, we can write a proper editlist at this point, allowing streams to start at something else than dts=0. For AC3 and DNXHD, a packet is needed in order to write the moov header properly. This isn't added to the normal behaviour for empty_moov, since the behaviour that ftyp+moov is written during avformat_write_header would be changed. Callers that split the output stream into header+segments (either by flushing manually, with the custom_frag flag set, or by just differentiating between data written during avformat_write_header and the rest) will need to be adjusted to take this option into use. For handling streams that start at something else than dts=0, an alternative would be to use different kinds of heuristics for guessing the start dts (using AVCodecContext delay or has_b_frames together with the frame rate), but this is not reliable and doesn't necessarily work well with stream copy, and wouldn't work for getting the right initialization data for AC3 or DNXHD either. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
This allows writing edit lists even when track->entry == 0, if the start times have been set. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
If fragments == 0 it means we haven't written any moov atom yet. If the empty_moov flag is set, we already have written an empty moov atom at startup. Thus, the check for empty_moov is redundant. This is in preparation for allowing writing the moov atom later, even when using the empty moov flag. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by:
Martin Storsjö <martin@martin.st>
-