Discovering what element caused a warning?

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Discovering what element caused a warning?

Murray Cumming
My pipeline's bus is giving me a GST_MESSAGE_WARNING GtkMessage whose
GError has:
  domain: GST_STREAM_ERROR
  code: GST_STREAM_ERROR_WRONG_TYPE (The stream is of a different type
than handled by this element.)
  message: "No decoder available for type 'audio/mpeg,
mpegversion=(int)4, framed=(boolean)true, codec_data=(buffer)1188,
rate=(int)48000, channels=(int)1'."

I am fairly sure that the affected element is my uridecodebin, but my
question is How can I generally discover at runtime what element(s) are
involved in a particular bus warning or error?

--
[hidden email]
www.murrayc.com
www.openismus.com


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
Reply | Threaded
Open this post in threaded view
|

Re: Discovering what element caused a warning?

michael smith-6-3
On Wed, Jul 29, 2009 at 4:33 PM, Murray Cumming<[hidden email]> wrote:

> My pipeline's bus is giving me a GST_MESSAGE_WARNING GtkMessage whose
> GError has:
>  domain: GST_STREAM_ERROR
>  code: GST_STREAM_ERROR_WRONG_TYPE (The stream is of a different type
> than handled by this element.)
>  message: "No decoder available for type 'audio/mpeg,
> mpegversion=(int)4, framed=(boolean)true, codec_data=(buffer)1188,
> rate=(int)48000, channels=(int)1'."
>
> I am fairly sure that the affected element is my uridecodebin, but my
> question is How can I generally discover at runtime what element(s) are
> involved in a particular bus warning or error?

The message is a GstMessage, not a GtkMessage. GstMessage::src points
at the source of the message; you can look at that to figure out what
sent it.

Mike

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
Reply | Threaded
Open this post in threaded view
|

Re: Discovering what element caused a warning?

ved kpl
GST_ELEMENT_NAME(GST_MESSAGE_SRC(msg)) will printout the name of the
element that has posted the message.

Vikram

On 7/30/09, Michael Smith <[hidden email]> wrote:

> On Wed, Jul 29, 2009 at 4:33 PM, Murray Cumming<[hidden email]> wrote:
>> My pipeline's bus is giving me a GST_MESSAGE_WARNING GtkMessage whose
>> GError has:
>>  domain: GST_STREAM_ERROR
>>  code: GST_STREAM_ERROR_WRONG_TYPE (The stream is of a different type
>> than handled by this element.)
>>  message: "No decoder available for type 'audio/mpeg,
>> mpegversion=(int)4, framed=(boolean)true, codec_data=(buffer)1188,
>> rate=(int)48000, channels=(int)1'."
>>
>> I am fairly sure that the affected element is my uridecodebin, but my
>> question is How can I generally discover at runtime what element(s) are
>> involved in a particular bus warning or error?
>
> The message is a GstMessage, not a GtkMessage. GstMessage::src points
> at the source of the message; you can look at that to figure out what
> sent it.
>
> Mike
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> gstreamer-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
Reply | Threaded
Open this post in threaded view
|

Re: Discovering what element caused a warning?

Murray Cumming
On Thu, 2009-07-30 at 11:37 +0900, ved kpl wrote:
> GST_ELEMENT_NAME(GST_MESSAGE_SRC(msg)) will printout the name of the
> element that has posted the message.

Thanks. That worked perfectly.

--
[hidden email]
www.murrayc.com
www.openismus.com


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
Reply | Threaded
Open this post in threaded view
|

Re: Discovering what element caused a warning?

Sebastian Dröge-7
Am Donnerstag, den 30.07.2009, 21:49 +0200 schrieb Murray Cumming:
> On Thu, 2009-07-30 at 11:37 +0900, ved kpl wrote:
> > GST_ELEMENT_NAME(GST_MESSAGE_SRC(msg)) will printout the name of the
> > element that has posted the message.
>
> Thanks. That worked perfectly.

You should check if the message src was really a GstElement. It could
also be any other GstObject subtype (but usually is a GstElement)

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel

signature.asc (204 bytes) Download Attachment