[gstreamer-bugs] [Bug 161922] script to provide plugin installation info

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=161922

  GStreamer | gstreamer (core) | Ver: HEAD CVS





------- Comment #9 from Tim-Philipp Müller  2007-01-08 09:17 UTC -------
> Can we clarify a few things in the draft?

Yes, I was waiting for the API for this to be finalized and committed first
(bug #392393).


> The entire ID string example given there is
> 'gstreamer.net|0.10|totem|Vorbis audio decoder|decoder-audio/x-vorbis'
>
> * how is the 'Vorbis audio decoder' part generated? caps and name?

Answer 1: the application shouldn't worry about this, it should just get the
entire detail string using gst_missing_plugin_message_get_installer_detail()

Answer 2: you could get it yourself by calling
gst_base_utils_get_decoder_description() with audio/x-vorbis caps.


> * could that app help here, e.g. when the app loads a projects
>   a notices a missing element, I believe it knows from its
>   project file format, if the element is a source (generator)
>   or an effect.

Not sure what you mean here. Do you mean that if you post a missing-plugin
message for an element (by element-name rather than decoder caps) the string
you get is just a generic 'GStreamer foobar element' and you want to supply
hints so it becomes something like 'foobar waveform generator' or so? I think
this kind of thing should either go into
gst_base_utils_get_element_description() or be completely up to the
application. 


> * can we add wrapper plugins there as an open issue

yes, good point, that should be mentioned so packagers are at least aware of
this.


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email