[Bug 711456] New: Unable to access on_message msg values in gst-1.2

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=711456
  GStreamer | don't know | 1.2.0

           Summary: Unable to access on_message msg values in gst-1.2
    Classification: Platform
           Product: GStreamer
           Version: 1.2.0
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: don't know
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: ondrejj at salstar.sk
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: 3.7/3.8


After update to gstreamer-1.2, I am unable to access pmt, eit, tot and other
message contents from python. I use this code:

    def on_message(self, bus, msg):
        msgs = msg.get_structure()
        msgn = msgs.get_name()
        if msgn=="pmt":
          print msgs.to_string()
          # process message

In gst-1.0 result is:
pmt, program-number=(uint)36, pcr-pid=(uint)561, version-number=(uint)11,
streams=(structure){ "pid-511\,\ pid\=\(uint\)511\,\ stream-type\=\(uint\)3\,\
lang-code\=\(string\)CZE\,\ descriptors\=\(GValueArray\)NULL\;", "pid-521\,\
pid\=\(uint\)521\,\ stream-type\=\(uint\)6\,\
descriptors\=\(GValueArray\)NULL\;", "pid-561\,\ pid\=\(uint\)561\,\
stream-type\=\(uint\)2\,\ descriptors\=\(GValueArray\)NULL\;" };

In gst-1.2 result is:
pmt, section=(GstMpegTsSection)NULL;

In gst-1.0 I can parse this string and get required information (program
number, description, time offsets, ...
In gst-1.2 this ability is broken. Even if I am trying to use
msgs.get_value("section") I get only an GstMpegTsSection object, which is an
gobject.GBoxed object and has only ability to copy or free it. :-(

I am not sure, if this is a gst-python problem but looks like this structure is
NULL and there is nothing to get in any programming language.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.