The "Minimum Cache Size" option in the Configure dialog allows settings all the way down to 0. Unfortunately mplayer requires a setting of >=32 for the cache size. As a result, the video will not play and mplayerplug-in will show "Stopped" immediately after downloading a video. Sometimes it even appears that the download has stopped somewhere around 95% instead of showing "Stopped". A bit of research (Gentoo forums, Google) will show that any number of issues could show these symptoms, and this issue of an invalid cache setting is just one of them. Reproducible: Always Steps to Reproduce: 1.Configure mplayerplug-in "Minimum Cache Size" to be <32 and uncheck "Play media directly from site". 2.Restart the application that is using mplayerplug-in. 3.Playback a video, for example a movie trailer from apple.com/trailers Actual Results: The video will go directly to the "Stopped" state after downloading. Expected Results: The video should playback after downloading. To see the details of what mplayerplug-in is trying to do when it loads a video, add the line: debug=1 to ~/.mplayer/mplayerplug-in.conf. Then run Firefox (or whatever you are using) from the console to see the output from mplayerplug-in. The following is an excerpt of the output: Starting: mplayer -wid 0x2415464 -vf scale=640:-3 -vo x11 -zoom -ao alsa -osdlevel 1 -nojoystick -noconsolecontrols -cookies -softvol -slave -user-agent NSPlayer -nomouseinput -cache 0 /tmp/mplaySKl1t6 Getting file mode flags READ: MPlayer dev-SVN-r27120-4.1.2 (C) 2000-2008 MPlayer Team READ: CPU: AMD Athlon(tm) 64 Processor 3700+ (Family: 15, Model: 39, Stepping: 1) READ: CPUflags: MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 1 READ: Compiled with runtime CPU detection. READ: The cache option must be >= 32: 0 READ: Error parsing option on the command line: -cache ----player thread: tryagain = 2 If you were to try running that mplayer command line in an xterm (replacing "/tmp/mplaySKl1t6" with an actual filename or URL), you would get a similar error.
Luckily, this was an easy fix! I'll send my patch upstream, but it's fixed in 3.55 (inCVS).
