n00b question: Does this fakesrc output look ok?

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

n00b question: Does this fakesrc output look ok?

Topi Hukkanen
This doesn't quite look like the output from the FAQ.  I am getting an EOS (end of stream?) from the pipeline.  Does this mean something is wrong, or is it normal?  Also, this "E" message, is that an Error?



:~$ gst-launch -v fakesrc num-buffers=3 ! fakesink
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
/pipeline0/fakesrc0: last-message = "get      ******* > (    0 bytes, timestamp: none, duration: none, offset: 0, offset_end: -1, flags: 0) 0x80c9a90"
/pipeline0/fakesink0: last-message = "preroll   ******* "
Pipeline is PREROLLED ...
/pipeline0/fakesink0: last-message = "event   ******* E (type: 102, GstEventNewsegment, update=(boolean)false, rate=(double)1, applied_rate=(double)1, format=(GstFormat)GST_FORMAT_BYTES, start=(gint64)0, stop=(gint64)-1, position=(gint64)0;) 0x8053cc8"
Setting pipeline to PLAYING ...
/pipeline0/fakesink0: last-message = "chain   ******* < (    0 bytes, timestamp: 0:00:00.000000000, duration: none, offset: 0, offset_end: -1, flags: 32) 0x80c9a90"
New clock: GstSystemClock
/pipeline0/fakesrc0: last-message = "get      ******* > (    0 bytes, timestamp: none, duration: none, offset: 1, offset_end: -1, flags: 0) 0x80c9ae0"
/pipeline0/fakesink0: last-message = "chain   ******* < (    0 bytes, timestamp: 0:00:00.000000000, duration: none, offset: 1, offset_end: -1, flags: 0) 0x80c9ae0"
/pipeline0/fakesrc0: last-message = "get      ******* > (    0 bytes, timestamp: none, duration: none, offset: 2, offset_end: -1, flags: 0) 0x80c9b30"
/pipeline0/fakesink0: last-message = "chain   ******* < (    0 bytes, timestamp: 0:00:00.000000000, duration: none, offset: 2, offset_end: -1, flags: 0) 0x80c9b30"
/pipeline0/fakesink0: last-message = "event   ******* E (type: 86, ) 0x8053cc8"
Got EOS from element "pipeline0".
Execution ended after 1044000 ns.
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
FREEING pipeline ...





-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
Reply | Threaded
Open this post in threaded view
|

Re: n00b question: Does this fakesrc output look ok?

Wim Taymans

On Fri, 2008-02-22 at 11:20 +0200, Topi Hukkanen wrote:
> This doesn't quite look like the output from the FAQ.  I am getting an
> EOS (end of stream?) from the pipeline.  Does this mean something is
> wrong, or is it normal?  Also, this "E" message, is that an Error?

It's normal, the FAQ has the output of an older version and is less
verbose. 'E' means event.

Wim

>
>
>
> :~$ gst-launch -v fakesrc num-buffers=3 ! fakesink
> Setting pipeline to PAUSED ...
> Pipeline is PREROLLING ...
> /pipeline0/fakesrc0: last-message = "get      ******* > (    0 bytes,
> timestamp: none, duration: none, offset: 0, offset_end: -1, flags: 0)
> 0x80c9a90"
> /pipeline0/fakesink0: last-message = "preroll   ******* "
> Pipeline is PREROLLED ...
> /pipeline0/fakesink0: last-message = "event   ******* E (type: 102,
> GstEventNewsegment, update=(boolean)false, rate=(double)1,
> applied_rate=(double)1, format=(GstFormat)GST_FORMAT_BYTES,
> start=(gint64)0, stop=(gint64)-1, position=(gint64)0;) 0x8053cc8"
> Setting pipeline to PLAYING ...
> /pipeline0/fakesink0: last-message = "chain   ******* < (    0 bytes,
> timestamp: 0:00:00.000000000, duration: none, offset: 0, offset_end:
> -1, flags: 32) 0x80c9a90"
> New clock: GstSystemClock
> /pipeline0/fakesrc0: last-message = "get      ******* > (    0 bytes,
> timestamp: none, duration: none, offset: 1, offset_end: -1, flags: 0)
> 0x80c9ae0"
> /pipeline0/fakesink0: last-message = "chain   ******* < (    0 bytes,
> timestamp: 0:00:00.000000000, duration: none, offset: 1, offset_end:
> -1, flags: 0) 0x80c9ae0"
> /pipeline0/fakesrc0: last-message = "get      ******* > (    0 bytes,
> timestamp: none, duration: none, offset: 2, offset_end: -1, flags: 0)
> 0x80c9b30"
> /pipeline0/fakesink0: last-message = "chain   ******* < (    0 bytes,
> timestamp: 0:00:00.000000000, duration: none, offset: 2, offset_end:
> -1, flags: 0) 0x80c9b30"
> /pipeline0/fakesink0: last-message = "event   ******* E (type: 86, )
> 0x8053cc8"
> Got EOS from element "pipeline0".
> Execution ended after 1044000 ns.
> Setting pipeline to PAUSED ...
> Setting pipeline to READY ...
> Setting pipeline to NULL ...
> FREEING pipeline ...
>
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
Reply | Threaded
Open this post in threaded view
|

Re: n00b question: Does this fakesrc output look ok?

Topi Hukkanen
Damn reply to all button....

Sorry for the noobspam, but if I run the example:

gst-launch audiotestsrc ! audioconvert ! audioresample ! osssink

I get the dialtone and all looks well...  but is Ctrl-C the proper way to "stop" the program?  I was doing this for webcam examples also, and I'm not sure if there's a "cleaner" way.











On Fri, Feb 22, 2008 at 11:27 AM, Wim Taymans <[hidden email]> wrote:

On Fri, 2008-02-22 at 11:20 +0200, Topi Hukkanen wrote:
> This doesn't quite look like the output from the FAQ.  I am getting an
> EOS (end of stream?) from the pipeline.  Does this mean something is
> wrong, or is it normal?  Also, this "E" message, is that an Error?

It's normal, the FAQ has the output of an older version and is less
verbose. 'E' means event.

Wim

>
>
>
> :~$ gst-launch -v fakesrc num-buffers=3 ! fakesink
> Setting pipeline to PAUSED ...
> Pipeline is PREROLLING ...
> /pipeline0/fakesrc0: last-message = "get      ******* > (    0 bytes,
> timestamp: none, duration: none, offset: 0, offset_end: -1, flags: 0)
> 0x80c9a90"
> /pipeline0/fakesink0: last-message = "preroll   ******* "
> Pipeline is PREROLLED ...
> /pipeline0/fakesink0: last-message = "event   ******* E (type: 102,
> GstEventNewsegment, update=(boolean)false, rate=(double)1,
> applied_rate=(double)1, format=(GstFormat)GST_FORMAT_BYTES,
> start=(gint64)0, stop=(gint64)-1, position=(gint64)0;) 0x8053cc8"
> Setting pipeline to PLAYING ...
> /pipeline0/fakesink0: last-message = "chain   ******* < (    0 bytes,
> timestamp: 0:00:00.000000000, duration: none, offset: 0, offset_end:
> -1, flags: 32) 0x80c9a90"
> New clock: GstSystemClock
> /pipeline0/fakesrc0: last-message = "get      ******* > (    0 bytes,
> timestamp: none, duration: none, offset: 1, offset_end: -1, flags: 0)
> 0x80c9ae0"
> /pipeline0/fakesink0: last-message = "chain   ******* < (    0 bytes,
> timestamp: 0:00:00.000000000, duration: none, offset: 1, offset_end:
> -1, flags: 0) 0x80c9ae0"
> /pipeline0/fakesrc0: last-message = "get      ******* > (    0 bytes,
> timestamp: none, duration: none, offset: 2, offset_end: -1, flags: 0)
> 0x80c9b30"
> /pipeline0/fakesink0: last-message = "chain   ******* < (    0 bytes,
> timestamp: 0:00:00.000000000, duration: none, offset: 2, offset_end:
> -1, flags: 0) 0x80c9b30"
> /pipeline0/fakesink0: last-message = "event   ******* E (type: 86, )
> 0x8053cc8"
> Got EOS from element "pipeline0".
> Execution ended after 1044000 ns.
> Setting pipeline to PAUSED ...
> Setting pipeline to READY ...
> Setting pipeline to NULL ...
> FREEING pipeline ...
>
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
Reply | Threaded
Open this post in threaded view
|

Re: n00b question: Does this fakesrc output look ok?

Wim Taymans

On Fri, 2008-02-22 at 11:37 +0200, Topi Hukkanen wrote:

> Damn reply to all button....
>
> Sorry for the noobspam, but if I run the example:
>
> gst-launch audiotestsrc ! audioconvert ! audioresample ! osssink
>
> I get the dialtone and all looks well...  but is Ctrl-C the proper way
> to "stop" the program?  I was doing this for webcam examples also, and
> I'm not sure if there's a "cleaner" way.
>
>
Yes, it's the only way to stop gst-launch. It's however not the cleanest
way (muxers might not properly finish the output file). Remember that
gst-launch is a quick testing tool. If you write an application you
likely will use the gstreamer API to properly shut down pipelines.

Wim

>
>
>
>
>
>
>
>
>
> On Fri, Feb 22, 2008 at 11:27 AM, Wim Taymans <[hidden email]>
> wrote:
>        
>         On Fri, 2008-02-22 at 11:20 +0200, Topi Hukkanen wrote:
>         > This doesn't quite look like the output from the FAQ.  I am
>         getting an
>         > EOS (end of stream?) from the pipeline.  Does this mean
>         something is
>         > wrong, or is it normal?  Also, this "E" message, is that an
>         Error?
>        
>        
>         It's normal, the FAQ has the output of an older version and is
>         less
>         verbose. 'E' means event.
>        
>         Wim
>        
>        
>         >
>         >
>         >
>         > :~$ gst-launch -v fakesrc num-buffers=3 ! fakesink
>         > Setting pipeline to PAUSED ...
>         > Pipeline is PREROLLING ...
>         > /pipeline0/fakesrc0: last-message = "get      ******* > (
>          0 bytes,
>         > timestamp: none, duration: none, offset: 0, offset_end: -1,
>         flags: 0)
>         > 0x80c9a90"
>         > /pipeline0/fakesink0: last-message = "preroll   ******* "
>         > Pipeline is PREROLLED ...
>         > /pipeline0/fakesink0: last-message = "event   ******* E
>         (type: 102,
>         > GstEventNewsegment, update=(boolean)false, rate=(double)1,
>         > applied_rate=(double)1, format=(GstFormat)GST_FORMAT_BYTES,
>         > start=(gint64)0, stop=(gint64)-1, position=(gint64)0;)
>         0x8053cc8"
>         > Setting pipeline to PLAYING ...
>         > /pipeline0/fakesink0: last-message = "chain   ******* < (
>          0 bytes,
>         > timestamp: 0:00:00.000000000, duration: none, offset: 0,
>         offset_end:
>         > -1, flags: 32) 0x80c9a90"
>         > New clock: GstSystemClock
>         > /pipeline0/fakesrc0: last-message = "get      ******* > (
>          0 bytes,
>         > timestamp: none, duration: none, offset: 1, offset_end: -1,
>         flags: 0)
>         > 0x80c9ae0"
>         > /pipeline0/fakesink0: last-message = "chain   ******* < (
>          0 bytes,
>         > timestamp: 0:00:00.000000000, duration: none, offset: 1,
>         offset_end:
>         > -1, flags: 0) 0x80c9ae0"
>         > /pipeline0/fakesrc0: last-message = "get      ******* > (
>          0 bytes,
>         > timestamp: none, duration: none, offset: 2, offset_end: -1,
>         flags: 0)
>         > 0x80c9b30"
>         > /pipeline0/fakesink0: last-message = "chain   ******* < (
>          0 bytes,
>         > timestamp: 0:00:00.000000000, duration: none, offset: 2,
>         offset_end:
>         > -1, flags: 0) 0x80c9b30"
>         > /pipeline0/fakesink0: last-message = "event   ******* E
>         (type: 86, )
>         > 0x8053cc8"
>         > Got EOS from element "pipeline0".
>         > Execution ended after 1044000 ns.
>         > Setting pipeline to PAUSED ...
>         > Setting pipeline to READY ...
>         > Setting pipeline to NULL ...
>         > FREEING pipeline ...
>         >
>         >
>         >
>         >
>        
>         >
>         -------------------------------------------------------------------------
>         > This SF.net email is sponsored by: Microsoft
>         > Defy all challenges. Microsoft(R) Visual Studio 2008.
>         > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>         > _______________________________________________
>         gstreamer-devel mailing list
>         [hidden email]
>         https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
>        
>


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel