- 25 Nov, 2014 2 commits
-
-
Michael Niedermayer authored
Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
Vittorio Giovara authored
CC: libav-stable@libav.org Bug-Id: CID 1245699 / CID 1245700
-
- 24 Nov, 2014 14 commits
-
-
Martin Storsjö authored
This makes sure that the internal utf8 path names are handled properly - the normal file handling functions assume path names are in the native codepage, which isn't utf8. This assumes that the tools outside of lavf don't use the mkdir definition. (The tools don't do the same reading of command line parameters as wchar either - they probably won't handle all possible unicode file parameters properly, but at least work more predictably if no utf8/wchar conversion is involved.) This is moved further down in os_support.h, since windows.h shouldn't be included before winsock2.h, while io.h needs to be included before the manual defines for lseek functions. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
On windows, rename(2) will fail if the target file exists. On unix this trick is used to make sure that people reading the file either will get the full previous file, or the full new version of the file, but no intermediate version. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Uwe L. Korn authored
Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
This makes sure that segments actually start at a keyframe (and makes sure we don't split segments twice in a row, with one segment consisting of only a handful of packets), when one stream uses b-frames while another one doesn't. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
This fixes playback with dash.js, when the input is one separate mp4 file per track. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Vittorio Giovara authored
Fixes a wordly warning from clang -Wsometimes-uninitialized.
-
Michael Niedermayer authored
Prevent NULL dereference. CC: libav-stable@libav.org Bug-Id: CID 703669 Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
'ret' can only be used without initialization if s->height <= 0, which can only happen if avctx->height <= 0, which is validated elsewhere. Doesn't hurt to still initialize it though. CC: libav-stable@libav.org Bug-Id: CID 732296
-
Luca Barbato authored
At least 8 bytes are needed (Mono audio). Bug-Id: CID 741418 CC: libav-stable@libav.org
-
Vittorio Giovara authored
Bug-Id: CID 1238993
-
Vittorio Giovara authored
Also move the check in the case it is actually used. CC: libav-stable@libav.org Bug-Id: CID 1087090
-
Vittorio Giovara authored
-
Vittorio Giovara authored
CC: libav-stable@libav.org Bug-Id: CID 29261
-
Vittorio Giovara authored
CC: libav-stable@libav.org Bug-Id: CID 700556 / CID 700557 / CID 700558
-
- 22 Nov, 2014 3 commits
-
-
Martin Storsjö authored
Don't write any bitrate attribute if it isn't known. As long as one doesn't want automatic bitrate switching, playback can work just fine even if it isn't set. If strict standard compliance is requested, this is still considered an error, since the attribute is mandatory according to the spec. Based on a patch by Rodger Combs. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
The same file already includes this header a few lines further above. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Michael Niedermayer authored
Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 21 Nov, 2014 8 commits
-
-
Luca Barbato authored
Signed-off-by:
Luca Barbato <lu_zero@gentoo.org>
-
Vittorio Giovara authored
CC: libav-stable@libav.org Bug-Id: CID 700555
-
Luca Barbato authored
And use a macro to make apparent why the value. Bug-Id: CID 1108595
-
Luca Barbato authored
CC: libav-stable@libav.org Bug-Id: CID 1198262
-
Vittorio Giovara authored
CC: libav-stable@libav.org Bug-Id: CID 1250330 / CID 1250335
-
Vittorio Giovara authored
CC: libav-stable@libav.org Bug-Id: CID 1250334
-
Luca Barbato authored
CC: libav-stable@libav.org Bug-Id: CID 1087092
-
Martin Storsjö authored
This makes sure the default behaviour of using the internal encoder stays the same regardless if libtwolame is enabled or not (as for any external library). This fixes fate-lavf-mpg if libav is built with libtwolame enabled. CC: libav-stable@libav.org Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
- 19 Nov, 2014 2 commits
-
-
Martin Storsjö authored
The chained flv muxer wants one set of tags - normally this set could be signaled via the AVOutputFormat codec_tag field (as smoothstreamingenc and dashenc do). hdsenc doesn't signal it, since the FLV codec tag arrays aren't exported from flvenc.c. This can lead to the caller keeping an original codec tag from the originating container here, which would then be a mismatch for the FLV muxer. Since we don't really care about what codec tag the caller might have set, just clear it and let the lavf muxer layer set the right one for the chained FLV muxer later instead. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 18 Nov, 2014 1 commit
-
-
Martin Storsjö authored
simd_align_16 is a configure item that can be enabled or disabled, it's not a variable containing a list of other configure items as need_memalign previously. This was broken in eba2233b. CC: libav-stable@libav.org Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 17 Nov, 2014 10 commits
-
-
Vittorio Giovara authored
CC: libav-stable@libav.org Bug-Id: CID 717497
-
Vittorio Giovara authored
CC: libav-stable@libav.org Bug-Id: CID 1194387 / CID 1194389 / CID 1194393 / CID 1206638
-
Vittorio Giovara authored
CC: libav-stable@libav.org Bug-Id: CID 733795
-
Vittorio Giovara authored
Also prevent a NULL pointer dereference. CC: libav-stable@libav.org Bug-Id: CID 1250329 / CID 1250331
-
Martin Storsjö authored
When given a stream starting at dts=0, it would previously consider s->offset as uninitialized and set an offset when the second packet was written, ending up writing two packets with dts=0. By initializing this field to AV_NOPTS_VALUE, we make sure that we only initialize it once, on the first packet. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
This tool can write an MPD file for fragmented MP4 files with a sidx index at the start of the file. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
This is mapped to the faststart flag (which in this case perhaps should be called "shift and write index at the start of the file"), which for fragmented files will write a sidx index at the start. When segmenting DASH into files, there's usually one sidx at the start of each segment (although it's not clear to me whether that actually is necessary). When storing all of it in one file, the MPD doesn't necessarily need to describe the individual segments, but the offsets of the fragments can be fetched from one large sidx atom at the start of the file. This allows creating files for the DASH ISO BMFF on-demand profile. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Previously only tfra entries were added for the first track in each moof. The frag_info array used for tfra can also be used for writing other kinds of fragment indexes, where it's more important to include all tracks. When the separate_moof option is enabled (as in ismv), we write a separate moof for each track, so this doesn't make any difference in that case. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
This is mostly to serve as a reference example on how to segment the output from the mp4 muxer, capable of writing the segment list in four different ways: - SegmentTemplate with SegmentTimeline - SegmentTemplate with implicit segments - SegmentList with individual files - SegmentList with one single file per track, and byte ranges The muxer is able to serve live content (with optional windowing) or create a static segmented MPD. In advanced cases, users will probably want to do the segmenting in their own application code. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
A flag "dash" is added, which enables the necessary flags for creating DASH compatible fragments. When this is enabled, one sidx atom is written for each track before every moof atom. Signed-off-by:
Martin Storsjö <martin@martin.st>
-