1. 18 May, 2016 2 commits
    • Martin Storsjö's avatar
      371df9ba
    • Martin Storsjö's avatar
      avio: Allow custom IO users to get labels for the output bytestream · db7968bf
      Martin Storsjö authored
      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: 's avatarMartin Storsjö <martin@martin.st>
      db7968bf
  2. 17 May, 2016 9 commits
  3. 16 May, 2016 9 commits
  4. 13 May, 2016 3 commits
  5. 11 May, 2016 4 commits
    • Diego Biurrun's avatar
      Add some more deprecation guards · 763d69bf
      Diego Biurrun authored
      Avoids unused function/label/variable warnings after the next version bump.
      763d69bf
    • Diego Biurrun's avatar
      Reduce the scope of some variables · b7e64fba
      Diego Biurrun authored
      This avoids unused variable warnings after the next version bump.
      Also drop a trace level av_log() call that is in the way.
      b7e64fba
    • Martin Storsjö's avatar
      rtsp: Parse SSRC attributes in the SDP · bc2a3296
      Martin Storsjö authored
      When feeding input RTP packets to the depacketizer via custom IO,
      it needs to pick the right stream using the payload type for
      RTP packets, and using the SSRC for RTCP packets. If the first
      packet is an RTCP packet, we don't (currently) know the SSRC
      yet and thus can't pick the right RTP depacketizer to handle it.
      
      By parsing the SSRC attribute in the SDP, we can map initial
      RTCP packets to the right stream.
      Signed-off-by: 's avatarMartin Storsjö <martin@martin.st>
      bc2a3296
    • Martin Storsjö's avatar
      rtpdec: Always check if we have the next packet queued · 9ea78fd0
      Martin Storsjö authored
      It doesn't matter what the actual reason for not returning
      an AVPacket was - if we didn't return any packet and we have
      the next one queued, parse it immediately. (rtp_parse_queued_packet
      always consumes a queued packet if one exists, so there's no risk
      for infinite loops.)
      Signed-off-by: 's avatarMartin Storsjö <martin@martin.st>
      9ea78fd0
  6. 10 May, 2016 4 commits
  7. 06 May, 2016 1 commit
  8. 05 May, 2016 2 commits
  9. 04 May, 2016 3 commits
  10. 03 May, 2016 3 commits