[mythtv-users] Starting to think I should use Kaffeine instead of Mythtv

[Nick Rout]

On Wed, 19 Oct 2005 10:03:02 +1000
ffrr wrote:

> match at ece.utah.edu wrote:
> 
> >
> >I think sometimes people make posts like this out of frustration because they don't 
> >understand enough about the "problem" they see (or think they see) to ask a more 
> >intelligent question, or don't have the trouble-shooting skills to enlighten themselves. 
> >So, folks on the list have to pry meaningful information from the original poster (once 
> >the original poster finally gets someone's attention) in order to make an attempt at 
> >helping him solve his problem, or to lead him into solving it for himself. At least his post 
> >finally generated some discussion, and eventually the list gave him some ideas to try, 
> >and maybe some direction.
> >  
> >
> 
> Thank you for your understanding.

I have read bits of this thread, not all of it. However I seem to recall similar problems a while back being solved by fixing the audio - ie it
was an audio problem. When the audio driver/hardware couldn't keep up
the system would freeze momentarily while something caught up. Sorry
thats not very technical, but hopefully you get the picture.

Can i suggest that you do a little trouble shooting instead of all this
complaining? I am not trying to criticise you, sometimes people don't
know how to help theselves. Seeing glitches in a playback is not a
description a software author can diagnose without more information.

Can i suggest that you run mythfrontend from an xterm with logging
turned on. Watch for errors like audio overrun. If they seem to coincide with glitches in viewing take careful note.

Of course mythfrontend usually runs fuull screen and obscures the xterm
with the logging info. Personally I ssh in from another machine, then
set DISPLAY:

export DISPLAY=:0

then run mythfrontend from the command line from the other machine. The
logging info appears on the machine you are sitting at, the mythfrontend complete with glitches runs on the other machine. Watch for the error
messages as the glitches happen.


> 


-- 
Nick Rout <nick at rout.co.nz>