[gstreamer-bugs] [Bug 582588] [API] Add a way to get the pad corresponding to a taglist

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=582588

  GStreamer | gstreamer (core) | Ver: git

Sebastian Dröge changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #134638|rejected                    |none
               Flag|                            |
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|FIXED                       |
            Summary|[API] Add functions to add  |[API] Add a way to get the
                   |source pad to tag messages  |pad corresponding to a
                   |                            |taglist




------- Comment #4 from Sebastian Dröge  2009-05-27 08:31 UTC -------
Ok, then let's revert this for 0.10 and add a FIXME 0.11 there...

But I don't think the way totem uses it is correct but at least it explains why
it doesn't show bitrate tags for audio/video emitted by a demuxer ;) Wouldn't
it be better for totem to get the pad corresponding to the taglist and check
the caps if they're audio/* or video/*  (and some application/* )? But that's
of course unrelated to the change here (although it would be impossible to get
the pad corresponding to the taglist without either the attached patch or the
committed patch).

Jan, would you be fine to revert the change and commit the attached patch to
this bug instead? It's a bit unclean IMHO but doesn't change the sender of the
message.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=582588.