When I play some Mpeg4(Divx or Xvid,640*360) files with Mplayer,
At the start ,the video and the audio are very smooth but after a while (about 10 mins), in some scenes the audio become not smooth,especially in some scenes with background music ,(but the video is very smooth)If I stop the mplayer and run it again ,the sound will be fine again.
The same video ,if there isn't the background music ,everything is very good.
When this happened ,I find the CPU consume is not 100%.
The default audio codec is "mad",I tried to change to ffmpeg,It's the same.
I think maybe it is because the audio decoder is not very good,
it can't deal with some mistaken codes ,or the OS can't release
some resource .
Now I want to install mpg123 codec for Mplayer,but where to download it and how to add it to Mplayer?
I only find version 0.66 at http://elkins.org/packages/
but it is for Chinook,and not for Diablo.
Who can tell me why?How to resolve it for me.THANKS.
---------------
Frame dropping have been set "Yes".

First, I'd make sure frame dropping is enabled.

Frame dropping doesn't help.

Either live with it, or find a copy of PocketDivxEncoder. That one (with the correct settings) produces video files that don't stutter.

I don't know why.

Today I find It will be better when I set framedrop to OFF.

Presumably it plays better with -noaudio then?

Strange that it only happens some time after the start of the video, what does the cpu usage do then? Is it something particular about the video, or some issue with mplayer?

I would recommend to also check mplayer autput after playback ('Report' button), maybe it gets a lot of error messages accumulated or whatever.

One of the problems with fixing this issue is that I don't have a problematic video sample for testing it and nobody cared to provide it to me yet. I tried various encoding settings myself some time ago with no luck (that means, could not reproduce the bug).

I should note that I don't have any windows system to try all the fancy encoders around, so the only thing that will help me to investigate the problem is a video sample (or a full commandline and exact version for mencoder that is used to produce problematic files). That is if you want my assistance of course.

Counterintuitively, what fixed a similar problem with audio (reproducing videos encoded for an ipod from an nfs mounted directory) was to use the -nocache option.