1. 29 Jan, 2016 3 commits
  2. 27 Jan, 2016 10 commits
  3. 25 Jan, 2016 1 commit
  4. 22 Jan, 2016 2 commits
  5. 21 Jan, 2016 2 commits
  6. 20 Jan, 2016 4 commits
  7. 19 Jan, 2016 5 commits
  8. 18 Jan, 2016 3 commits
  9. 16 Jan, 2016 1 commit
  10. 14 Jan, 2016 2 commits
  11. 13 Jan, 2016 1 commit
    • Sebastian Dröge's avatar
      wavparse: When flushing on EOS, don't process more data than the "data" size · 53c797d6
      Sebastian Dröge authored
      Even if we have more data queued up when flushing than the size of the data
      chunk, don't process and output it. If the data size is known, this likely
      contains another chunk (e.g. an INFO chunk) or things like ID3 tags. Just
      outputting them as if they were data is going to cause unexpected behaviour
      and unpleasant audio noises.
  12. 12 Jan, 2016 3 commits
    • Antonio Ospite's avatar
      tests: fix a thinko in the wavenc example · be5f9473
      Antonio Ospite authored
      The code is supposed to follow somehow what the comment above says, that
      is to have one channel with a wave of freq 440 and the other channel
      with a wave of freq 880, but an off by one error results in frequencies
      of 0 and 440.
    • Antonio Ospite's avatar
      interleave: Fix the example by setting channel-masks in the sink pads · bdcc0390
      Antonio Ospite authored
      The current example does not work, it fails with:
      ERROR: from element /GstPipeline:pipeline0/GstDecodeBin:decodebin0/GstWavParse:wavparse0: Internal data flow error.
      gstwavparse.c(2178): gst_wavparse_loop (): /GstPipeline:pipeline0/GstDecodeBin:decodebin0/GstWavParse:wavparse0:
      streaming task paused, reason not-negotiated (-4)
      This is because negotiation with wavenc gets messed up by the missing
      channel positions configuration.
      The proper way to define the channel layout when using the interleave
      element in code would be to set the channel-positions property, but
      gst-launch-1.0 does not know how to deal with arrays; so the example
      pipeline works around the issue by setting the channel-masks in the sink
      Also fix a repetition in the deinterleave example description
    • Tim Sheridan's avatar
      sbcparse: Fix frame length calculation · 205565cc
      Tim Sheridan authored
      SBC frame length calculation wasn't being rounded up to the nearest byte
      (as specified in the A2DP 1.0 specification, section 12.9). This could
      cause 'stereo' and 'joint stereo' mode SBC streams to have incorrectly
      calculated frame lengths.
      Incorrect frame length calculation causes frame coalescing to fail, as
      subsequent frames in the stream aren't found in the expected locations.
  13. 11 Jan, 2016 1 commit
  14. 08 Jan, 2016 2 commits