- 19 5月, 2016 24 次提交
-
-
由 Anton Khirnov 提交于
Based on a patch by Agatha Hu <ahu@nvidia.com>.
-
由 Timo Rothenpieler 提交于
For some unknown reason enabling these causes proper CBR padding, so as there are no known downsides just always enable them in CBR mode. Signed-off-by: NAnton Khirnov <anton@khirnov.net>
-
由 Timo Rothenpieler 提交于
Signed-off-by: NAnton Khirnov <anton@khirnov.net>
-
由 Anton Khirnov 提交于
Based on a patch by Philip Langdale <philipl@overt.org>
-
由 Timo Rothenpieler 提交于
Signed-off-by: NAnton Khirnov <anton@khirnov.net>
-
由 Anton Khirnov 提交于
-
由 Anton Khirnov 提交于
-
由 Derek Buitenhuis 提交于
Signed-off-by: NDerek Buitenhuis <derek.buitenhuis@gmail.com> Signed-off-by: NAnton Khirnov <anton@khirnov.net>
-
由 Anton Khirnov 提交于
Print them as a subsection of the external library section, in line with what is done for the help text in the previous commit.
-
由 Anton Khirnov 提交于
Group them in a subsection of the external library section. That should make them easier to find and understand how they fit in the scheme of things. Also, rewrite the description text in a similar way as in the previous commit.
-
由 Anton Khirnov 提交于
Add a more accurate description of what the switches actually do (i.e. allow using the given library, not enabling the corresponding codecs etc.). Replace the library descriptions, in many cases boilerplate text without useful information, with a short summary of what the library does.
-
由 Anton Khirnov 提交于
There is no real advantage to listing some codecs or subsystems separately simply because they are somehow "hw-accelerated", on the contrary it makes them harder to find than in a plain alphabetically ordered list.
-
由 Diego Biurrun 提交于
-
由 Diego Biurrun 提交于
-
由 Diego Biurrun 提交于
-
由 Martin Storsjö 提交于
Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Martin Storsjö 提交于
Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Michael Niedermayer 提交于
Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Michael Niedermayer 提交于
Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Michael Niedermayer 提交于
Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Michael Niedermayer 提交于
Previously, we required the minimum number of bytes required for the full box. Don't strictly require the astronomical body and additional notes fields, but do require an altitude field (which currently isn't parsed). This matches the initial length check at the start of the function (which doesn't know about the variable length place field). Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Michael Niedermayer 提交于
Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Martin Storsjö 提交于
Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Martin Storsjö 提交于
This was missed in e1eb0fc9, when ff_interleaved_peek was changed to include const during the evolution of the patch. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
- 18 5月, 2016 10 次提交
-
-
由 Martin Storsjö 提交于
Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Martin Storsjö 提交于
As long as caller only writes packets using av_interleaved_write_frame with no manual flushing, this should allow us to always have accurate durations at the end of fragments, since there should be at least one queued packet in each stream (except for the stream where the current packet is being written, but if the muxer itself does the cutting of fragments, it also has info about the next packet for that stream). Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Martin Storsjö 提交于
Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Martin Storsjö 提交于
Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Martin Storsjö 提交于
Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Martin Storsjö 提交于
Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Martin Storsjö 提交于
This allows callers with avio write callbacks to get the bytestream positions that correspond to keyframes, suitable for live streaming. In the simplest form, a caller could expect that a header is written to the bytestream during the avformat_write_header, and the data output to the avio context during e.g. av_write_frame corresponds exactly to the current packet passed in. When combined with av_interleaved_write_frame, and with muxers that do buffering (most muxers that do some sort of fragmenting or clustering), the mapping from input data to bytestream positions is nontrivial. This allows callers to get directly information about what part of the bytestream is what, without having to resort to assumptions about the muxer behaviour. One keyframe/fragment/block can still be split into multiple (if they are larger than the aviocontext buffer), which would call the callback with e.g. AVIO_DATA_MARKER_SYNC_POINT, followed by AVIO_DATA_MARKER_UNKNOWN for the second time it is called with the following data. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Vittorio Giovara 提交于
-
由 Vittorio Giovara 提交于
Use it in av_dump_format() instead of a huge switch case.
-
由 Vladimir Voroshilov 提交于
Signed-off-by: NVittorio Giovara <vittorio.giovara@gmail.com>
-
- 17 5月, 2016 6 次提交
-
-
由 Martin Storsjö 提交于
Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Diego Biurrun 提交于
-
由 Francois Cartegnie 提交于
Unless specified, users must use non registered range for network id Signed-off-by: NLuca Barbato <lu_zero@gentoo.org>
-
由 Alexandra Hájková 提交于
Use the newly created vlc.h directly instead of including get_bits when needed. The VLC and RL_VLC_ELEM structures are independent from the bitreader. Signed-off-by: NLuca Barbato <lu_zero@gentoo.org>
-
由 Anton Khirnov 提交于
-
由 Anton Khirnov 提交于
-