After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 731125 - xvimagesink can't display 4k video
xvimagesink can't display 4k video
Status: RESOLVED DUPLICATE of bug 706066
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
git master
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-06-02 19:55 UTC by Lubosz Sarnecki
Modified: 2014-06-04 13:55 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Lubosz Sarnecki 2014-06-02 19:55:33 UTC
This works:
gst-launch-1.0 videotestsrc num-buffers=100 ! video/x-raw, width=4096, height=2160 ! glimagesink

This fails:
gst-launch-1.0 videotestsrc num-buffers=100 ! video/x-raw, width=4096, height=2160 ! xvimagesink


ERROR default video-frame.c:138:gst_video_frame_map_id: failed to map video frame plane 1


The ximagesink also fails:
RROR: from element /GstPipeline:pipeline0/GstXImageSink:ximagesink0: Failed to create output image buffer of 4096x2160 pixels


Is this a limitation in the X server?
Comment 1 Tim-Philipp Müller 2014-06-02 21:12:44 UTC
What is the output of 'xvinfo'?
Comment 2 Lubosz Sarnecki 2014-06-02 22:11:39 UTC
X-Video Extension version 2.2
screen #0
  Adaptor #0: "Nouveau GeForce 8/9 Textured Video"
    number of ports: 32
    port base: 63
    operations supported: PutImage 
    supported visuals:
      depth 24, visualID 0x21
      depth 24, visualID 0x22
    number of attributes: 7
      "XV_SET_DEFAULTS" (range 0 to 0)
              client settable attribute
      "XV_SYNC_TO_VBLANK" (range 0 to 1)
              client settable attribute
              client gettable attribute (current value is 1)
      "XV_BRIGHTNESS" (range -1000 to 1000)
              client settable attribute
              client gettable attribute (current value is 0)
      "XV_CONTRAST" (range -1000 to 1000)
              client settable attribute
              client gettable attribute (current value is 0)
      "XV_SATURATION" (range -1000 to 1000)
              client settable attribute
              client gettable attribute (current value is 0)
      "XV_HUE" (range -1000 to 1000)
              client settable attribute
              client gettable attribute (current value is 0)
      "XV_ITURBT_709" (range 0 to 1)
              client settable attribute
              client gettable attribute (current value is 1)
    maximum XvImage size: 8192 x 8192
    Number of image formats: 4
      id: 0x32315659 (YV12)
        guid: 59563132-0000-0010-8000-00aa00389b71
        bits per pixel: 12
        number of planes: 3
        type: YUV (planar)
      id: 0x30323449 (I420)
        guid: 49343230-0000-0010-8000-00aa00389b71
        bits per pixel: 12
        number of planes: 3
        type: YUV (planar)
      id: 0x32595559 (YUY2)
        guid: 59555932-0000-0010-8000-00aa00389b71
        bits per pixel: 16
        number of planes: 1
        type: YUV (packed)
      id: 0x59565955 (UYVY)
        guid: 55595659-0000-0010-8000-00aa00389b71
        bits per pixel: 16
        number of planes: 1
        type: YUV (packed)
Comment 3 Sebastian Dröge (slomo) 2014-06-04 09:18:01 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 706066 ***
Comment 4 Tim-Philipp Müller 2014-06-04 12:19:42 UTC
Note that it might not be the same as the other bug, since that's about not putting the size limitation into the caps.

But here the size limitation is 8192x8192, but it still appears to fail to allocate less than that.
Comment 5 Lubosz Sarnecki 2014-06-04 13:55:49 UTC
This also could be a bug in the graphics driver, which adresses the wrong maximal buffer size.
The funny thing is that it is possible to allocate this size via OpenGL.
I will try this with the NVIDIA blob driver.