- 09 Jan, 2016 1 commit
-
-
Michael Niedermayer authored
Durations outside are not supported Fixes Ticket5114 Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
- 30 Dec, 2015 1 commit
-
-
Michael Niedermayer authored
Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 15 Dec, 2015 1 commit
-
-
erankor authored
support writing encrypted mp4 using aes-ctr, conforming to ISO/IEC 23001-7. 3 new parameters were added: - encryption_scheme - allowed values are none (default) and cenc-aes-ctr - encryption_key - 128 bit encryption key (hex) - encryption_kid - 128 bit encryption key identifier (hex) Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
- 06 Dec, 2015 1 commit
-
-
Anton Khirnov authored
Do not access the encoder options, since it makes no sense when the AVStream codec context is not the encoding context.
-
- 04 Dec, 2015 2 commits
-
-
Clément Bœsch authored
-
Yann Coupin authored
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
- 18 Nov, 2015 1 commit
-
-
John Stebbins authored
This feature allows making associations between audio tracks that apple players recognize. E.g. when an ac3 track has a tref that points to an aac track, devices that don't support ac3 will automatically fall back to the aac track. Apple used to *guess* these associations, but new products (AppleTV 4) no longer guess and this association can only be made explicitly now using the "fall" tref. Signed-off-by: Anton Khirnov <anton@khirnov.net>
-
- 11 Nov, 2015 2 commits
-
-
Martin Storsjö authored
By writing a zero-sized packet, the caller can communicate the start_dts/start_cts for the stream without actually writing the first packet. This allows doing random-access writing of fragments when the start dts of the stream isn't zero, so that the edit list in the moov is written based on timestamps from the nominal start time signaled via the zero-sized packet, while the first proper packet written corresponds to a later fragment. To avoid potential unexpected behaviour, empty packets only set start_dts if the frag_discont flag is set. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
This allows producing fragments discontinously where the video stream has b-frames (but starts at pts=0), but doesn't work for the cases with audio with preroll. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 10 Nov, 2015 1 commit
-
-
Martin Storsjö authored
In most other cases when writing fragmented mp4 files, the output IO context is flushed after each fragment. Also flush it after writing the initial moov, to have it behave in the same way. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 27 Oct, 2015 1 commit
-
-
Hendrik Leppkes authored
-
- 23 Oct, 2015 1 commit
-
-
Martin Storsjö authored
This also makes sure that a fragmented file without the empty_moov flag (i.e. with a non-empty initial moov fragment) actually gets written, if some of the tracks turn out to not have any samples. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 21 Oct, 2015 1 commit
-
-
Andreas Cadhalpun authored
avpriv_ac3_parse_header was removed in commit 3dfb643c. Reviewed-by: Michael Niedermayer <michael@niedermayer.cc> Signed-off-by: Andreas Cadhalpun <Andreas.Cadhalpun@googlemail.com>
-
- 15 Sep, 2015 1 commit
-
-
Michael Niedermayer authored
-
- 12 Aug, 2015 1 commit
-
-
Martin Storsjö authored
The double meaning of the faststart flag (moving a moov atom to the start of files, making them streamable, for non-fragmented files, vs inserting a global sidx index at the start of files for fragmented files) is confusing - see 40ed1cbf for explanation of its origins. Since the second meaning of the flag hasn't been part of any libav release yet, just rename it to get rid of the confusion without any extra deprecation (which wouldn't get rid of the potential confusion, of users adding -movflags faststart even for fragmented files, where it isn't needed for making them "streamable"). This gets back the old behaviour, where -movflags faststart doesn't have any effect for fragmented files. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 10 Aug, 2015 3 commits
-
-
Martin Storsjö authored
For fragmented files with non-empty moov, with a fragment index (sidx), place the index after the initial moov/mdat pair. Previously, for this pathological case, the index was written at the start of the file. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
The same field is also used for writing the sidx index header, for fragmented files, when the faststart flag is used. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
This fixes crashes with pathological cases when trying to write a sidx index (via the -movflags faststart option, in combination with fragmenting options), when no fragments actually have been written. (This is possible if the empty_moov flag isn't used, so that all actual packet data is written in the moov/mdat pair, and no moof/mdat pairs have been written.) In these pathological cases, no sidx should be written at all. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 27 Jul, 2015 1 commit
-
-
Vittorio Giovara authored
Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-
- 18 Jul, 2015 1 commit
-
-
Michael Niedermayer authored
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
- 09 Jul, 2015 1 commit
-
-
compn authored
https://developer.apple.com/library/ios/documentation/AppleApplications/Reference/SafariWebContent/CreatingContentforSafarioniPhone/CreatingContentforSafarioniPhone.html says video/mp4 suggested by BBB on irc. Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 30 Jun, 2015 1 commit
-
-
Luca Barbato authored
Make sure to not write the custom `encoder` string in that case. Bug-Id: 845 CC: libav-stable@libav.org
-
- 21 Jun, 2015 1 commit
-
-
Michael Niedermayer authored
Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 10 Jun, 2015 2 commits
-
-
Michael Niedermayer authored
Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
Janne Grunau authored
display_matrix_size is only initialized when av_stream_get_side_data() returns a side data pointer. The code is safe since the only effect this has is setting the display_matrix pointer to NULL which it was already anyway.
-
- 01 Jun, 2015 1 commit
-
-
Michael Niedermayer authored
Fixes CID1302838 Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 30 May, 2015 1 commit
-
-
Michael Niedermayer authored
Fixes Ticket4337 Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 29 May, 2015 2 commits
-
-
Michael Niedermayer authored
Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
Michael Niedermayer authored
This avoids the possibility for rounding/precision differences between platforms Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 26 May, 2015 2 commits
-
-
Michael Niedermayer authored
Fixes Ticket4267 Approved-by: Baptiste Coudurier <baptiste.coudurier@gmail.com> Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
Michael Niedermayer authored
Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 24 May, 2015 1 commit
-
-
Michael Niedermayer authored
Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 20 May, 2015 2 commits
-
-
Carl Eugen Hoyos authored
Suggested-by: Ronald Bultje
-
Carl Eugen Hoyos authored
This matches the demuxer's behaviour.
-
- 23 Mar, 2015 1 commit
-
-
Martin Storsjö authored
These are essential allowing QuickTime to keep detecting content as slow-motion - this allows preserving them on stream copy. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 20 Mar, 2015 1 commit
-
-
Michael Niedermayer authored
Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 19 Mar, 2015 4 commits
-
-
Anton Khirnov authored
-
Martin Storsjö authored
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: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
When reading these values from track->frag_info, the same adjustment has already been done. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
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: Martin Storsjö <martin@martin.st>
-