CVS: main/DOCS/man/en mplayer.1,1.811,1.812
CVS change done by Diego Biurrun CVS Update of /cvsroot/mplayer/main/DOCS/man/en In directory mail:/var2/tmp/cvs-serv1044/DOCS/man/en Modified Files: mplayer.1 Log Message: -double is now default, thus -nodouble needs to be documented instead. Slightly reworded the description of -nodouble. Index: mplayer.1 =================================================================== RCS file: /cvsroot/mplayer/main/DOCS/man/en/mplayer.1,v retrieving revision 1.811 retrieving revision 1.812 diff -u -r1.811 -r1.812 --- mplayer.1 24 Nov 2004 11:18:36 -0000 1.811 +++ mplayer.1 30 Nov 2004 22:47:28 -0000 1.812 @@ -33,7 +33,7 @@ .\" Title .\" -------------------------------------------------------------------------- . -.TH MPlayer 1 "2004-11-17" "The MPlayer Project" "The Movie Player" +.TH MPlayer 1 "2004-11-30" "The MPlayer Project" "The Movie Player" . .SH NAME mplayer \- movie player @@ -1959,15 +1959,6 @@ .PD 1 . .TP -.B \-double -Enables double buffering. -Fixes flicker by storing two frames in memory, and displaying one while -decoding another. -Can affect OSD negatively, but often it removes OSD flickering. -Needs twice the memory of a single buffer, so it won't work on cards with -very little video memory. -. -.TP .B \-dr \ \ \ Turns on direct rendering (not supported by all codecs and video outputs) .br @@ -2195,6 +2186,15 @@ .PD 1 . .TP +.B \-nodouble +Disables double buffering. +Double buffering fixes flicker by storing two frames in memory, and +displaying one while decoding another. +It can affect OSD negatively, but often removes OSD flickering. +It needs twice the memory of a single buffer and thus will not +work on cards with very little video memory. +. +.TP .B \-nograbpointer Do not grab the mouse pointer after a video mode change (\-vm). Useful for multihead setups.
On Tue, Nov 30, 2004 at 11:47:31PM +0100, Diego Biurrun CVS wrote:
+.B \-nodouble +Disables double buffering. +Double buffering fixes flicker by storing two frames in memory, and +displaying one while decoding another. +It can affect OSD negatively, but often removes OSD flickering. +It needs twice the memory of a single buffer and thus will not +work on cards with very little video memory.
I don't think there's any supported hardware where this is the case, though... Rich
D Richard Felker III writes:
On Tue, Nov 30, 2004 at 11:47:31PM +0100, Diego Biurrun CVS wrote:
+.B \-nodouble +Disables double buffering. +Double buffering fixes flicker by storing two frames in memory, and +displaying one while decoding another. +It can affect OSD negatively, but often removes OSD flickering. +It needs twice the memory of a single buffer and thus will not +work on cards with very little video memory.
I don't think there's any supported hardware where this is the case, though...
Remove the sentence then? Or just specify how much "little" video memory is? How much is "little" in this case anyway? Nowadays people believe that 8MB of video RAM is little memory, so this should be made explicit. Diego
On Wed, Dec 01, 2004 at 05:12:36PM +0100, Diego Biurrun wrote:
D Richard Felker III writes:
On Tue, Nov 30, 2004 at 11:47:31PM +0100, Diego Biurrun CVS wrote:
+.B \-nodouble +Disables double buffering. +Double buffering fixes flicker by storing two frames in memory, and +displaying one while decoding another. +It can affect OSD negatively, but often removes OSD flickering. +It needs twice the memory of a single buffer and thus will not +work on cards with very little video memory.
I don't think there's any supported hardware where this is the case, though...
Remove the sentence then? Or just specify how much "little" video memory is? How much is "little" in this case anyway? Nowadays people believe that 8MB of video RAM is little memory, so this should be made explicit.
something like 1-2 megs for normal sized video... if a card has that little memory, its io is way too slow to play a hi-res movie anyway. also, it only affects drivers where the buffers are actually in video memory and double-buffering is supported, i.e. mga/vidix/directx. imo it's irrelevant and the stuff about vid mem doesn't need to be documented. the only purpose of -nodouble is for debugging or if you have a perverse desire to see tearing. :) rich
D Richard Felker III writes:
On Wed, Dec 01, 2004 at 05:12:36PM +0100, Diego Biurrun wrote:
D Richard Felker III writes:
On Tue, Nov 30, 2004 at 11:47:31PM +0100, Diego Biurrun CVS wrote:
+.B \-nodouble +Disables double buffering. +Double buffering fixes flicker by storing two frames in memory, and +displaying one while decoding another. +It can affect OSD negatively, but often removes OSD flickering. +It needs twice the memory of a single buffer and thus will not +work on cards with very little video memory.
I don't think there's any supported hardware where this is the case, though...
Remove the sentence then? Or just specify how much "little" video memory is? How much is "little" in this case anyway? Nowadays people believe that 8MB of video RAM is little memory, so this should be made explicit.
something like 1-2 megs for normal sized video... if a card has that little memory, its io is way too slow to play a hi-res movie anyway. also, it only affects drivers where the buffers are actually in video memory and double-buffering is supported, i.e. mga/vidix/directx.
imo it's irrelevant and the stuff about vid mem doesn't need to be documented. the only purpose of -nodouble is for debugging or if you have a perverse desire to see tearing. :)
Notice about little memory removed.. Diego
participants (3)
-
D Richard Felker III -
Diego Biurrun -
syncmail＠mplayerhq.hu