[MPlayer-dev-eng] [PATCH] dvdnav

[The Wanderer]

Rich Felker wrote:

> On Mon, Feb 06, 2006 at 02:27:08AM -0500, The Wanderer wrote:
> 
>> Rich Felker wrote:

>>> 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.)
> 
> Always with everything. It prevents annoying things like flicker
> between multiple files, window being destroyed and recreated, etc.

Definitely very desirable, if it works right. (I'll note that ISTR that
it did work correctly with varying-resolution files at one point, but if
so it stopped a long time ago.)

Diego just removed the BETA CODE notice from the man page entry; should
we add a note there (and possibly another somewhere in the XML docs?) to
the effect that the option is always recommended?

>> 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.

(To extend this: even if the files are the *same* resolution, if there
was blank space left around the video to fit it within the screen's
aspect ratio, then on switching to the second file there will
(frequently if not necessarily always) be bright blue where that blank
space was. Or I remember encountering this in the past, anyway - I
haven't been able to find a pair of files which give the effect now, so
I can't confirm it.)

(In case it wasn't obvious from the mention of "blue background": this
entire problem occurs only when also using -fs. Since that's the only
way I ever play multiple files in the same session, it didn't occur to
me to mention it before.)

> It's supposed to be. If it's not then this is a bug, and hopefully
> the co maintainer will fix it if you report it. :)

Okay... what exactly should go into this type of bug report? There's no
crash, so obviously that type of information is unavailable; the -v
output doesn't seem at a glance to contain anything obviously related.
How many levels of verbosity (and/or, what types of verbosity) would I
be likely to need to get relevant output?

-- 
       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.