After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 750040 - tests: add dynamic audiovisualizers example
tests: add dynamic audiovisualizers example
Status: RESOLVED NOTABUG
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
git master
Other All
: Normal enhancement
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-05-28 14:39 UTC by Luis de Bethencourt
Modified: 2015-05-29 14:44 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
proposed patch (8.49 KB, patch)
2015-05-28 14:39 UTC, Luis de Bethencourt
rejected Details | Review

Description Luis de Bethencourt 2015-05-28 14:39:43 UTC
Created attachment 304175 [details] [review]
proposed patch

Add an example in gst-plugins-base/tests/examples using the audiovisualizers. The audiovisualizer used is switched dynamically every second.
Comment 1 Tim-Philipp Müller 2015-05-28 15:05:01 UTC
Sure, one can add it, but what does this add in addition to e.g. test-effect-switch.c?

(And wouldnl't people usually just use playbin and change the effect there on the fly?)
Comment 2 Luis de Bethencourt 2015-05-28 15:46:50 UTC
To be honest I didn't knew of the existence of gst-plugins-base/tests/icles/test-effect-switch. I based the audiovisualizer switcher in the demo code in the documentation.

The only two differences are:
  - location: eventhough test-effect-switch is in -base some of the elements in the default list are in -good and -bad. My proposal is in the same module where the elements are.
  - audiovisualizers instead of video effects

It is really hard to justify code duplication with only those two differences. 

If an element in the default list isn't available, it won't be added to the queue used in the automatic switching. Not a big problem.

For the second difference, audiovisualizers aren't really that complex to use that they must have example code.

If you agree with this, I am inclined to close this as "Won't Fix" and not merge the code.

In an unrelated topic, what is the reason for the divide between tests/examples and test/icles in gst-plugins-base? This is mostly the reason I didn't knew of this code's existence.
Comment 3 Luis de Bethencourt 2015-05-29 14:44:07 UTC
Review of attachment 304175 [details] [review]:

Close