<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
> I just went to look at dmesg for some other reason and found these errors.<BR>><BR>> [108715.863315] ivtv0: All encoder MPEG stream buffers are full. Dropping<BR>> data.<BR>> [108715.863320] ivtv0: Cause: the application is not reading fast enough.<BR>> [187845.748109] ivtv0: All encoder MPEG stream buffers are full. Dropping<BR>> data.<BR>> [187845.748115] ivtv0: Cause: the application is not reading fast enough.<BR><BR>>>I get these every once in a while. It's not anything to worry about<BR>>>unless you're getting a constant stream of them during every<BR>>>recording. It's difficult to diagnose just based on these messages.<BR>>>What was the load of the machine while the recording was in progress?<BR>>>How much I/O activity was there?<BR><BR>>>I get these in the rare instances where my backend is transcoding,<BR>>>commercial flagging, mythfilldatabase is running and both tuners are<BR>>>recording at the same time.<BR><BR>>>The impact on my recordings is minimal... maybe some garbled/missing<BR>>>frames for a few seconds.<BR><BR>>>Joe Ripley<BR>>>vitaminjoe@gmail.com<BR><BR><BR>Joe,<BR>
Thanks for the reply. I can't say how much I/O activity there was at the time since I can't read the dmesg error time? I can't see anything unusual in the mythbackend.log file? I'll have to check out my recent recordings for any missing frames and whatnot as I am way behind on watching stuff. I have stuff from October to watch, he he he. I have a 500gb hdd on my main backend with a PVR-350 and a 500gb on a secondary backend with a PVR-500 in it. Recordings are stored on their own machines since I couldn't figure out the whole NFS share thingy. Thanks for your comments. Happy New Year.<BR>
<BR>
daniel<BR></body>
</html>