1. 18 Feb, 2019 1 commit
    • Nicolas Dufresne's avatar
      tests: video: Test video format enum stability · fcaf938e
      Nicolas Dufresne authored
      It is really easy to break the API and insert a new video format in the
      middle of the enum instead of at the end. This minimal test should catch
      the most obvious errors. Ideally, this test should be updated after new
      format have been added, so that it won't allow further modification to
      the enumeration API.
      fcaf938e
  2. 05 Feb, 2019 1 commit
  3. 31 Jan, 2019 1 commit
  4. 30 Jan, 2019 1 commit
    • Seungha Yang's avatar
      meson: Add support orc fallback · 57aba895
      Seungha Yang authored
      Allow fallback to orc subproject if any.
      Additionally 'dependencies' keyword is removed from find_library,
      because it's invalid keyword for find_library.
      57aba895
  5. 28 Jan, 2019 1 commit
  6. 16 Jan, 2019 2 commits
  7. 14 Jan, 2019 2 commits
  8. 11 Jan, 2019 1 commit
    • Alex Ashley's avatar
      codec-utils: support extension audio object type and sample rate · 5767d653
      Alex Ashley authored
      ISO 14496-3 defines that audioObjectType 5 is a special case that
      indicates SBR is present and that an additional field has to be
      parsed to find the true audioObjectType.
      
      There are two ways of signaling SBR within an AAC stream - implicit
      and explicit (see [1] section 4.2). When explicit signaling is used,
      the presence of SBR data is signaled by means of the SBR
      audioObjectType in the AudioSpecificConfig data.
      
      Normally the sample rate is specified by an index into a
      table of common sample rates. However index 0x0f is a special case
      that indicates that the next 24 bits contain the real sample rate.
      
      [1] https://www.telosalliance.com/support/A-closer-look-into-MPEG-4-High-Efficiency-AAC
      
      Fixes #39
      5767d653
  9. 30 Dec, 2018 2 commits
  10. 28 Dec, 2018 1 commit
  11. 27 Dec, 2018 1 commit
  12. 26 Dec, 2018 1 commit
  13. 19 Dec, 2018 2 commits
  14. 18 Dec, 2018 4 commits
  15. 14 Dec, 2018 2 commits
  16. 13 Dec, 2018 1 commit
    • Justin Kim's avatar
      rtcpbuffer: add support XR packet parsing · 5303e2c3
      Justin Kim authored
      According to RFC3611, the extended report blocks in XR packet can
      have variable length. To visit each block, the iterator should look
      into block header. Once XR type is extracted, users can parse the
      detailed information by given functions.
      
      Loss/Duplicate RLE
      The Loss RLE and the Duplicate RLE have same format so
      they can share parsers. For unit test, randomly generated
      pseudo packet is used.
      
      Packet Receipt Times
      The packet receipt times report block has a list of receipt
      times which are in [begin_seq, end_seq).
      
      Receiver Reference Time paser for XR packet
      The receiver reference time has ntptime which is 64 bit type.
      
      DLRR
      The DLRR report block consists of sub-blocks which has ssrc, last RR,
      and delay since last RR. The number of sub-blocks should be calculated
      from block length.
      
      Statistics Summary
      The Statistics Summary report block provides fixed length
      information.
      
      VoIP Metrics
      VoIP Metrics consists of several metrics even though they are in
      a report block. Data retrieving functions are added per metrics.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=789822
      5303e2c3
  17. 30 Nov, 2018 1 commit
  18. 28 Nov, 2018 1 commit
  19. 22 Nov, 2018 1 commit
  20. 12 Nov, 2018 2 commits
  21. 07 Nov, 2018 2 commits
  22. 05 Nov, 2018 1 commit
  23. 01 Nov, 2018 3 commits
  24. 28 Oct, 2018 3 commits
  25. 27 Oct, 2018 1 commit
    • Edward Hervey's avatar
      tests: Solidify tcp connection check · 33e92afd
      Edward Hervey authored
      The previous failure was a timeout which was due to the sending pipeline
      pushing test buffer *before* the remote client was accepted. We would
      therefore never get the buffer on the other side.
      
      While the client socket would indeed appear as "connected", this doesn't
      mean that the remote server side did "accept" it (which is where we then
      add it to the list of remote parties to which data will be sent).
      
      The problem isn't with the element implementation, but to the nature of
      TCP 3-way handshake.
      
      In order to make the test reliable, wait for the sink to have accepted
      the remote client (by checking the number of handles) before sending out
      test buffers.
      33e92afd
  26. 10 Oct, 2018 1 commit
    • Stian Selnes's avatar
      rtpbasepayload: rtpbasedepayload: Add source-info property · f766b85b
      Stian Selnes authored
      Add a source-info property that will read/write meta to the buffers
      about RTP source information. The GstRTPSourceMeta can be used to
      transport information about the origin of a buffer, e.g. the sources
      that is included in a mixed audio buffer.
      
      A new function gst_rtp_base_payload_allocate_output_buffer() is added
      for payloaders to use to allocate the output RTP buffer with the correct
      number of CSRCs according to the meta and fill it.
      
      RTPSourceMeta does not make sense on RTP buffers since the information
      is in the RTP header. So the payloader will strip the meta from the
      output buffer.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=761947
      f766b85b