- 21 8月, 2013 1 次提交
-
-
由 Diego Biurrun 提交于
-
- 20 8月, 2013 9 次提交
-
-
由 John Stebbins 提交于
This allows creation of frame accurate chapter marks from sources like DVD and BD where the precise chapter location is not known until the chapter mark has been reached during reading. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 John Stebbins 提交于
Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Diego Biurrun 提交于
-
由 Luca Barbato 提交于
Do not segfault when writing tracks such as tmcd by writing them down as generic DataHandlers if not known.
-
由 Luca Barbato 提交于
Prevent an assert.
-
由 Luca Barbato 提交于
Data streams have a defined timebase, do not ignore it.
-
由 Martin Storsjö 提交于
Allow emitting the current cluster that is being written before starting a new one, simplifying how to figure out where clusters are positioned in the output stream (for live streaming). Signed-off-by: NLuca Barbato <lu_zero@gentoo.org>
-
由 Luca Barbato 提交于
This simplifies keeping track of cluster boundaries for e.g. livestreaming of WebM. Signed-off-by: NLuca Barbato <lu_zero@gentoo.org>
-
由 Luca Barbato 提交于
Signed-off-by: NLuca Barbato <lu_zero@gentoo.org>
-
- 19 8月, 2013 2 次提交
-
-
由 Luca Barbato 提交于
Signed-off-by: NLuca Barbato <lu_zero@gentoo.org>
-
由 Reimar Döffinger 提交于
Seeking in certain broken files would cause ogg_read_timestamp to fail because ogg_packet would go into a state where all packets of stream 1 would be discarded until the end of the stream. Bug-Id: 553 CC: libav-stable@libav.org Signed-off-by: NJan Gerber <j@v2v.cc> Signed-off-by: NLuca Barbato <lu_zero@gentoo.org>
-
- 18 8月, 2013 1 次提交
-
-
由 Martin Storsjö 提交于
The mov/mp4 muxer has support for handling negative timestamps via edit lists (which customarily is used for handling the 1-frame delay due to B-frames as well). Using the muxer's native way of handling it is better than using the generic offsetting. The generic offsetting is a bit too crude when e.g. the timebase of one track is 1/fps, where the edit lists can handle it accurately. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
- 17 8月, 2013 1 次提交
-
-
由 Janne Grunau 提交于
5ef7c84a broke decoding for the first keyframe due to an unnecessary check for a reference frame. CC: libav-stable@libav.org
-
- 16 8月, 2013 6 次提交
-
-
由 Luca Barbato 提交于
Reported-by: Mateusz "j00ru" Jurczyk and Gynvael Coldwind CC: libav-stable@libav.org
-
由 Luca Barbato 提交于
Reported-by: Mateusz "j00ru" Jurczyk and Gynvael Coldwind CC: libav-stable@libav.org
-
由 Kostya Shishkov 提交于
Implicit vector loads on POWER7 hardware can use the VSX instruction set instead of classic Altivec/VMX. Let's force a VMX load in this case. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Carl Eugen Hoyos 提交于
The counter itself shouldn't be wrapped, since it is used for determining end_pts for the next segment - only wrap the number used for the segment file name. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Stefano Sabatini 提交于
Also avoid comparing NOPTS values. Bug-id: 551 Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Martin Storsjö 提交于
The hls muxer itself doesn't have any direct (object file level) dependencies on mpegtsenc.o, and including that object file directly doesn't ensure that it is registered so that the muxer actually is accessible. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
- 15 8月, 2013 16 次提交
-
-
由 Diego Biurrun 提交于
-
由 Diego Biurrun 提交于
-
由 Diego Biurrun 提交于
-
由 Diego Biurrun 提交于
-
由 Diego Biurrun 提交于
-
由 Diego Biurrun 提交于
Also add missing ff_ prefixes where necessary.
-
由 Diego Biurrun 提交于
-
由 Diego Biurrun 提交于
-
由 Martin Storsjö 提交于
IPPROTO_IPV6 is unrelated here (it's only used in udp.c for multicast sockopts), check for support for the sockaddr_in6 struct itself. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Diego Biurrun 提交于
-
由 Diego Biurrun 提交于
-
由 Diego Biurrun 提交于
-
由 Diego Biurrun 提交于
-
由 Diego Biurrun 提交于
-
由 Janne Grunau 提交于
-
由 Dave Yeo 提交于
Some systems, such as OS/2, define AF_INET6 without a full implementation. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
- 14 8月, 2013 3 次提交
-
-
由 Martin Storsjö 提交于
An SDP description normally only contains the target IP address and port for the packets. This means that we don't really have any clue where to send the RTCP RR packets - previously they're sent to the destination IP written in the SDP (at the same port), which rarely is the actual peer. And if the source for the packets is on a different port than the destination, it's never correct. With a new option, we can choose to send the packets to the address that the latest packet on each socket arrived from. --- Some may even argue that this should be the default - perhaps, but I'd rather keep it optional at first. Additionally, I'm not sure if sending RTCP RR directly back to the source is desireable for e.g. multicast. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Martin Storsjö 提交于
If we've received packets on the same socket before, the return packets are sent to that address. If we've only received packets on the other socket, try to guess the source port for the other one assuming the basic +1/-1 logic. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Martin Storsjö 提交于
Move the sources documentation up below the marker for deprecated otpions. Also mention the new block parameter, that was added in 74972220. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
- 13 8月, 2013 1 次提交
-
-
由 Luca Barbato 提交于
Reported-by: Mateusz "j00ru" Jurczyk and Gynvael Coldwind CC: libav-stable@libav.org
-