diff options
| author | Akemi <der.richter@gmx.de> | 2016-06-16 19:28:14 +0200 |
|---|---|---|
| committer | wm4 <wm4@nowhere> | 2016-06-18 19:15:34 +0200 |
| commit | fb7c5804bbb6046472406f3fa8426784cbda4408 (patch) | |
| tree | 48656ec6f4b2320fea7736ff2214f3c3d5cbe2f0 /wscript | |
| parent | 0fd5a24ecb9a0b1d716224b2eafa487b3e2574d5 (diff) | |
| download | mpv-fb7c5804bbb6046472406f3fa8426784cbda4408.tar.bz2 mpv-fb7c5804bbb6046472406f3fa8426784cbda4408.tar.xz | |
cocoa: fix actual display refresh rate retrieval
We have two problems here.
1. CVDisplayLinkGetActualOutputVideoRefreshPeriod, like the name suggests,
returns a frame period and not a refresh rate. using this as screen_fps
just leads to a slideshow. why didn't this break video playback on OS X
completely? the answer to this leads us to the second problem.
2. it seems that CVDisplayLinkGetActualOutputVideoRefreshPeriod always
returns 0 if used without CVDisplayLinkSetOutputCallback and hence always
fell back to CVDisplayLinkGetNominalOutputVideoRefreshPeriod. adding a
callback to CVDisplayLink solves this problem. the callback function at
this moment doesn't do anything but could possibly used in the future.
Diffstat (limited to 'wscript')
0 files changed, 0 insertions, 0 deletions