1. 08 Sep, 2020 2 commits
  2. 07 Sep, 2020 3 commits
  3. 24 Aug, 2020 1 commit
  4. 20 Aug, 2020 1 commit
  5. 29 Jul, 2020 1 commit
    • Jordan Petridіs's avatar
      amrnbenc: remove global variables · 995a135d
      Jordan Petridіs authored
      gstcheck is declaring its own buffers glist which ends up
      overwritten, loks like the code meant to use that already
      
      gcc 10 is also complaining about this, but only on static
      builds for some reason
      
      ```
      FAILED: subprojects/gst-plugins-ugly/tests/check/elements_amrnbenc
      /usr/bin/ld: subprojects/gstreamer/libs/gst/check/libgstcheck-1.0.a(gstcheck.c.o):(.bss+0x38): multiple definition of `buffers'; subprojects/gst-plugins-ugly/tests/check/708af1f@@elements_amrnbenc@exe/elements_amrnbenc.c.o:(.bss+0x18): first defined here
      collect2: error: ld returned 1 exit status
      ```
      
      also remove unused var `current_buf`
      
      Part-of: <!62>
      995a135d
  6. 27 Jul, 2020 2 commits
  7. 25 Jul, 2020 2 commits
  8. 24 Jul, 2020 1 commit
  9. 22 Jul, 2020 2 commits
  10. 21 Jul, 2020 3 commits
  11. 10 Jul, 2020 1 commit
  12. 08 Jul, 2020 1 commit
  13. 03 Jul, 2020 1 commit
  14. 02 Jul, 2020 1 commit
  15. 22 Jun, 2020 2 commits
  16. 19 Jun, 2020 2 commits
  17. 10 Jun, 2020 1 commit
  18. 08 Jun, 2020 1 commit
  19. 06 Jun, 2020 1 commit
  20. 05 Jun, 2020 1 commit
  21. 04 Jun, 2020 3 commits
  22. 02 Jun, 2020 2 commits
  23. 27 May, 2020 2 commits
    • Tim-Philipp Müller's avatar
      tests: fix meson test env setup to make sure we use the right gst-plugin-scanner · 4063a319
      Tim-Philipp Müller authored
      If core is built as a subproject (e.g. as in gst-build), make sure to use
      the gst-plugin-scanner from the built subproject. Without this, gstreamer
      might accidentally use the gst-plugin-scanner from the install prefix if
      that exists, which in turn might drag in gst library versions we didn't
      mean to drag in. Those gst library versions might then be older than
      what our current build needs, and might cause our newly-built plugins
      to get blacklisted in the test registry because they rely on a symbol
      that the wrongly-pulled in gst lib doesn't have.
      
      This should fix running of unit tests in gst-build when invoking
      meson test or ninja test from outside the devenv for the case where
      there is an older or different-version gst-plugin-scanner installed
      in the install prefix.
      
      In case no gst-plugin-scanner is installed in the install prefix, this
      will fix "GStreamer-WARNING: External plugin loader failed. This most
      likely means that the plugin loader helper binary was not found or
      could not be run. You might need to set the GST_PLUGIN_SCANNER
      environment variable if your setup is unusual." warnings when running
      the unit tests.
      
      In the case where we find GStreamer core via pkg-config we use
      a newly-added pkg-config var "pluginscannerdir" to get the right
      directory. This has the benefit of working transparently for both
      installed and uninstalled pkg-config files/setups.
      
      Part-of: <!53>
      4063a319
    • Guillaume Desmottes's avatar
      dvdreadsrc: fix uninitialized warning · 887416db
      Guillaume Desmottes authored
      Variable is always set in actual code paths but let's keep gcc happy.
      
      Part-of: <!51>
      887416db
  24. 11 May, 2020 1 commit
    • Nirbheek Chauhan's avatar
      meson: Pass native: false to add_languages() · 8562bb30
      Nirbheek Chauhan authored
      This is needed for cross-compiling without a build machine compiler
      available. The option was added in 0.54, but we only need this in
      Cerbero and it doesn't affect older versions so it should be ok.
      Will just cause a spurious warning.
      
      Part-of: <!50>
      8562bb30
  25. 08 Apr, 2020 1 commit
    • Derek Lesho's avatar
      asfdemux: Always re-initialize metadata and global_metadata · 8fe8ed3d
      Derek Lesho authored
      When transitioning from the PAUSED state, to the READY state, and back,
      metadata and global_metadata are left uninitialized, unlike when the
      demxuer transitions from NULL to READY, then to PAUSED.  I have found
      this to cause a segmentation fault when fields in these structures are
      set.
      8fe8ed3d
  26. 02 Apr, 2020 1 commit
    • Nicolas Dufresne's avatar
      x264enc: Fix 'ref' property range and default · 15440f2d
      Nicolas Dufresne authored
      The --ref option indicate the size of the DPB, hence should be in the range of
      0 to 16. This patch also fix the default to match x264enc default 3. This
      change isn't a behaviour change since we don't enforce the reported default.
      15440f2d