GST_FLOW_WRONG_STATE
Locked
 
|
Hello,
I have a video sink and ALSA driver to be used to play videos on the platform. If I play video or audio by them self everything works fine, but if I specify the whole pipeline for video and audio, the video decoder (in pipeline right before the sink) comes back with the message: "The decoded frame did not successfully push out to downstream element" The message comes because the gst_pad_push have returned with GST_FLOW_WRONG_STATE instead GST_FLOW_OK. Any idea why this might happen? ------------------------------------------------------------------------------ This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
Re: GST_FLOW_WRONG_STATE
|
|
On Wed, 2010-12-08 at 12:53 -0800, Radivoje Jovanovic wrote:
> I have a video sink and ALSA driver to be used to play videos on the > platform. If I play video or audio by them self everything works fine, > but if I specify the whole pipeline for video and audio, the video > decoder (in pipeline right before the sink) comes back with the > message: > "The decoded frame did not successfully push out to downstream > element" > The message comes because the gst_pad_push have returned with > GST_FLOW_WRONG_STATE instead GST_FLOW_OK. > > Any idea why this might happen? It usually helps if you post your exact pipeline and/or any code snippets that go with it. FLOW_WRONG_STATE is what you get when a pad is flushing, which may be normal (happens during a flushing seek, to make the old streaming thread stop) or because you forgot to set an element into PAUSED/PLAYING state (e.g. because you added it from a pad-added or new-decoded-pad callback or so). The GST_DEBUG=*:5 log might give you more information (just grep for wrong-state and read the lines before that). Cheers -Tim ------------------------------------------------------------------------------ This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
|
|
So the pipeline I am using is:
gst-launch-0.10 filesrc location=MY_MOVIE ! qtdemux name=t ! queue ! mpeg4dec ! MY_VIDEO_SINK t. ! queue ! faad ! alsasink This pipeline will hang and after CTRL-C the mpeg4dec will show the message that is the result of calling gst_push_pad. This gst_push_pad will return GST_FLOW_WRONG_STATE. If I run gst-launch-0.10 filesrc location=MY_MOVIE ! qtdemux name=t ! queue ! mpeg4dec ! MY_VIDEO_SINK the video will play just fine If I run: gst-launch-0.10 filesrc location=MY_MOVIE ! qtdemux name=t ! queue ! faad ! alsasink the audio from the audio will play just fine. I am not sure which code would be helpful since I have a lot of it. Thanks for the GST_DEBUG info. Ogi On Wed, Dec 8, 2010 at 4:05 PM, Tim-Philipp Müller <[hidden email]> wrote:
------------------------------------------------------------------------------ This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
|
|
On Thu, Dec 9, 2010 at 6:26 AM, Radivoje Jovanovic
<[hidden email]> wrote: > So the pipeline I am using is: > gst-launch-0.10 filesrc location=MY_MOVIE ! qtdemux name=t ! queue ! > mpeg4dec ! MY_VIDEO_SINK t. ! queue ! faad ! alsasink > This pipeline will hang and after CTRL-C the mpeg4dec will show the message > that is the result of calling gst_push_pad. This gst_push_pad will return > GST_FLOW_WRONG_STATE. > > If I run gst-launch-0.10 filesrc location=MY_MOVIE ! qtdemux name=t ! queue > ! mpeg4dec ! MY_VIDEO_SINK > the video will play just fine > > If I run: > gst-launch-0.10 filesrc location=MY_MOVIE ! qtdemux name=t ! queue ! faad ! > alsasink > the audio from the audio will play just fine. > > I am not sure which code would be helpful since I have a lot of it. > Thanks for the GST_DEBUG info. > > Ogi > > > On Wed, Dec 8, 2010 at 4:05 PM, Tim-Philipp Müller <[hidden email]> wrote: >> >> On Wed, 2010-12-08 at 12:53 -0800, Radivoje Jovanovic wrote: >> >> > I have a video sink and ALSA driver to be used to play videos on the >> > platform. If I play video or audio by them self everything works fine, >> > but if I specify the whole pipeline for video and audio, the video >> > decoder (in pipeline right before the sink) comes back with the >> > message: >> > "The decoded frame did not successfully push out to downstream >> > element" >> > The message comes because the gst_pad_push have returned with >> > GST_FLOW_WRONG_STATE instead GST_FLOW_OK. >> > >> > Any idea why this might happen? >> >> It usually helps if you post your exact pipeline and/or any code >> snippets that go with it. >> >> FLOW_WRONG_STATE is what you get when a pad is flushing, which may be >> normal (happens during a flushing seek, to make the old streaming thread >> stop) or because you forgot to set an element into PAUSED/PLAYING state >> (e.g. because you added it from a pad-added or new-decoded-pad callback >> or so). >> >> The GST_DEBUG=*:5 log might give you more information (just grep for >> wrong-state and read the lines before that). >> >> Cheers >> -Tim >> >> >> >> >> ------------------------------------------------------------------------------ >> This SF Dev2Dev email is sponsored by: >> >> WikiLeaks The End of the Free Internet >> http://p.sf.net/sfu/therealnews-com >> _______________________________________________ >> gstreamer-devel mailing list >> [hidden email] >> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel > > > ------------------------------------------------------------------------------ > This SF Dev2Dev email is sponsored by: > > WikiLeaks The End of the Free Internet > http://p.sf.net/sfu/therealnews-com > _______________________________________________ > gstreamer-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/gstreamer-devel > > ------------------------------------------------------------------------------ This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
|
|
Hi,
One possible reason could be that one of the queues is getting full while the other remains empty because of (a) continuous audio/video buffers for a considerably longer time, longer than the what the queues can hold. (b) high latency at the your video decoder (mpeg4dec). Hence the streaming thread is blocked & one of the sinks is not able to commit the state to PAUSED. (because it has not received a buffer yet). Yo can also set async=FALSE on the sinks and see. (not recommended) You can try disabling the the max time & max bytes properties of the queue. Try the following pipeline gst-launch-0.10 filesrc location=MY_MOVIE ! qtdemux name=t ! queue max-size-time=0 max-size-bytes=0 ! mpeg4dec ! MY_VIDEO_SINK t. ! queue max-size-time=0 max-size-bytes=0 ! faad ! alsasink -v Note that this will increase the mem usage.. and even more if u set max-size-buffers=0 as well. (queue without any limits!) Vikram On Thu, Dec 9, 2010 at 9:44 AM, ved kpl <[hidden email]> wrote: > On Thu, Dec 9, 2010 at 6:26 AM, Radivoje Jovanovic > <[hidden email]> wrote: >> So the pipeline I am using is: >> gst-launch-0.10 filesrc location=MY_MOVIE ! qtdemux name=t ! queue ! >> mpeg4dec ! MY_VIDEO_SINK t. ! queue ! faad ! alsasink >> This pipeline will hang and after CTRL-C the mpeg4dec will show the message >> that is the result of calling gst_push_pad. This gst_push_pad will return >> GST_FLOW_WRONG_STATE. >> >> If I run gst-launch-0.10 filesrc location=MY_MOVIE ! qtdemux name=t ! queue >> ! mpeg4dec ! MY_VIDEO_SINK >> the video will play just fine >> >> If I run: >> gst-launch-0.10 filesrc location=MY_MOVIE ! qtdemux name=t ! queue ! faad ! >> alsasink >> the audio from the audio will play just fine. >> >> I am not sure which code would be helpful since I have a lot of it. >> Thanks for the GST_DEBUG info. >> >> Ogi >> >> >> On Wed, Dec 8, 2010 at 4:05 PM, Tim-Philipp Müller <[hidden email]> wrote: >>> >>> On Wed, 2010-12-08 at 12:53 -0800, Radivoje Jovanovic wrote: >>> >>> > I have a video sink and ALSA driver to be used to play videos on the >>> > platform. If I play video or audio by them self everything works fine, >>> > but if I specify the whole pipeline for video and audio, the video >>> > decoder (in pipeline right before the sink) comes back with the >>> > message: >>> > "The decoded frame did not successfully push out to downstream >>> > element" >>> > The message comes because the gst_pad_push have returned with >>> > GST_FLOW_WRONG_STATE instead GST_FLOW_OK. >>> > >>> > Any idea why this might happen? >>> >>> It usually helps if you post your exact pipeline and/or any code >>> snippets that go with it. >>> >>> FLOW_WRONG_STATE is what you get when a pad is flushing, which may be >>> normal (happens during a flushing seek, to make the old streaming thread >>> stop) or because you forgot to set an element into PAUSED/PLAYING state >>> (e.g. because you added it from a pad-added or new-decoded-pad callback >>> or so). >>> >>> The GST_DEBUG=*:5 log might give you more information (just grep for >>> wrong-state and read the lines before that). >>> >>> Cheers >>> -Tim >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> This SF Dev2Dev email is sponsored by: >>> >>> WikiLeaks The End of the Free Internet >>> http://p.sf.net/sfu/therealnews-com >>> _______________________________________________ >>> gstreamer-devel mailing list >>> [hidden email] >>> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel >> >> >> ------------------------------------------------------------------------------ >> This SF Dev2Dev email is sponsored by: >> >> WikiLeaks The End of the Free Internet >> http://p.sf.net/sfu/therealnews-com >> _______________________________________________ >> gstreamer-devel mailing list >> [hidden email] >> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel >> >> > ------------------------------------------------------------------------------ This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
|
|
It seems like we are on a good path. after I tried the pipeline:
gst-launch-0.10 filesrc location=MY_MOVIE ! qtdemux name=t ! queue max-size-time=0 max-size-bytes=0 ! mpeg4dec ! MY_VIDEO_SINK t. ! queue ! faad ! alsasink (so I only give time and bytes for video side) the video and audio worked just fine. Unfortunately this trick does not work for the other decoder I have which decodes h264 videos. Even with the pipeline: gst-launch-0.10 filesrc location=MY_MOVIE ! qtdemux name=t ! queue max-size-time=0 max-size-bytes=0 ! h264dec ! MY_VIDEO_SINK t. ! queue ! faad ! alsasink The pipeline is stuck. This all has nothing to do with GST_FLOW_WRONG_STATE since this error pops up all the time after CTRL-C operation. Any idea why would h264 get stuck? Another question is if I am giving too much memory to gstreamer with max-size-time=0 max-size-bytes=0? Cheers Ogi On Wed, Dec 8, 2010 at 8:27 PM, ved kpl <[hidden email]> wrote: Hi, ------------------------------------------------------------------------------ _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
|
|
On Fri, Dec 10, 2010 at 1:39 AM, Radivoje Jovanovic
<[hidden email]> wrote: > It seems like we are on a good path. after I tried the pipeline: > gst-launch-0.10 filesrc location=MY_MOVIE ! qtdemux name=t ! queue > max-size-time=0 max-size-bytes=0 ! mpeg4dec ! MY_VIDEO_SINK t. ! queue > ! faad ! alsasink > (so I only give time and bytes for video side) the video and audio worked > just fine. > > Unfortunately this trick does not work for the other decoder I have which > decodes h264 videos. > > Even with the pipeline: > gst-launch-0.10 filesrc location=MY_MOVIE ! qtdemux name=t ! queue > max-size-time=0 max-size-bytes=0 ! h264dec ! MY_VIDEO_SINK t. ! queue > ! faad ! alsasink > The pipeline is stuck. This all has nothing to do with GST_FLOW_WRONG_STATE > since this error pops up all the time after CTRL-C operation. Any idea why > would h264 get stuck? To start off, try setting max-size-time/bytes/buffers=0 on the both the queues (no limits) If it works, it indicates that your h264dec has a very high latency..and you can narrow to the problem from here. > Another question is if I am giving too much memory to gstreamer with > max-size-time=0 max-size-bytes=0? Well, It would depend on your codec details (resilution, etc), environment/platform. You could possibly track down the issue. > Cheers > Ogi > > > On Wed, Dec 8, 2010 at 8:27 PM, ved kpl <[hidden email]> wrote: >> >> Hi, >> >> One possible reason could be that one of the queues is getting full >> while the other remains empty >> because of >> (a) continuous audio/video buffers for a considerably longer time, >> longer than the what the queues can hold. >> (b) high latency at the your video decoder (mpeg4dec). >> Hence the streaming thread is blocked & one of the sinks is not able >> to commit the state to PAUSED. >> (because it has not received a buffer yet). >> >> Yo can also set async=FALSE on the sinks and see. (not recommended) >> >> You can try disabling the the max time & max bytes properties of the >> queue. >> Try the following pipeline >> >> gst-launch-0.10 filesrc location=MY_MOVIE ! qtdemux name=t ! queue >> max-size-time=0 max-size-bytes=0 ! mpeg4dec ! MY_VIDEO_SINK t. ! queue >> max-size-time=0 max-size-bytes=0 ! faad ! alsasink -v >> >> Note that this will increase the mem usage.. and even more if u set >> max-size-buffers=0 as well. (queue without any limits!) >> >> Vikram >> >> On Thu, Dec 9, 2010 at 9:44 AM, ved kpl <[hidden email]> wrote: >> > On Thu, Dec 9, 2010 at 6:26 AM, Radivoje Jovanovic >> > <[hidden email]> wrote: >> >> So the pipeline I am using is: >> >> gst-launch-0.10 filesrc location=MY_MOVIE ! qtdemux name=t ! queue ! >> >> mpeg4dec ! MY_VIDEO_SINK t. ! queue ! faad ! alsasink >> >> This pipeline will hang and after CTRL-C the mpeg4dec will show the >> >> message >> >> that is the result of calling gst_push_pad. This gst_push_pad will >> >> return >> >> GST_FLOW_WRONG_STATE. >> >> >> >> If I run gst-launch-0.10 filesrc location=MY_MOVIE ! qtdemux name=t ! >> >> queue >> >> ! mpeg4dec ! MY_VIDEO_SINK >> >> the video will play just fine >> >> >> >> If I run: >> >> gst-launch-0.10 filesrc location=MY_MOVIE ! qtdemux name=t ! queue ! >> >> faad ! >> >> alsasink >> >> the audio from the audio will play just fine. >> >> >> >> I am not sure which code would be helpful since I have a lot of it. >> >> Thanks for the GST_DEBUG info. >> >> >> >> Ogi >> >> >> >> >> >> On Wed, Dec 8, 2010 at 4:05 PM, Tim-Philipp Müller <[hidden email]> >> >> wrote: >> >>> >> >>> On Wed, 2010-12-08 at 12:53 -0800, Radivoje Jovanovic wrote: >> >>> >> >>> > I have a video sink and ALSA driver to be used to play videos on the >> >>> > platform. If I play video or audio by them self everything works >> >>> > fine, >> >>> > but if I specify the whole pipeline for video and audio, the video >> >>> > decoder (in pipeline right before the sink) comes back with the >> >>> > message: >> >>> > "The decoded frame did not successfully push out to downstream >> >>> > element" >> >>> > The message comes because the gst_pad_push have returned with >> >>> > GST_FLOW_WRONG_STATE instead GST_FLOW_OK. >> >>> > >> >>> > Any idea why this might happen? >> >>> >> >>> It usually helps if you post your exact pipeline and/or any code >> >>> snippets that go with it. >> >>> >> >>> FLOW_WRONG_STATE is what you get when a pad is flushing, which may be >> >>> normal (happens during a flushing seek, to make the old streaming >> >>> thread >> >>> stop) or because you forgot to set an element into PAUSED/PLAYING >> >>> state >> >>> (e.g. because you added it from a pad-added or new-decoded-pad >> >>> callback >> >>> or so). >> >>> >> >>> The GST_DEBUG=*:5 log might give you more information (just grep for >> >>> wrong-state and read the lines before that). >> >>> >> >>> Cheers >> >>> -Tim >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> ------------------------------------------------------------------------------ >> >>> This SF Dev2Dev email is sponsored by: >> >>> >> >>> WikiLeaks The End of the Free Internet >> >>> http://p.sf.net/sfu/therealnews-com >> >>> _______________________________________________ >> >>> gstreamer-devel mailing list >> >>> [hidden email] >> >>> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel >> >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> >> This SF Dev2Dev email is sponsored by: >> >> >> >> WikiLeaks The End of the Free Internet >> >> http://p.sf.net/sfu/therealnews-com >> >> _______________________________________________ >> >> gstreamer-devel mailing list >> >> [hidden email] >> >> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel >> >> >> >> >> > >> >> >> ------------------------------------------------------------------------------ >> This SF Dev2Dev email is sponsored by: >> >> WikiLeaks The End of the Free Internet >> http://p.sf.net/sfu/therealnews-com >> _______________________________________________ >> gstreamer-devel mailing list >> [hidden email] >> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel > > > ------------------------------------------------------------------------------ > > _______________________________________________ > gstreamer-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/gstreamer-devel > > ------------------------------------------------------------------------------ _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
|
|
Thank you for all of your input. Unfortunately I did not write the decoders at all, but I do have the source code. What is considered as decoder latency? Is it the time for decoder to set up or something else?
Cheers Ogi On Thu, Dec 9, 2010 at 7:45 PM, ved kpl <[hidden email]> wrote:
------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
|
|
It is the time taken taken for a input 'X' at the decoder
to appear as the decoded output, which possibly could involve the startup latency as well,. depends on your implementation. (in READY->PAUSED). On Wed, Dec 15, 2010 at 2:52 AM, Radivoje Jovanovic <[hidden email]> wrote: > Thank you for all of your input. Unfortunately I did not write the decoders > at all, but I do have the source code. What is considered as decoder > latency? Is it the time for decoder to set up or something else? > Cheers > Ogi > > On Thu, Dec 9, 2010 at 7:45 PM, ved kpl <[hidden email]> wrote: >> >> On Fri, Dec 10, 2010 at 1:39 AM, Radivoje Jovanovic >> <[hidden email]> wrote: >> > It seems like we are on a good path. after I tried the pipeline: >> > gst-launch-0.10 filesrc location=MY_MOVIE ! qtdemux name=t ! queue >> > max-size-time=0 max-size-bytes=0 ! mpeg4dec ! MY_VIDEO_SINK t. ! queue >> > ! faad ! alsasink >> > (so I only give time and bytes for video side) the video and audio >> > worked >> > just fine. >> > >> > Unfortunately this trick does not work for the other decoder I have >> > which >> > decodes h264 videos. >> > >> > Even with the pipeline: >> > gst-launch-0.10 filesrc location=MY_MOVIE ! qtdemux name=t ! queue >> > max-size-time=0 max-size-bytes=0 ! h264dec ! MY_VIDEO_SINK t. ! queue >> > ! faad ! alsasink >> > The pipeline is stuck. This all has nothing to do with >> > GST_FLOW_WRONG_STATE >> > since this error pops up all the time after CTRL-C operation. Any idea >> > why >> > would h264 get stuck? >> >> To start off, try setting max-size-time/bytes/buffers=0 on the both >> the queues (no limits) >> If it works, it indicates that your h264dec has a very high >> latency..and you can >> narrow to the problem from here. >> >> > Another question is if I am giving too much memory to gstreamer with >> > max-size-time=0 max-size-bytes=0? >> >> Well, It would depend on your codec details (resilution, etc), >> environment/platform. You could possibly track down the issue. >> >> > Cheers >> > Ogi >> > >> > >> > On Wed, Dec 8, 2010 at 8:27 PM, ved kpl <[hidden email]> wrote: >> >> >> >> Hi, >> >> >> >> One possible reason could be that one of the queues is getting full >> >> while the other remains empty >> >> because of >> >> (a) continuous audio/video buffers for a considerably longer time, >> >> longer than the what the queues can hold. >> >> (b) high latency at the your video decoder (mpeg4dec). >> >> Hence the streaming thread is blocked & one of the sinks is not able >> >> to commit the state to PAUSED. >> >> (because it has not received a buffer yet). >> >> >> >> Yo can also set async=FALSE on the sinks and see. (not recommended) >> >> >> >> You can try disabling the the max time & max bytes properties of the >> >> queue. >> >> Try the following pipeline >> >> >> >> gst-launch-0.10 filesrc location=MY_MOVIE ! qtdemux name=t ! queue >> >> max-size-time=0 max-size-bytes=0 ! mpeg4dec ! MY_VIDEO_SINK t. ! queue >> >> max-size-time=0 max-size-bytes=0 ! faad ! alsasink -v >> >> >> >> Note that this will increase the mem usage.. and even more if u set >> >> max-size-buffers=0 as well. (queue without any limits!) >> >> >> >> Vikram >> >> >> >> On Thu, Dec 9, 2010 at 9:44 AM, ved kpl <[hidden email]> wrote: >> >> > On Thu, Dec 9, 2010 at 6:26 AM, Radivoje Jovanovic >> >> > <[hidden email]> wrote: >> >> >> So the pipeline I am using is: >> >> >> gst-launch-0.10 filesrc location=MY_MOVIE ! qtdemux name=t ! queue >> >> >> ! >> >> >> mpeg4dec ! MY_VIDEO_SINK t. ! queue ! faad ! alsasink >> >> >> This pipeline will hang and after CTRL-C the mpeg4dec will show the >> >> >> message >> >> >> that is the result of calling gst_push_pad. This gst_push_pad will >> >> >> return >> >> >> GST_FLOW_WRONG_STATE. >> >> >> >> >> >> If I run gst-launch-0.10 filesrc location=MY_MOVIE ! qtdemux name=t >> >> >> ! >> >> >> queue >> >> >> ! mpeg4dec ! MY_VIDEO_SINK >> >> >> the video will play just fine >> >> >> >> >> >> If I run: >> >> >> gst-launch-0.10 filesrc location=MY_MOVIE ! qtdemux name=t ! queue ! >> >> >> faad ! >> >> >> alsasink >> >> >> the audio from the audio will play just fine. >> >> >> >> >> >> I am not sure which code would be helpful since I have a lot of it. >> >> >> Thanks for the GST_DEBUG info. >> >> >> >> >> >> Ogi >> >> >> >> >> >> >> >> >> On Wed, Dec 8, 2010 at 4:05 PM, Tim-Philipp Müller <[hidden email]> >> >> >> wrote: >> >> >>> >> >> >>> On Wed, 2010-12-08 at 12:53 -0800, Radivoje Jovanovic wrote: >> >> >>> >> >> >>> > I have a video sink and ALSA driver to be used to play videos on >> >> >>> > the >> >> >>> > platform. If I play video or audio by them self everything works >> >> >>> > fine, >> >> >>> > but if I specify the whole pipeline for video and audio, the >> >> >>> > video >> >> >>> > decoder (in pipeline right before the sink) comes back with the >> >> >>> > message: >> >> >>> > "The decoded frame did not successfully push out to downstream >> >> >>> > element" >> >> >>> > The message comes because the gst_pad_push have returned with >> >> >>> > GST_FLOW_WRONG_STATE instead GST_FLOW_OK. >> >> >>> > >> >> >>> > Any idea why this might happen? >> >> >>> >> >> >>> It usually helps if you post your exact pipeline and/or any code >> >> >>> snippets that go with it. >> >> >>> >> >> >>> FLOW_WRONG_STATE is what you get when a pad is flushing, which may >> >> >>> be >> >> >>> normal (happens during a flushing seek, to make the old streaming >> >> >>> thread >> >> >>> stop) or because you forgot to set an element into PAUSED/PLAYING >> >> >>> state >> >> >>> (e.g. because you added it from a pad-added or new-decoded-pad >> >> >>> callback >> >> >>> or so). >> >> >>> >> >> >>> The GST_DEBUG=*:5 log might give you more information (just grep >> >> >>> for >> >> >>> wrong-state and read the lines before that). >> >> >>> >> >> >>> Cheers >> >> >>> -Tim >> >> >>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> ------------------------------------------------------------------------------ >> >> >>> This SF Dev2Dev email is sponsored by: >> >> >>> >> >> >>> WikiLeaks The End of the Free Internet >> >> >>> http://p.sf.net/sfu/therealnews-com >> >> >>> _______________________________________________ >> >> >>> gstreamer-devel mailing list >> >> >>> [hidden email] >> >> >>> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> >> >> This SF Dev2Dev email is sponsored by: >> >> >> >> >> >> WikiLeaks The End of the Free Internet >> >> >> http://p.sf.net/sfu/therealnews-com >> >> >> _______________________________________________ >> >> >> gstreamer-devel mailing list >> >> >> [hidden email] >> >> >> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> >> This SF Dev2Dev email is sponsored by: >> >> >> >> WikiLeaks The End of the Free Internet >> >> http://p.sf.net/sfu/therealnews-com >> >> _______________________________________________ >> >> gstreamer-devel mailing list >> >> [hidden email] >> >> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel >> > >> > >> > >> > ------------------------------------------------------------------------------ >> > >> > _______________________________________________ >> > gstreamer-devel mailing list >> > [hidden email] >> > https://lists.sourceforge.net/lists/listinfo/gstreamer-devel >> > >> > >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> gstreamer-devel mailing list >> [hidden email] >> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel > > > ------------------------------------------------------------------------------ > Lotusphere 2011 > Register now for Lotusphere 2011 and learn how > to connect the dots, take your collaborative environment > to the next level, and enter the era of Social Business. > http://p.sf.net/sfu/lotusphere-d2d > _______________________________________________ > gstreamer-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/gstreamer-devel > > ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
«
Return to GStreamer-devel
|
1 view|%1 views
| Free forum by Nabble | Edit this page |