- 15 Jan, 2019 1 commit
-
-
Carl Eugen Hoyos authored
Fixes a warning using musl: In file included from libavformat/rtpproto.c:43:0: /usr/local/musl/include/sys/poll.h:1:2: warning: #warning redirecting incorrect #include <sys/poll.h> to <poll.h>
-
- 03 Oct, 2018 1 commit
-
-
Marton Balint authored
Signed-off-by: Marton Balint <cus@passwd.hu>
-
- 06 Jan, 2018 1 commit
-
-
Rostislav Pehlivanov authored
Only used by ffserver Signed-off-by: Rostislav Pehlivanov <atomnuker@gmail.com>
-
- 13 Nov, 2016 1 commit
-
-
Vlad Tarca authored
Pro-MPEG Code of Practice #3 release 2 forward error correction for rtp_mpegts streams Signed-off-by: Vlad Tarca <vtarca@mobibase.com> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
- 03 Nov, 2016 1 commit
-
-
Diego Biurrun authored
-
- 24 Mar, 2016 1 commit
-
-
Martin Storsjö authored
Since all URLContexts have the same AVOptions, such AVOptions will be applied on the outermost context only and removed from the dict, while they probably make sense on all contexts. This makes sure that rw_timeout gets propagated to the innermost URLContext (to make sure it gets passed to the tcp protocol, when opening a http connection for instance). Alternatively, such matching options would be kept in the dict and only removed after the ffurl_connect call. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 07 Mar, 2016 1 commit
-
-
Zhao Zhili authored
We cannot play multiple multicast streams with the same port at the same time. This is because both rtp and rtcp port are opened in read-write mode, so they will not bind to the multicast address. Try to make rtp port as read-only by default to solve this bug. Signed-off-by: Zhao Zhili <wantlamy@gmail.com> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
- 04 Mar, 2016 1 commit
-
-
Derek Buitenhuis authored
Signed-off-by: Derek Buitenhuis <derek.buitenhuis@gmail.com>
-
- 22 Feb, 2016 2 commits
-
-
Anton Khirnov authored
This way, the decisions about which protocols are available for use in any given situations can be delegated to the caller.
-
Anton Khirnov authored
Instead of a linked list constructed at av_register_all(), store them in a constant array of pointers. Since no registration is necessary now, this removes some global state from lavf. This will also allow the urlprotocol layer caller to limit the available protocols in a simple and flexible way in the following commits.
-
- 02 Feb, 2016 1 commit
-
-
Michael Niedermayer authored
Reviewed-by: Andreas Cadhalpun <andreas.cadhalpun@googlemail.com> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
- 04 Dec, 2015 1 commit
-
-
Clément Bœsch authored
-
- 11 Apr, 2015 1 commit
-
-
Michael Niedermayer authored
Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 01 Apr, 2015 2 commits
-
-
Luca Barbato authored
It gets forwarded down to UDP.
-
Luca Barbato authored
Signed-off-by: Luca Barbato <lu_zero@gentoo.org>
-
- 24 Dec, 2014 1 commit
-
-
Michael Niedermayer authored
Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 09 Dec, 2014 1 commit
-
-
Martin Storsjö authored
Only the upper 2 bits of the first byte are known to be a fixed value. The lower bits in the first byte of a RTP packet could be set if the input is from another RTP packetizers than libavformat's, but for RTCP packets, they would also be set when sending RTCP RR packets, triggering false warnings about incorrect input format to the protocol. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 08 Dec, 2014 1 commit
-
-
Martin Storsjö authored
Tell the user that the RTP muxer needs to be used to packetize the data - using the RTP protocol on its own isn't enough. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 27 Nov, 2014 1 commit
-
-
Vincent Bernat authored
By appending `?dscp=26` to the URL, IP packets will be classified as AF31 (assured forwarding for multimedia flows with low probability of loss). On congested network, this allows a user to assign priorities to flows. Signed-off-by: Vincent Bernat <vincent@bernat.im>
-
- 20 Oct, 2014 1 commit
-
-
Luca Barbato authored
CC: libav-stable@libav.org Bug-Id: CID 1238797
-
- 16 Sep, 2014 1 commit
-
-
Michael Niedermayer authored
It appears this breaks build with MSVC until someone who has MSVC setup has time to investigate and workaround/fix this, its better to revert so that build is not broken Thats even more so as the original commit only fixed a hypothetical issue This reverts commit e587a428.
-
- 15 Sep, 2014 1 commit
-
-
Michael Niedermayer authored
Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 25 Oct, 2013 1 commit
-
-
lemonlinger@gmail.com authored
avformat/rtpproto: when local rtp port and local rtcp port are not specified, try to make two successive ports and retry 3 times when failed some video players on Android will not send udp hole punching messages if the rtcp port and rtp port are not two successive integers. So, if the video player is behind NAT, it could not receive and rtp messages via udp Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 15 Aug, 2013 2 commits
-
-
Martin Storsjö authored
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: Martin Storsjö <martin@martin.st>
-
Dave Yeo authored
Some systems, such as OS/2, define AF_INET6 without a full implementation. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 14 Aug, 2013 1 commit
-
-
Martin Storsjö authored
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: Martin Storsjö <martin@martin.st>
-
- 13 Aug, 2013 1 commit
-
-
Martin Storsjö authored
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: Martin Storsjö <martin@martin.st>
-
- 01 Aug, 2013 2 commits
-
-
Martin Storsjö authored
A separate rtcp port can already be set when opening the rtp protocol normally, but when doing port setup as in RTSP (where we first need to open the local ports and pass them to the peer, and only then receive the remote peer port numbers), we didn't check the same url parameter as in the normal open routine. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
I doubt that anyone ever would try to send a 1 byte packet via the RTP protocol, but check just in case - it shouldn't crash at least. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 31 Jul, 2013 4 commits
-
-
Martin Storsjö authored
Mixing these with the rtp depacketizer functions in rtpdec.h is no good. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
This avoids having duplicate code where only the fd parameter differs. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
The fdset is a pollfd array nowadays, and it is already populated at this point. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 29 Jul, 2013 1 commit
-
-
Ed Torbett authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 19 Jul, 2013 2 commits
-
-
Martin Storsjö authored
If another peer is sending unicast packets to the same port that we are listening on, those packets can end up being received despite using source specific multicast. For those cases, manually check the source address of received packets against the intended source address. This only handles the case when the source list is one single IP address for now, which probably is the most common case. Based on a patch by Ed Torbett. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Ed Torbett authored
Blocking/exclusion is not supported yet. The rtp protocol parameter takes the same form as the existing sources parameter for the udp protocol. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 18 Jul, 2013 1 commit
-
-
Ed Torbett authored
Passes Source-Specific Multicast parameters read from an sdp file through to the UDP socket code, allowing source-specific multicast streams to be correctly received. As an integral part of this change, additional checking (currently only enabled in the case of SSM streams, but probably useful in similar scenarios) has been added to the RTP protocol handler to distinguish UDP packets arriving from multiple sources to the same port and process only the expected packets (those transmitted from the expected UDP source address). This resolves an issue identified when multiple instances of FFmpeg subscribe to different Source-Specific Multicast streams but with each sharing the same destination port. Signed-off-by: Edward Torbett <ed.torbett@simulation-systems.co.uk> Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 12 Dec, 2012 1 commit
-
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 17 Aug, 2012 2 commits
-
-
Jordi Ortiz authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
Jordi Ortiz authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-