1. 23 Jun, 2014 1 commit
  2. 22 Jun, 2014 6 commits
  3. 20 Jun, 2014 1 commit
    • Sebastian Dröge's avatar
      audiodecoder: Don't be too picky about the output frame counter · 909dd783
      Sebastian Dröge authored
      With most decoder libraries, and especially when accessing codecs via
      OpenMAX or similar APIs, we don't have the ability to properly related
      the output buffers to a number of input samples. And could e.g. get
      a fractional number of input buffers decoded at a time.
      
      Previously this would in the end lead to an error message and stopped
      playback. Change it to a warning message instead and try to handle it
      gracefully. In theory the subclass can now get timestamp tracking
      wrong if it completely misuses the API, but if on average it behaves
      correct (and gst-omx and others do) it will continue to work properly.
      
      Also add a test for the new behaviour.
      
      We don't change it in the encoder yet as that requires more internal logic
      changes AFAIU and I'm not aware of a case where this was a problem so far.
      909dd783
  4. 13 Jun, 2014 3 commits
  5. 12 Jun, 2014 1 commit
    • Edward Hervey's avatar
      mikey: Fix Wall to NTP conversion · 072fa354
      Edward Hervey authored
      We are scaling from a unit in microseconds to a unit in ((1 << 32) per seconds).
      
      We therefore scale the microseconds values by:
      
               value of a second in the target unit (1 << 32)
        --------------------------------------------------------------
        value of a second in the origin format (1 000 000 microsecond)
      072fa354
  6. 11 Jun, 2014 4 commits
  7. 10 Jun, 2014 3 commits
  8. 09 Jun, 2014 2 commits
  9. 06 Jun, 2014 1 commit
  10. 05 Jun, 2014 1 commit
  11. 04 Jun, 2014 3 commits
  12. 03 Jun, 2014 7 commits
  13. 02 Jun, 2014 2 commits
  14. 29 May, 2014 1 commit
    • Thiago Santos's avatar
      decodebin: aggregate buffering messages · 783195cc
      Thiago Santos authored
      Aggregate buffering messages to only post the lower value
      to avoid setting pipeline to playing while any multiqueue
      is still buffering.
      
      There are 3 scenarios where the entries should be removed from
      the list:
      
      1) When decodebin is set to READY
      2) When an element posts a 100% buffering (already implemented)
      3) When a multiqueue is removed from decodebin.
      
      For item 3 we don't need to handle it because this should only
      happen when either 1 is hapenning or when it is playing a
      chained file, for which number 2 should have happened for the
      previous stream to finish
      
      https://bugzilla.gnome.org/show_bug.cgi?id=726423
      783195cc
  15. 28 May, 2014 1 commit
  16. 27 May, 2014 2 commits
  17. 26 May, 2014 1 commit