[Bug 693037] New: ximagesrc works poorly when using DAMAGE

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=693037
  GStreamer | gst-plugins-good | 1.0.3

           Summary: ximagesrc works poorly when using DAMAGE
    Classification: Platform
           Product: GStreamer
           Version: 1.0.3
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: swestrup at gmail.com
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


ximagesrc has a feature where it will use the X Damage feature to only send
updates for changed parts of the screen, rather than entire screens. However,
when using damage, performance as a whole degrades badly, rather than
improving.

This pipeline can easily handle 25 frames-per-second of updates on my system:

gst-launch-1.0 ximagesrc display-name=:1 use-damage=false ! videoconvert !
'video/x-raw,pixel-aspect-ratio=(fraction)1/1' ! videorate ! xvimagesink
display=:2

However, if one removes the 'use-damage=false' clause to permit ximagesrc to
'optimize' buffers, then one quickly gets results like this:

$ gst-launch-1.0 ximagesrc display-name=:1  ! videoconvert !
'video/x-raw,pixel-aspect-ratio=(fraction)1/1' ! videorate ! xvimagesink
display=:2
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
WARNING: from element /GstPipeline:pipeline0/GstXvImageSink:xvimagesink0: A lot
of buffers are being dropped.
Additional debug info:
gstbasesink.c(2675): gst_base_sink_is_too_late ():
/GstPipeline:pipeline0/GstXvImageSink:xvimagesink0:
There may be a timestamping problem, or this computer is too slow.
WARNING: from element /GstPipeline:pipeline0/GstXvImageSink:xvimagesink0: A lot
of buffers are being dropped.
Additional debug info:
gstbasesink.c(2675): gst_base_sink_is_too_late ():
/GstPipeline:pipeline0/GstXvImageSink:xvimagesink0:
There may be a timestamping problem, or this computer is too slow.
WARNING: from element /GstPipeline:pipeline0/GstXvImageSink:xvimagesink0: A lot
of buffers are being dropped.
Additional debug info:
gstbasesink.c(2675): gst_base_sink_is_too_late ():
/GstPipeline:pipeline0/GstXvImageSink:xvimagesink0:
There may be a timestamping problem, or this computer is too slow.
WARNING: from element /GstPipeline:pipeline0/GstXvImageSink:xvimagesink0: A lot
of buffers are being dropped.
Additional debug info:
gstbasesink.c(2675): gst_base_sink_is_too_late ():
/GstPipeline:pipeline0/GstXvImageSink:xvimagesink0:
There may be a timestamping problem, or this computer is too slow.
WARNING: from element /GstPipeline:pipeline0/GstXvImageSink:xvimagesink0: A lot
of buffers are being dropped.
Additional debug info:
gstbasesink.c(2675): gst_base_sink_is_too_late ():
/GstPipeline:pipeline0/GstXvImageSink:xvimagesink0:
There may be a timestamping problem, or this computer is too slow.
WARNING: from element /GstPipeline:pipeline0/GstXvImageSink:xvimagesink0: A lot
of buffers are being dropped.
Additional debug info:
gstbasesink.c(2675): gst_base_sink_is_too_late ():
/GstPipeline:pipeline0/GstXvImageSink:xvimagesink0:
There may be a timestamping problem, or this computer is too slow.
^CCaught interrupt -- handling interrupt.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.