GStreamer-devel

element specific bus messages

Classic

List

Threaded

9 messages Options

Tim Hilden

element specific bus messages

hi there,

playing around with the (sparsly documented) Gstreamer a couple of
questions came to my mind.

This one is about the element specific bus messages. Getting a message
of type GST_MESSAGE_ELEMENT I wonder where I can find the "specific
element's documentation" that is mentioned in the API doc. The online
doc of elements like xvimagesink or jpegenc don't contain any
information on what the element's bus messages contain. So where can I
find that information?

Tim

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel

michael smith-6-3

Re: element specific bus messages

On Tue, Jan 20, 2009 at 8:09 AM, Tim Hilden <[hidden email]> wrote:

That would mean a) those elements don't have any element-specific
messages, or b) they're missing documentation for any they might send.

In this case, they just don't have any element-specific messages
(though xvimagesink will send a "prepare-xwindow-id" message - as
documented in the GstXOverlay interface, which it implements.

Mike

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel

Wim Taymans

Re: element specific bus messages

In reply to this post by Tim Hilden

those elements don't implement element specific messages. Take a look
at the spectrum element here for an element that implements element
messages:

http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-good-plugins/html/gst-plugins-good-plugins-spectrum.html

Wim

On Tue, Jan 20, 2009 at 5:09 PM, Tim Hilden <[hidden email]> wrote:

> hi there,
>
> playing around with the (sparsly documented) Gstreamer a couple of
> questions came to my mind.
>
> This one is about the element specific bus messages. Getting a message
> of type GST_MESSAGE_ELEMENT I wonder where I can find the "specific
> element's documentation" that is mentioned in the API doc. The online
> doc of elements like xvimagesink or jpegenc don't contain any
> information on what the element's bus messages contain. So where can I
> find that information?
>
> Tim
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> gstreamer-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
>

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel

Tim Hilden

Re: element specific bus messages

In reply to this post by michael smith-6-3

well, the following code reads the bus messages:

gboolean bus_callback(GstBus *bus, GstMessage *message, gpointer
unused){
printf("%s: %s\n", gst_object_get_name(message->src),\
gst_message_type_get_name(message->type));

switch(GST_MESSAGE_TYPE(message)){
case GST_MESSAGE_ERROR:{
fprintf(stderr, "ERROR\n");
g_main_loop_quit(loop);
break;
}
case GST_MESSAGE_EOS:{
printf("end-of-stream\n");
g_main_loop_quit(loop);
break;
}
}

return true;
}

generates the following output :

demuxer: tag
videosink: element
videosink: element
videosink: state-changed

to me this shows that I rereived an element specific message from
element "videosink", which in this case is a xvimagesink.

now the doc for xvimagesink
http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-base-plugins/html/gst-plugins-base-plugins-xvimagesink.html
doesn't tell me anything about a specific message (unlike the spectrum
element for example). And how am I supposed to make the connection from
xvimagesink to the GstXOverlay definition by just looking at the URL 3
lines up?

Tim

On Tue, 2009-01-20 at 10:16 -0800, Michael Smith wrote:

> On Tue, Jan 20, 2009 at 8:09 AM, Tim Hilden <[hidden email]> wrote:
> > hi there,
> >
> > playing around with the (sparsly documented) Gstreamer a couple of
> > questions came to my mind.
> >
> > This one is about the element specific bus messages. Getting a message
> > of type GST_MESSAGE_ELEMENT I wonder where I can find the "specific
> > element's documentation" that is mentioned in the API doc. The online
> > doc of elements like xvimagesink or jpegenc don't contain any
> > information on what the element's bus messages contain. So where can I
> > find that information?
>
> That would mean a) those elements don't have any element-specific
> messages, or b) they're missing documentation for any they might send.
>
> In this case, they just don't have any element-specific messages
> (though xvimagesink will send a "prepare-xwindow-id" message - as
> documented in the GstXOverlay interface, which it implements.
>
> Mike
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> gstreamer-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel

michael smith-6-3

Re: element specific bus messages

>
> now the doc for xvimagesink
> http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-base-plugins/html/gst-plugins-base-plugins-xvimagesink.html
> doesn't tell me anything about a specific message (unlike the spectrum
> element for example). And how am I supposed to make the connection from
> xvimagesink to the GstXOverlay definition by just looking at the URL 3
> lines up?

The documentation pretty consistently (and sensibly) doesn't duplicate
docs for the interfaces and superclasses of each element.

So, from that URL, the obvious thing to do is to look at documentation
for the interfaces and superclasses. In this case, that page links to
GstXOverlay as one of the interfaces this element implements.

Unfortunately, the link is broken. I'm not sure why; clearly that's a
mistake (GstXOverlay does have documentation). I'll ask around to see
if anyone knows why these links are broken.

Mike

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel

Stefan Sauer

Re: element specific bus messages

Michael Smith schrieb:

>> now the doc for xvimagesink
>> http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-base-plugins/html/gst-plugins-base-plugins-xvimagesink.html
>> doesn't tell me anything about a specific message (unlike the spectrum
>> element for example). And how am I supposed to make the connection from
>> xvimagesink to the GstXOverlay definition by just looking at the URL 3
>> lines up?
>>
>
> The documentation pretty consistently (and sensibly) doesn't duplicate
> docs for the interfaces and superclasses of each element.
>
> So, from that URL, the obvious thing to do is to look at documentation
> for the interfaces and superclasses. In this case, that page links to
> GstXOverlay as one of the interfaces this element implements.
>
> Unfortunately, the link is broken. I'm not sure why; clearly that's a
> mistake (GstXOverlay does have documentation). I'll ask around to see
> if anyone knows why these links are broken.
>
> Mike
>
>

They are uploaded wrongly. It needs a gtkdoc-rebase --online and then
uploading.

Stefan

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel

Jan Schmidt-6

Re: element specific bus messages

On Thu, 2009-01-29 at 17:57 +0200, Stefan Kost wrote:

> >
>
> They are uploaded wrongly. It needs a gtkdoc-rebase --online and then
> uploading.
>
> Stefan
>

Hmmm. How does that look in terms of actual commands to execute? Can we
make the gtkdoc-rebase execution part of the upload make target?

J.
--
Jan Schmidt <[hidden email]>

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel

Stefan Sauer

online api docs

Jan Schmidt schrieb:

> On Thu, 2009-01-29 at 17:57 +0200, Stefan Kost wrote:
>
>
>>>
>>>
>> They are uploaded wrongly. It needs a gtkdoc-rebase --online and then
>> uploading.
>>
>> Stefan
>>
>>
>
> Hmmm. How does that look in terms of actual commands to execute? Can we
> make the gtkdoc-rebase execution part of the upload make target?
>
> J.
>

Uploading is done in common/upload.mak

What it needs is:

cd gstreamer/docs/gst
gtkdoc-rebase --online --html-dir=html
cd gstreamer/docs/libs
gtkdoc-rebase --online --html-dir=html

...

Need to think a bit how to integrate this, as upload.mak is used for
normal docs too. The online rebasing against glib/gtk is broken on e.g.
ubuntu (bug filed) and on most systems you would need to patch
/usr/share/gtk-doc/html/glib/index.sgml
like this (I just committed the online url stuff for glib/gtk docs).
+ <ONLINE href="http://library.gnome.org/devel/glib/unstable/">
<ANCHOR id="glib-building" href="glib/glib-building.html">

Should I for now go thru all the docs and do one manual round (rebase +
call make upload)?

Stefan

------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel

Jan Schmidt-6

Re: online api docs

On Fri, 2009-02-06 at 11:06 +0200, Stefan Kost wrote:
>
> Should I for now go thru all the docs and do one manual round (rebase +
> call make upload)?

Sure, thanks.

As you say, we should figure out how to put it into upload.mak, possibly
as a new rule.

J.
--
Jan Schmidt <[hidden email]>

------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel