Hi all, Perhaps someone can explain to me what might be happening for me. I've been successfully using a pipeline, such as the following gst-launch equivalent, on my own development machine (32 bit linux, ubuntu hardy): > gst-launch-0.10 uridecodebin uri=rtsp://some_mp4v_encoded_source ! queue ! decodebin2 ! xvimagesink However, when it came time to deploy my code on to a test machine (64 bit linux, ubuntu hardy, all relevant packages are the same versions, as far as I can tell), it was found that playback was far from good - very stuttered, missing/corrupted frames etc. I was playing around with a few of the element properties, and discovered that setting the "sync" property to false (default is "true) fixed my problem - i.e. it resulted in smooth playback. Now, the doco from BaseSink says: "sync" - Sync on the clock. Well it might be obvious to some, but I'm not sure why the behaviour would be different on the two different machines. Which element would be providing the clock in the above pipelines (I think the uridecodebin and decodebin2 elements "resolve" to something like rtpmp4vdepay ! ffdec_mpeg4)? Does turning sink off just result in the sink rendering it as soon as it gets data? Cheers, Jono