Mplayer fails with Window Resize

Hi,

When running mplayer under Angstrom on Beagleboard, if I resize the
window that contains a video that is playing, the whole thing goes
kerflooey. The desktop gets corrupted, there are lots of lines across
the screen etc.

Any ideas?

Thanks very much.

Best regards,
Geof

That's the DSS overlay not liking the stuff it gets, it's an alignment issue. Try with 2.6.28 to get better results.

regards,

Koen

I'm using the 2.6.28 kernel (sakoman's build). Any other ideas?

Thanks.
Geof

I'm using the 2.6.28 kernel (sakoman's build). Any other ideas?

Yes, use the angstrom one.

regards,

koen

My builds don't have the DSS2 patches, so it may be related to that.

Steve

Ok, I've done some experimentation. Using the Angstrom kernel (2.6.28
from demo/beagleboard), mplayer works (and I can resize the window) as
long as I use: -vo x11. With the Angstrom kernel, -vo xv does not
display any video. Whereas with the Sakoman build, mplayer works (but
dies if I resize the window) and I can use -vo xv. And the -vo xv
option seems to have better performance. Is this what is expected?
Is there a preference of x11 vs xv?

Also, the Angstrom kernel runs the DVI-D monitor at a much lower
resolution (I think 800x600) versus the Sakoman built kernel (I think
1280x1024). So things look better with the Sakoman build. As a long-
time Windows user (and I know that's evil), I'm used to the OS
figuring out what resolution to use based on the monitor attached. So
I'm surprised that the resolutions vary due to the build.

Thanks for listening. :slight_smile:

Best regards,
Geof

Ok, I've done some experimentation. Using the Angstrom kernel (2.6.28
from demo/beagleboard), mplayer works (and I can resize the window) as
long as I use: -vo x11. With the Angstrom kernel, -vo xv does not
display any video. Whereas with the Sakoman build, mplayer works (but
dies if I resize the window) and I can use -vo xv. And the -vo xv
option seems to have better performance. Is this what is expected?
Is there a preference of x11 vs xv?

I'll let Koen answer this first question since I am pretty sure it is
DDS2 related and I know very little about DSS2 :slight_smile: My guess is that
you may need to modify your kernel command line in u-boot to make this
work properly.

I'm working on support for an LCD panel for Overo, so I guess it is
time for me to make the switch. From what I understand DSS2 will be
better suited to support both DVI and LCD from the same kernel image.

Also, the Angstrom kernel runs the DVI-D monitor at a much lower
resolution (I think 800x600) versus the Sakoman built kernel (I think
1280x1024). So things look better with the Sakoman build. As a long-
time Windows user (and I know that's evil), I'm used to the OS
figuring out what resolution to use based on the monitor attached. So
I'm surprised that the resolutions vary due to the build.

You're pointing out one the motivations for the move to a new display
subsystem (DSS). The current implementation (call it DSS1) is
somewhat challenged in its ability to support arbitrary
resolutions/timings. DSS2 should fix that (along with providing lots
of other nifty features)

That alone won't be enough to give the behavior you like in Windows --
for that the display subsystem will need to communicate with the
monitor to receive a list of supported resolutions. Beagle provides
the I2C channel that is used to do this, and Koen has verified that it
actually works. So it is just a matter of time before you are happy
;-=)

Steve

Not quite. Monitors (well, my monitor at least) report only normal
timings, which OMAP is unable to use.

I guess we could get the resolutions and refresh rates from the monitor,
then modify the timings to reduced ones, and hope the monitor accepts
the result.

Tomi