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 588271 - uridecodebin fails to include parsers
uridecodebin fails to include parsers
Status: RESOLVED WONTFIX
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
0.10.x
Other Linux
: Normal enhancement
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-07-10 19:08 UTC by Christian Fredrik Kalager Schaller
Modified: 2011-05-19 08:50 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Christian Fredrik Kalager Schaller 2009-07-10 19:08:40 UTC 
When adding 'parsed=true' to the uridecodebin 'parse' property it fails to
add the needed parser elements and thus we get non-parsed output still.
Comment 1 Sebastian Dröge (slomo) 2009-07-16 18:04:56 UTC 
What do you mean with 'parse' property of uridecodebin? There's nothing like that.

Do you mean on the 'caps' property? If that's the case, which caps are you setting there and which caps does uridecodebin use on the output buffers instead? Also, which codecs/container formats are used in your case?
Comment 2 Christian Fredrik Kalager Schaller 2009-07-16 18:56:59 UTC 
Sorry, yeah meant the caps property. I talked about this with Wim and it is a known issue. Wim was not sure how/if to fix it.
Comment 3 Tim-Philipp Müller 2009-07-16 19:20:49 UTC 
Didn't we basically agree that this was NOTABUG and that you'd want either a uriparsebin written for the purpose, or do your own element selecting in the "autoplug-select" signal?

IIRC this was about formats/parsers where the rank was either NONE or smaller than that of the decoder, so it didn't get autoplugged.
Comment 4 Christian Fredrik Kalager Schaller 2009-07-16 19:38:49 UTC 
I asked Wim about it the day after you and he discussed it, and he was at that point still thinking about the issue and had at that point not decided that setting parsed=true was not the solution.
Comment 5 Christian Fredrik Kalager Schaller 2011-05-19 08:50:23 UTC 
This seems to be fixed in the sense that encodebin can be enabled to plug parsers as needed. So I am closing this.