1. 23 Dec, 2021 1 commit
  2. 16 Dec, 2021 2 commits
    • Florent Thiery's avatar
      specify in log warning that streams not starting at 0 is perfectly normal · 14692b5f
      Florent Thiery authored
      First, transport streams were originally intended for very long broadcasts (days or weeks. Think television stations). TS uses 33 bits to store 90kHz ticks. This makes timesamp rollovers very common (about once a day). Because the timestamp rolls over so frequently, It is generally not a good idea to rely on the time stamps as anything other than an arbitrary tick on a ever moving clock with a start time at an unknown point in the past. Think of an analog clock, and remove all markings. Without the orientation, you can not use it to tell time. But you can still use it to measure time. In other words the timestamps only have meaning relative to other timestamps in the stream. They do not exist for human convenience. They exist so the decoder can do its job.
      
      But as to why not start at 0 anyway. TS stores pts and dts as separate values, where as other containers use a dts+cts to determine pts. So, If you have a stream with out of order (B) frames, you will encounter frames that must be decoded before time 0, and displayed after. In other words, you will have negative (rolled over) dts values at the start of the stream. To simplify the decoders job, some value larger then the largest possible cts (pts-dts) is added to the pts/dts to bring them into the positive range at the start. This is common practice, and left up to the decoder/player to apply the logic as to what time is displayed to the user.
      
      https://stackoverflow.com/questions/27532571/start-timestamp-of-pts-time-in-an-mpeg-ts-stream-is-not-zero
      14692b5f
    • Florent Thiery's avatar
      add .flake8 file · f0ac2289
      Florent Thiery authored
      f0ac2289
  3. 01 Dec, 2021 1 commit
  4. 30 Nov, 2021 1 commit
  5. 31 May, 2021 1 commit
  6. 12 May, 2021 1 commit
  7. 29 Apr, 2021 1 commit
  8. 10 Mar, 2021 1 commit
  9. 09 Mar, 2021 1 commit
  10. 24 Feb, 2021 3 commits
  11. 28 Jan, 2021 1 commit
  12. 03 Dec, 2020 1 commit
  13. 01 Dec, 2020 1 commit
  14. 27 Nov, 2020 3 commits
  15. 21 Sep, 2020 1 commit
  16. 30 Jul, 2020 1 commit
  17. 13 Jul, 2020 1 commit
  18. 09 Jul, 2020 2 commits
  19. 03 Jul, 2020 3 commits
  20. 24 Jun, 2020 1 commit
  21. 23 Jun, 2020 1 commit
  22. 22 Jun, 2020 3 commits
  23. 19 Jun, 2020 4 commits
  24. 18 Jun, 2020 1 commit
  25. 15 Jun, 2020 1 commit
  26. 12 Jun, 2020 1 commit
  27. 26 May, 2020 1 commit