<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I have now tried many things, but I am running out of ideas.<br>
<br>
* it happens usually every 2-10 minutes<br>
* it happens for HD h264 and SD MPEG2, just for HD a little more often<br>
* it happens with and without VDPAU<br>
* it happened on old and upgraded hardware (only sound card identical)<br>
* it happens on 0.26 and earlier versions<br>
* I have tried all VDPAU profiles<br>
* I have disabled logging over NFS (> /dev/null)<br>
* I have enabled realtime prio (but it is not mentioned in the log)<br>
* I have reniced mythfrontend to -2 and X to -12<br>
* I have set the GPU to max. frequency all the time, so no switching<br>
* I have disabled the often crashing mythlcdserver<br>
* I have tried different kernel and NVidia driver versions<br>
<br>
What else can I try? What more info should I provide?<br>
<br>
Probably, something needs a little CPU time every now and then and this<br>
probably causes that little "jump" in playback and the log entry from<br>
the subject, but I don't know what it is and why MythTV is so sensitive<br>
on such hardware specs (Core i3, 3.1 GHz)?<br>
<br>
Or does it probably have something to do with the fact that this is a<br>
diskless PXE frontend?<br>
<div class="im"><br></div></blockquote><div><br></div><div style>That would be my guess. Between VDPAU and your CPU... you have a surplus of cpu resources, I have much less powerful systems (P4 3GHz) using CPU decoding that don't exhibit symptoms like that even with HD content. I find it difficult to believe that it's anything other than the network.</div>
<div style><br></div><div style>One other other thing to look at... you are using the myth:// protocol and not accessing your recordings via an NFS mouint, correct? While 'local' access should work, you might find the myth protocol to be more stable.</div>
<div style><br></div></div><br></div></div>