1. 26 Jun, 2020 3 commits
  2. 25 Jun, 2020 8 commits
  3. 24 Jun, 2020 16 commits
  4. 23 Jun, 2020 11 commits
  5. 22 Jun, 2020 2 commits
    • Sebastian Dröge's avatar
      webrtcbin: Don't call gst_ghost_pad_construct() anymore · aa01e6ba
      Sebastian Dröge authored and GStreamer Marge Bot's avatar GStreamer Marge Bot committed
      It's deprecated, unneeded and doesn't do anything anymore.
      
      Part-of: <gstreamer/gst-plugins-bad!1360>
      aa01e6ba
    • Vivia Nikolaidou's avatar
      Revert "h264parse: Include `interlace-mode` in caps" · 652773de
      Vivia Nikolaidou authored and Sebastian Dröge's avatar Sebastian Dröge committed
      This reverts commit b75a6134.
      
      The parser would only set the mode to progressive or mixed, missing the
      cases where it should have been interleaved. Interleaved is more
      difficult to detect because in h264 it happens per frame. On the other
      hand, h264 decoders detect the interlacing information per-frame and set
      the caps correctly. By giving potentially incorrect interlacing
      information in the parser already, it's being enforced downstream even
      after decoding, breaking some use cases (e.g. an encoder can't properly
      mark the stream as TFF or BFF). On the other hand, there's no valid use
      case for having interlacing information on the caps at the parsing
      stage, so after a lot of discussion, it was decided to revert this.
      
      Initial commit message:
      =========================
      Those are the rules:
      
      In the SPS:
        * if frame_mbs_only_flag=1 => all frame progressive
        * if frame_mbs_only_flag=0 => field_pic_flag defines if each frame is
          progressive or interlaced, thus the mode is 'mixed' in GStreamer
          terms.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=779309
      =========================
      
      Fixes #1313
      
      Part-of: <gstreamer/gst-plugins-bad!1335>
      652773de