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 686093 - playbin: player properties not available - get 'uri' returns NULL once playback has started, not current uri
playbin: player properties not available - get 'uri' returns NULL once playba...
Status: RESOLVED NOTABUG
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
1.x
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-10-13 16:13 UTC by Mike
Modified: 2012-10-15 13:15 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
test case (1.16 KB, text/x-python)
2012-10-13 16:13 UTC, Mike 		Details

Description Mike 2012-10-13 16:13:04 UTC 
Created attachment 226380 [details]
test case

under introspection for 1.0.1 there seems to be a bug thats not present under 0.10
its exposed by the code below

works fine under 0.10 introspection so its a regression i guess
Comment 1 Mike 2012-10-13 16:14:02 UTC 
get_property seems to only see certain properties though they all seem available in Gst-1.0.gir
Comment 2 Tim-Philipp Müller 2012-10-13 23:14:03 UTC 
Last I brought this up with Wim it was not a bug, but a feature.

I'll let him explain the rationale and close the bug :)
Comment 3 Mike 2012-10-15 06:31:03 UTC 
be interested to see the rationale, i mean its not hard to workaround, simply assign the property to something else at the time of setting for later use, but still, but i cant see the reason for the change.
Comment 4 Wim Taymans 2012-10-15 07:32:16 UTC 
There are 2 states, the next uri (uri property) and the currently playing uri (current-uri). in 0.10 it's all mapped to the uri property which causes problems
because then, during playback, setting and getting a uri returns different results. In 1.0 it was made into 2 properties to get the full functionality.

You probably want to use the current-uri property. 

Ideas for improvements are welcome, though.
Comment 5 Mike 2012-10-15 13:15:36 UTC 
ok i see, i think that does make sense to me actually, especially in the context of things like crossfading when it would be convenient to have access to the playing and next stream uri, thanks for clearing that up :)