1. 01 Mar, 2018 1 commit
    • Edward Hervey's avatar
      id3v2: re-fix handling of v2.4 extended headers · 6f5c9db1
      Edward Hervey authored
      The various id3v2 specs handle the extended header sizes differently
      (because hey, it wouldn't be fun otherwise).
      
      http://id3.org/id3v2.3.0 states:
      "Where the 'Extended header size', currently 6 or 10 bytes, excludes
       itself."
      
      http://id3.org/id3v2.4.0-structure states:
        Extended header size   4 * %0xxxxxxx
           Number of flag bytes       $01
           Extended Flags             $xx
      
         Where the 'Extended header size' is the size of the whole extended
         header, stored as a 32 bit synchsafe integer. An extended header can
         thus never have a size of fewer than six bytes.
      
      So in id3v2.4.0 it's the *whole* extended header size (a-la ISOBMFF
      atom), whereas in id3v2.3.0 it's the extended header size *excluding*
      those 4 initial bytes.
      
      And for other versions, god knows..
      
      Fixes regression introduced in commit da607005.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=792983
      6f5c9db1
  2. 28 Feb, 2018 4 commits
  3. 27 Feb, 2018 4 commits
  4. 26 Feb, 2018 4 commits
  5. 24 Feb, 2018 3 commits
  6. 23 Feb, 2018 1 commit
    • Jan Schmidt's avatar
      glimagesink: Correct PAR in output caps when transforming · 09584edc
      Jan Schmidt authored
      When doing a 3D/multiview transformation and rescaling to
      match the output window size, the resulting PAR may
      not match the input any more and needs recalculating,
      or else the GstSample reported to client-draw has the
      wrong PAR.
      09584edc
  7. 22 Feb, 2018 1 commit
  8. 21 Feb, 2018 2 commits
    • Guillaume Desmottes's avatar
      videometa: add support for downstream parameters to ROI meta · f5855d50
      Guillaume Desmottes authored
      The current GstVideoRegionOfInterestMeta API allows elements to detect
      and name ROI but doesn't tell anything about how this information is
      meant to be consumed by downstream elements.
      Typically, encoders may want to tweak their encoding settings for a
      given ROI to increase or decrease their quality.
      Each encoder has its own set of settings so that's not something that
      can be standardized.
      
      This patch adds encoder-specific parameters to the meta which can be
      used to configure the encoding of a specific ROI.
      
      A typical use case would be: source ! roi-detector ! encoder
      with a buffer probe on the encoder sink pad set by the application.
      Thanks to the probe the application will be able to tell to the encoder
      how this specific region should be encoded.
      
      Users could also develop their specific roi detectors meant to be used with a
      specific encoder and directly putting the encoder parameters when
      detecting the ROI.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=793338
      f5855d50
    • Mikhail Fludkov's avatar
      rtpbuffer.h: Add new RTPBuffer flags · d7397f02
      Mikhail Fludkov authored
      These flags will be used for Forward Error Correction purposes
      
      https://bugzilla.gnome.org/show_bug.cgi?id=792695
      d7397f02
  9. 20 Feb, 2018 1 commit
  10. 19 Feb, 2018 7 commits
  11. 18 Feb, 2018 1 commit
  12. 17 Feb, 2018 1 commit
  13. 16 Feb, 2018 1 commit
  14. 15 Feb, 2018 9 commits