How to avoid locking during changing state of element?

[박성호]

Hi Experts,

I made a demuxing element for test.
But it is very similar with ffmpeg's.
It works nice in pull mode.
However in push mode (i.e. streaming like dlna), it hangs at changing state
PAUSED to READY.
Hanging occurs only at middle of contents.
After end of content, normally changed.

This is the last log with --gst-debug=GST_STATES:5
==============================================================
LOG               GST_STATES
gstelement.c:2942:gst_element_change_state_func:<seonghotsdemuxer0> default
handler tries setting state from PAUSED to READY (001a)
==============================================================

Because of my poor googling ability, I didn't find solution to avoid this.
I just heard "Use new progress message api" "Use asynchronous state
changing" and "Improve your element".

I need more information with regard to changing state.
Anything, thanks.

Best regards.
Seongho.

_______________________________________________
gstreamer-devel mailing list
[hidden email]
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[박성호]

Please never mind my question.
It is just my mistake.
Thanks.


Best regards.
 
Seongho, Park.

> -----Original Message-----
> From: gstreamer-devel-bounces+pncc=[hidden email]
> [mailto:gstreamer-devel-bounces+pncc=[hidden email]] On
> Behalf Of 박성호
> Sent: Tuesday, December 06, 2011 4:40 PM
> To: [hidden email]
> Subject: How to avoid locking during changing state of element?
>
> Hi Experts,
>
> I made a demuxing element for test.
> But it is very similar with ffmpeg's.
> It works nice in pull mode.
> However in push mode (i.e. streaming like dlna), it hangs at changing

state

> PAUSED to READY.
> Hanging occurs only at middle of contents.
> After end of content, normally changed.
>
> This is the last log with --gst-debug=GST_STATES:5
> ============================================================
> ==
> LOG               GST_STATES
> gstelement.c:2942:gst_element_change_state_func:<seonghotsdemuxer0>
> default
> handler tries setting state from PAUSED to READY (001a)
> ============================================================
> ==
>
> Because of my poor googling ability, I didn't find solution to avoid this.
> I just heard "Use new progress message api" "Use asynchronous state
> changing" and "Improve your element".
>
> I need more information with regard to changing state.
> Anything, thanks.
>
> Best regards.
> Seongho.
>
> _______________________________________________
> gstreamer-devel mailing list
> [hidden email]
> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

_______________________________________________
gstreamer-devel mailing list
[hidden email]
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[Dan_U]

Hi Seongho,

I am having the exact same issue (from PAUSED to READY). Instead of your
demuxer, for me it happens with <source> currently using filesrc.
What was the mistake you found there and how did you solve it?

Regards,
Daniel



--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel