On Sat, 12 May 2012 11:41:33 -0400
Norman Invasion <invasivenor...@gmail.com> wrote:

> On 12 May 2012 11:05, Alex Schuster <wo...@wonkology.org> wrote:
> > Norman Invasion writes:
> >
> >> On 11 May 2012 21:40, Alex Schuster <wo...@wonkology.org> wrote:
> >> > Finally, I found something. It's Dolphin!
> > [...]
> >> Apologies: I haven't followed this thread from the beginning,
> >
> > Which was quite long ago :)
> >
> >> but do you have any advanced power management features
> >> enabled (especially hard drive related)?
> >
> > My drives spin down after 30 minutes of idle time, but this never
> > happens for the system drive. The CPU is set to throttle down from
> > 3600 MHz to 1400 MHz with the ondemand governor, but changing to
> > performance governor makes no change.
> >
> >> When I pull the power cord on my lap-top, it goes into all kinds
> >> of nutty "power-saving" and mplayer has long pauses while
> >> the drive spins back up.
> >
> > Yeah, but those pauses are much longer than the small interruptions
> > that are a fraction of a second mostly, and do not happen 15 times
> > per minute. And it only happens when MPlayer is started from
> > Dolphin. Well, mainly, when there is much system load, I also had
> > small interruptions when I run mplayer from the command line, but
> > they are much much less frequent, and do not happen under normal
> > circumstances, like when doing emerges while playing videos.
> >
> 
> I'm just recalling that I get stuttering audio in freebsd, which is
> caused by what-I-don't-know, but only happens when the CPU load is
> low. Firing up burncpu or doing useless recompiles ameliorates it.
> 

I was getting stuttering audio from a sizeable % of my .avi files
served from a FreeBSD NAS. The likely cause became obvious when I
noticed that it was only on .avi files - all real containers were
fine[1].

mencoder -ovc copy -oac copy -of avi -o <new_file> <old_file>

fixed it permanently. I'm won't go so far as to say this might apply
to your issue, but sometimes the simplest things are the actual
causes :-)


[1] .avi files are notorious for this shit. It's what happens when you
are Microsoft and you release any old crappy format without consulting
the other experts out there (who will always outnumber you)


-- 
Alan McKinnnon
alan.mckin...@gmail.com


Reply via email to