shmsink changes from 1.0.10 to 1.1.4

[Olivier Crête]

Hi,

On Wed, 2013-09-18 at 22:03 +0200, Peter Maersk-Moller wrote:

> It turns out that GStreamer 1.1.4 is a bit more pedantic about timing
> compared to 1.0.x and 0.10. The following pipeline will use the shared
> memory area and then freeze in 1.1.4 while working in 1.0.x and 0.10
> 
> gst-launch-1.0 -v videotestsrc is-live=true ! $RAWVIDEO ! queue !
> identity ! shmsink socket-path=/tmp/feed1-control-pipe
> shm-size=20000000 wait-for-connection=0 sync=true
> 
> 
> However if you add 'do-timestamp=true' to videotestsrc, it will flow
> again, also in 1.1.4.
> 
> gst-launch-1.0 -v videotestsrc is-live=true do-timestamp=true !
> $RAWVIDEO ! queue ! identity ! shmsink
> socket-path=/tmp/feed1-control-pipe shm-size=20000000
> wait-for-connection=0 sync=true

I'm curious to know how your pipeline is different from these ones which
work fine for me using git master:

gst-launch-1.0 -v videotestsrc ! 'video/x-raw, format=(string)I420,
width=(int)320, height=(int)240, framerate=(fraction)30/1' ! queue !
identity ! shmsink wait-for-connection=1 socket-path=/tmp/tmpsock
shm-size=20000000 sync=true

gst-launch-1.0 shmsrc socket-path=/tmp/tmpsock ! 'video/x-raw,
format=(string)I420, width=(int)320, height=(int)240,
framerate=(fraction)30/1' ! xvimagesink


-- 
Olivier Crête
olivier.crete at collabora.com