Frequently Asked Questions

Any questions? Please read this page first, because maybe you'll find an answer here. If not, don't hesitate and drop me a mail.

On which operating systems does MPUI run?

The only operating systems that are officially supported are Windows NT and its predecessors (2000, XP, 2003). It may work with WINE, but this is untested. It is a 32-bit application, but it should run on the x64 versions of Windows, too. The same is true for Vista. It does not work on Windows 95, 98 or Me because of weird problems with I/O redirection. Any help on this is appreciated, but I can't test that for myself because I don't have any 9x installations at hand to test on.

Why does MPlayer always use 100% CPU? It doesn't when I start MPlayer directly (without MPUI).

This is some strange bug in MPlayer itself: If the -wid option (the option that embeds MPlayer in another window, e.g. MPUI's) is used, it does some nasty stuff that eats up the CPU. This problem is already fixed in the MPlayer CVS, so be sure to use a recent version. The build that comes with MPUI is recommended.
For technical details, see my blog posts about MPUI 1.1.1 (where I first investigated the bug) and the patch where I fixed it.

What's special about the MPlayer version that ships with MPUI?

The MPlayer build that can be downloaded along with MPUI is just a standard checkout from the CVS repository, compiled with MinGW. So it's very similar to the »semi-official« build from Sascha Sommer.
The only difference is that the configuration of MPUI's MPlayer is minimized: By default, MPlayer includes features like reading and writing GIF, JPEG or PNG sequences, none of which is very useful in a normal media player. Thus, I disabled some of these features, saving roughly 500k of compressed binary size.

MPlayer always says something like this on startup:
  C:\WINDOWS\Fonts\Arial.ttf doesn't look like a font description, ignoring.
  Cannot load font: C:\WINDOWS\Fonts\Arial.ttf
Is this an error?

No, that's nothing to worry about. MPUI tells MPlayer which OSD font to use (if it didn't, no OSD would be visible at all), and MPlayer checks for its own proprietary font description format first. These two messages only complain about Arial.ttf not being in the expected format. Only if this check fails, MPlayer tests whether the font file is a TrueType file.