1. 02 Nov, 2020 1 commit
  2. 08 Sep, 2020 2 commits
  3. 07 Sep, 2020 3 commits
  4. 24 Aug, 2020 1 commit
  5. 20 Aug, 2020 1 commit
  6. 29 Jul, 2020 1 commit
    • Jordan Petridіs's avatar
      amrnbenc: remove global variables · 995a135d
      Jordan Petridіs authored and GStreamer Marge Bot's avatar GStreamer Marge Bot committed
      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>
  7. 27 Jul, 2020 2 commits
  8. 25 Jul, 2020 2 commits
  9. 24 Jul, 2020 1 commit
  10. 22 Jul, 2020 2 commits
  11. 21 Jul, 2020 3 commits
  12. 10 Jul, 2020 1 commit
  13. 08 Jul, 2020 1 commit
  14. 03 Jul, 2020 1 commit
  15. 02 Jul, 2020 1 commit
  16. 22 Jun, 2020 2 commits
  17. 19 Jun, 2020 2 commits
  18. 10 Jun, 2020 1 commit
  19. 08 Jun, 2020 1 commit
  20. 06 Jun, 2020 1 commit
  21. 05 Jun, 2020 1 commit
  22. 04 Jun, 2020 3 commits
  23. 02 Jun, 2020 2 commits
  24. 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: <gstreamer/gst-plugins-ugly!53>
    • 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: <gstreamer/gst-plugins-ugly!51>
  25. 11 May, 2020 1 commit
  26. 08 Apr, 2020 1 commit
    • Derek Lesho's avatar
      asfdemux: Always re-initialize metadata and global_metadata · 8fe8ed3d
      Derek Lesho authored and Sebastian Dröge's avatar Sebastian Dröge committed
      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