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 322127 - Make all relevant source/sink elements support the GstURIHandler interface
Make all relevant source/sink elements support the GstURIHandler interface
Status: RESOLVED WONTFIX
Product: GStreamer
Classification: Platform
Component: gst-plugins
git master
Other Linux
: Normal enhancement
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-11-22 12:51 UTC by Edward Hervey
Modified: 2011-04-29 13:39 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Edward Hervey 2005-11-22 12:51:54 UTC 
All sink/source elements where it makes sense to have a URI location should
implement GstURIHandler interface.

Good Example : v4lsrc (v4l://[device])
Bad Example : alsasrc
Comment 1 Andy Wingo 2006-01-27 11:40:23 UTC 
Ping, edward?
Comment 2 Edward Hervey 2006-01-27 12:18:25 UTC 
I need to go over all new src/sink sometime. Bug is still valid til checked.
Comment 3 David Schleef 2008-08-12 18:48:42 UTC 
Anyone checked this recently?
Comment 4 Stefan Sauer (gstreamer, gtkdoc dev) 2008-08-20 13:27:09 UTC 
Its quite easy to check with gst-inspector. There is definitely more elements that don't support it yet, that those that do.

Edward: why is alsasrc a bad idea? or worse that v4lsrc/v4l2src?

audiotestsrc/videotestsrc are probably examples that won't need a uri-handler.
Comment 5 Stefan Sauer (gstreamer, gtkdoc dev) 2010-08-11 14:35:02 UTC 
gst-inspector shows 29 elements having it. Still wondering why v4l2src deserves it, but alsasrc not ...
Comment 6 Stefan Sauer (gstreamer, gtkdoc dev) 2011-03-14 20:33:26 UTC 
Patch for alsasrc in Bug #162007
Comment 7 Stefan Sauer (gstreamer, gtkdoc dev) 2011-03-14 20:47:11 UTC 
Edward, it would be good to have a consistent list of elements where this would make sense. 
That said, I feel using uri-handler would mostly be useful for e.g. playbin2 to autoplug a life-source and that again might mostly be interested for testing (It would also be limited as you would not be able to plug an audio and video source at the same time.) Otherwise the element properties should be adequate to configure the elements.
Comment 8 Tim-Philipp Müller 2011-03-14 20:57:45 UTC 
Why make things like alsasrc (or even v4lsrc) implement URI handlers exactly? I just don't see the use case for that (other than testing with playbin).
Comment 9 Tobias Mueller 2011-04-29 13:23:23 UTC 
Reopening as I can't see any open non-developer question.
Comment 10 Tim-Philipp Müller 2011-04-29 13:39:53 UTC 
> Reopening as I can't see any open non-developer question.

It was filed by a developer, who was then asked questions by other developers...

Anyway, let's just WONTFIX this for now, it's been open for years without anything happening. I'm sure someone will re-open it if they can think of a rationale.