1. 15 Feb, 2018 3 commits
  2. 08 Feb, 2018 1 commit
  3. 05 Feb, 2018 1 commit
  4. 30 Jan, 2018 1 commit
  5. 03 Jan, 2018 2 commits
  6. 26 Dec, 2017 1 commit
  7. 14 Dec, 2017 1 commit
  8. 08 Dec, 2017 1 commit
  9. 06 Dec, 2017 1 commit
  10. 27 Nov, 2017 1 commit
  11. 26 Nov, 2017 2 commits
  12. 13 Nov, 2017 2 commits
    • Edward Hervey's avatar
      asfdemux: Fix prerolling files with "empty" streams · f86751d9
      Edward Hervey authored
      This is a regression that was introduced by
      commit 1803b3c1
      "    asfdemux: Add support for dvr-ms"
      
      The problem is that some files/streams might contain stream definition
      but there is no actual packets for those streams.
      
      This was used to "define" streams with different bitrates for example.
      
      The first_ts calculation resulted in never ever finding a valid first_ts
      since some streams were empty, and therefore never "activating" itself.
      
      Instead of that we first check if we are prerolled. And if we are we
      unconditionally get the "first_ts"
      
      The preroll check has been adapted to check whether streams of
      each defined type (i.e. audio/video/sub) has been prerolled. This solves
      the problem of having different streams of a particular type where only
      one stream actually has data.
      f86751d9
    • Edward Hervey's avatar
      asfdemux: Store the stream type in streams · 2d9867b1
      Edward Hervey authored
      The field was present but never set :)
      2d9867b1
  13. 26 Sep, 2017 1 commit
  14. 18 Sep, 2017 1 commit
  15. 07 Sep, 2017 1 commit
  16. 31 Aug, 2017 1 commit
  17. 30 Aug, 2017 1 commit
  18. 26 Aug, 2017 3 commits
  19. 20 Aug, 2017 1 commit
  20. 17 Aug, 2017 1 commit
  21. 10 Aug, 2017 2 commits
  22. 09 Aug, 2017 1 commit
  23. 25 Jul, 2017 1 commit
  24. 15 Jul, 2017 4 commits
  25. 11 Jul, 2017 1 commit
  26. 07 Jul, 2017 1 commit
  27. 05 Jul, 2017 1 commit
  28. 27 Jun, 2017 2 commits
    • Edward Hervey's avatar
      asfdemux: More index handling · ec24f4c9
      Edward Hervey authored
      In the same vein as the previous commit, the end of the file might have been
      cut and therefore contains bogus data.
      
      If the object is too short, consider it as garbage and return a non-fatal
      flow.
      
      Regression introduced in 97294eb8
      ec24f4c9
    • Edward Hervey's avatar
      asfdemux; Don't assume index is present at end of file · 0bbdfa8e
      Edward Hervey authored
      Some files have garbage at the end of the file, don't error out if we don't
      find the index there.
      
      Reverts back to previous behaviour (where corrupted/missing indexex were
      not a fatal error).
      
      Regression introduced in 97294eb8
      0bbdfa8e