[MPlayer-dev-eng] [PATCH] dvdnav

The Wanderer inverseparadox at comcast.net
Mon Feb 6 08:27:08 CET 2006


Rich Felker wrote:

> On Mon, Feb 06, 2006 at 04:09:53AM +0100, Diego Biurrun wrote:
> 
>>On Sun, Feb 05, 2006 at 09:41:42PM -0500, Rich Felker wrote:

>>> Are you using -fixed-vo? In any case it sounds like this is the
>>> problem: reinitializing the vo again and again. We need to do
>>> something so the config request gets blocked if the new mode is
>>> the same as the old one.
>> 
>> No, I don't use -fixed-vo.
> 
> Try it and see if the problem goes away. BTW -fixed-vo is recommended
> to always be used unless you're using a broken old vo driver that
> crashes with it.

To always be used with everything, or just with streams which are
supposed to be multiple segments of the same thing? (Also, where is this
recommended? I don't see any such note in the docs, and in fact
-fixed-vo is described as beta code in the man page.)

I have groups of files - music videos and the like - which I like to
play back in semi-random order, and if I use -fixed-vo then very
frequently when going from one file to another I will either see only
part of the image (if the new file had a larger resolution), or see a
bright blue background around the video (if the new file had a smaller
resolution). Nothing I've done has been able to track down where the
blue is coming from, and I've mostly just decided that it's an inherent
side effect of using a "fixed" (i.e. invariant) video-out method;
-fixed-vo does not appear to be compatible with playing multiple
consecutive files with different resolutions.

(For the record, in case anyone cares enough for it to matter, the
relevant line from my config file is 'vo=xv,sdl,'. I believe I've
received the impression that xv is the recommended video-out method...)

-- 
       The Wanderer

Warning: Simply because I argue an issue does not mean I agree with any
side of it.

Secrecy is the beginning of tyranny.




More information about the MPlayer-dev-eng mailing list