<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, May 14, 2014 at 5:46 AM, Jean-Yves Avenard <span dir="ltr"><<a href="mailto:jyavenard@gmail.com" target="_blank">jyavenard@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 14 May 2014 05:06, John <<a href="mailto:reidjr@lineone.net">reidjr@lineone.net</a>> wrote:<br>
<br>
> I am intrigued by what the difference is between the frontend being in the<br>
><br>
> kState_WatchingRecording rather than kState_WatchingPreRecorded, as I assume<br>
> it is the dBase activity of being in the former state that causes the issue.<br>
> As the backend shouldnt care if a frontend is watching somthing its<br>
> recording, nulling out that activity seems to make sense.<br>
<br>
as far as the FE is concerned, it makes no difference except that it<br>
will know if it needs to query the database for seek tables.<br>
<br>
your BE is obviously too busy to properly serve files while also recording<br><br></blockquote><div><br></div><div>I would have to agree with JYA on this. My setup has 2 HDHR's recording from antenna, an HD-PVR and a PVR-150, and I found that many recordings were damaged or would have dropped sections (especially the HDHR recordings, which led me down the wrong path of thinking it was signal related), until a few weeks ago I upgraded my backend hardware (new mobo), and more specifically moved to faster and dedicated drives. Since I've done that, I have not had any of the issues that you are having, and that I had previously.</div>
<div><br></div><div>Tom</div><div><br></div></div></div></div>