> Regarding mplayer: There is another ebuild in the multimedia-overlay > that I prefer now to mplayer(-mt) and that also uses ffmpeg-mt : > media-video/mplayer-uau. > > It fetches the mplayer-version from one of the mplayer-devs and creates > a binary called "mplayer-uau" which can be installed at the same time as > the official mplayer package.
I gave that a try and it smoothed everything right out, so I guess it was a CPU issue after all. Thank you for your help. How is mplayer-uau different from mplayer-mt? Maybe mplayer-mt can't be installed alongside mplayer? > Regarding your frame drops: it is highly likely that sound is the > problem. Please try playing the video with "-ao null" to see if that's > the case. I assume you use pulseaudio? Check if it has real time > capabilities (kill it, start it with verbose/debug in foreground, read > log). Also try "-ao alsa" and "-ao oss". No change with "-ao null". I actually don't use pulseaudio. > Your data-source (gard disk, network?) is fast enough? Copy 1GB into RAM > to be sure by ether using RAM-disk or cache-settings. It's running from an internal HD. > Try nvidia-binary. You'll get VDPAU in that case, which will result in > about 5% CPU usage when decoding h264! I'm trying to move away from VDPAU. It fixes the performance issue but the extra layer creates a new set of problems. - Grant
