All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 79223] New: extra vsync when reading back pixels in xbmc
Date: Sun, 25 May 2014 19:10:07 +0000	[thread overview]
Message-ID: <bug-79223-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1452 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=79223

          Priority: medium
            Bug ID: 79223
          Assignee: dri-devel@lists.freedesktop.org
           Summary: extra vsync when reading back pixels in xbmc
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: pierre-bugzilla@ossman.eu
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: DRM/Radeon
           Product: DRI

Something is causing an extra wait for vsync in xbmc when it needs to read back
pixels. This seems to be specific to the radeon driver as I'm not seeing it
with nouveau.

Test scenario:

 - Configure xbmc to wait for vsync

 - Install something that activates xbmc's capture code (e.g. xbmc's boblight
plugin)

 - Play a video whose framerate > screen refresh / 2

You'll see the frame rate reliably locked to screen refresh / 2 under these
circumstances. A major problem as you generally want to run with a 24 Hz
refresh rate for 24 Hz films.


I'm unable to pinpoint exactly the offending GL command as xbmc's rendering is
quite complex. I hope you're more experienced in finding these things. :)

The rough sequence of events is:

1. xbmc renders the scene
2. Wait for vsync
3. Map PBO and memcpy data. (from previous frame)
4. Render small version of scene
5. glReadPixels into PBO

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2755 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2014-05-25 19:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-25 19:10 bugzilla-daemon [this message]
2014-05-25 19:10 ` [Bug 79223] extra vsync when reading back pixels in xbmc bugzilla-daemon
2014-05-25 20:20 ` bugzilla-daemon
2014-05-28  3:09 ` bugzilla-daemon
2014-05-28  5:46 ` bugzilla-daemon
2014-05-28  7:03 ` bugzilla-daemon
2014-05-30 13:15 ` bugzilla-daemon
2014-05-30 13:21 ` bugzilla-daemon
2014-05-30 13:35 ` bugzilla-daemon
2014-05-30 13:47 ` bugzilla-daemon
2014-05-30 20:04 ` bugzilla-daemon
2014-05-30 21:23 ` bugzilla-daemon
2014-06-01 18:21 ` bugzilla-daemon
2014-06-02  7:07 ` bugzilla-daemon
2014-06-02 15:48 ` bugzilla-daemon
2014-06-02 19:24 ` bugzilla-daemon
2014-06-02 19:26 ` bugzilla-daemon
2014-06-03  6:34 ` bugzilla-daemon
2014-06-03 15:07 ` bugzilla-daemon
2019-11-19  8:49 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-79223-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.