Understanding QOS in gstreamer

[Baby Octopus]

Hi,

I'm using gstreamer 1.4.4. By any chance do you feel this could have been
fixed in git master? Just asking. Here is more detailed print from the
console. The system shows a load of 25% with 5% memory used(out of 4GB)

[root at localhost gst-plugins-good-1.4.4]# gst-launch-1.0 videotestsrc
is-live=1 ! videoscale qos=1 ! video/x-raw,width=32000,height=2160 !
checksumsink qos=1 sync=1  
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
PTS: 0:00:00.252750378  DTS: 0:00:00.252750378
PTS: 0:00:00.286083711  DTS: 0:00:00.286083711
PTS: 0:00:00.519417044  DTS: 0:00:00.519417044
PTS: 0:00:02.219417044  DTS: 0:00:02.219417044
^Chandling interrupt.
Interrupt: Stopping pipeline ...
Execution ended after 0:00:18.569766699
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
Freeing pipeline ...





--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/Understanding-QOS-in-gstreamer-tp4672096p4672102.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.