summaryrefslogtreecommitdiffstats
path: root/DOCS/DGA
diff options
context:
space:
mode:
authoracki2 <acki2@b3059339-0415-0410-9bf9-f77b7e298cf2>2001-06-17 21:20:29 +0000
committeracki2 <acki2@b3059339-0415-0410-9bf9-f77b7e298cf2>2001-06-17 21:20:29 +0000
commit46fcb9f83a46751fff7639dc757c77999c0926de (patch)
treea734ecdfa8eee026616dc73e16abe03448545dc1 /DOCS/DGA
parent4a17b6a5be84d79113e806cadb3d7f1cc5b3445b (diff)
downloadmpv-46fcb9f83a46751fff7639dc757c77999c0926de.tar.bz2
mpv-46fcb9f83a46751fff7639dc757c77999c0926de.tar.xz
- reflect changes as to -(no)double and -lircconfig
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@1152 b3059339-0415-0410-9bf9-f77b7e298cf2
Diffstat (limited to 'DOCS/DGA')
-rw-r--r--DOCS/DGA15
1 files changed, 15 insertions, 0 deletions
diff --git a/DOCS/DGA b/DOCS/DGA
index 51fd989834..97f5a62c55 100644
--- a/DOCS/DGA
+++ b/DOCS/DGA
@@ -97,6 +97,21 @@ Contents
results in much smoother movie replaying. It will tell you whether double-
buffering is enabled or not.
+ Doublebuffering means that the next frame of your video is being drawn in
+ some offscreen memory while the current frame is being displayed. When the
+ next frame is ready, the graphics chip is just told the location in memory
+ of the new frame and simply fetches the data to be displayed from there.
+ In the meantime the other buffer in memory will be filled again with new
+ video data.
+
+ Doublebuffering may be switched on by using the option -double and may be
+ disabled with -nodouble. Current default option is to disable
+ doublebuffering. When using the DGA driver, onscreen display (OSD) only
+ works with doublebuffering enabled. However, enabling doublebuffering may
+ result in a big speed penalty (on my K6-II+ 525 it used an additional 20% of
+ CPU time!) depending on the implementation of DGA for your hardware.
+
+
6. Speed issues
~~~~~~~~~~~~~~~