- 21 3月, 2015 3 次提交
-
-
由 Anton Khirnov 提交于
It's the output_window that is applied to the output frame, not pic_conf_win
-
由 Anton Khirnov 提交于
-
由 Luca Barbato 提交于
Signed-off-by: NLuca Barbato <lu_zero@gentoo.org>
-
- 20 3月, 2015 3 次提交
-
-
由 Luca Barbato 提交于
It drops everything that cannot be used for re-encoding and/or streamcopy.
-
由 Andreas Cadhalpun 提交于
According to the WebP Lossless Bitstream Specification "each transform is allowed to be used only once". If a transform is more than once this can lead to memory corruption. Signed-off-by: NAndreas Cadhalpun <Andreas.Cadhalpun@googlemail.com> Signed-off-by: NAnton Khirnov <anton@khirnov.net>
-
由 Anton Khirnov 提交于
-
- 19 3月, 2015 9 次提交
-
-
由 Martin Storsjö 提交于
Since the duration is compared to the tfra durations/intervals which are expressed in pts, calculate that here as well. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Martin Storsjö 提交于
For strict CFR, they should be pretty much equal, but if the stream is VFR, there can be a sometimes significant difference. Calculate the pts duration separately, used in sidx atoms and for tfrf/tfxd boxes in smooth streaming ismv files. Also make sure to reduce the duration of sidx entries according to edit lists. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Martin Storsjö 提交于
When reading these values from track->frag_info, the same adjustment has already been done. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Martin Storsjö 提交于
Adjusting it is only necessary when a sidx/tfrf/tfxd atom already has been written for the previous fragment (since the sidx/tfrf/tfxd atoms include the duration between the first pts of the previous fragment, to the first pts of the new fragment). Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Martin Storsjö 提交于
This matches what we write in tfra and tfrf since 9cbf70fa. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Martin Storsjö 提交于
When automatically flushing fragments based on set conditions (fragmentation on keyframes, after some interval or byte size), we already have the next packet for one stream - use this for setting the duration of the last packet in the flushed fragment correctly. This avoids having to adjust the timestamp of the first packet in the new fragment since the last duration was unknown. Unfortunately, this only works for automatic flushing (not for caller-triggered flushing, like in the dash muxer), and only for the one single track that triggered the flushing. The duration of the last sample in all other tracks still is dependent on AVPacket duration (or heuristics). Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Martin Storsjö 提交于
This avoids that the mp4 muxer does a similar heuristic, adjusting the timestamps in a way that the dash muxer doesn't know the actual timestamps written to the file in the end. By making sure that the mp4 muxer internal heuristic isn't applied, we know the exact timestamps written to file, so that the timestamps in manifest match the files. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Martin Storsjö 提交于
Even if this is a guess, it is way better than writing a zero duration of the last sample in a fragment (because if the duration is zero, the first sample of the next fragment will have the same timestamp as the last sample in the previous one). Since we normally don't require libavformat muxer users to set the duration field in AVPacket, we probably can't strictly require it here either, so don't log this as a strict warning, only as info. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Martin Storsjö 提交于
Add a missing AVClass member, check whether localaddr is null. (Previously, localaddr was always a local stack buffer, while it now also can be an avoption string which can be null.) This fixes crashes when not passing any localaddr parameter, since 66028b7b. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
- 18 3月, 2015 2 次提交
-
-
由 Derek Buitenhuis 提交于
The current behavior may produce a different sequence of packets after seeking, compared to demuxing linearly from the beginning. This is because the MOV demuxer seeks in each stream individually, based on timestamp, which may set each stream at a slightly different position than if the file would have been read sequentially. This makes implementing certain operations, such as segmenting, quite hard, and slower than need be. Therefore, add an option which retains the same packet sequence after seeking, as when a file is demuxed linearly.
-
由 Martin Storsjö 提交于
Signed-off-by: NMartin Storsjö <martin@martin.st>
-
- 17 3月, 2015 12 次提交
-
-
由 Vittorio Giovara 提交于
-
由 Vittorio Giovara 提交于
Set this field to TRUE if the audio component is to operate on little-endian data, and FALSE otherwise. However TRUE and FALSE are not defined. Since this flag is just a boolean, interpret all values except for 0 as little endian. Sample-Id: 64bit_FLOAT_Little_Endian.mov
-
由 Vittorio Giovara 提交于
Prevents unsigned overflow and variable truncation. Bug-Id: CID 603186
-
由 Vittorio Giovara 提交于
This is a leftover from the static to dynamic vlc table conversion.
-
由 Carl Eugen Hoyos 提交于
Instead check for all mov code-points when demuxing avi and print a warning if a video codec is found like this. Signed-off-by: NVittorio Giovara <vittorio.giovara@gmail.com>
-
由 Paul B Mahol 提交于
Signed-off-by: NPaul B Mahol <onemda@gmail.com>
-
由 Vittorio Giovara 提交于
-
由 Carl Eugen Hoyos 提交于
Signed-off-by: NVittorio Giovara <vittorio.giovara@gmail.com>
-
由 Niels Möller 提交于
Prevent a spurious read from uninitialized memory.
-
由 Luca Barbato 提交于
It uses 6 registers, unbreaks building on hardened x86 system. Bug-Id: gentoo/541930 CC: libav-stable@libav.org
-
由 Luca Barbato 提交于
As produced by Camtasia 4.
-
由 Diego Biurrun 提交于
-
- 16 3月, 2015 10 次提交
-
-
由 Martin Storsjö 提交于
This is incompatible with the omit_tfhd_offset flag (writing position independent fragments with interleaving requires the default_base_moof flag). This makes the moof atoms slightly bigger, but can be better for playback (improving locality of sample data in the mdat). Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Martin Storsjö 提交于
This is needed if all the data for one track isn't continuous within the mdat. Normally we make sure all the data for one track is continuous, but in new cases we will need to have the samples interleaved. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Janne Grunau 提交于
-
由 Janne Grunau 提交于
-
由 Janne Grunau 提交于
-
由 Janne Grunau 提交于
-
由 Luca Barbato 提交于
Bug-Id: 833
-
由 Himangi Saraogi 提交于
Signed-off-by: NLuca Barbato <lu_zero@gentoo.org>
-
由 Luca Barbato 提交于
Add AVOptions for options currently available as url parameters.
-
由 Luca Barbato 提交于
Use AVOption and fallback over multiple addresses
-
- 15 3月, 2015 1 次提交
-
-
由 Diego Biurrun 提交于
-