<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
>> Any thoughts on troubleshooting options or other logs/verbose levels I<br>
>> should be looking at?<br>
><br>
> Look at the log and signal status on the Prime's web interface.<br>
><br>
> Just curious... Are the recordings correctly detected as damaged? (New in 0.25)<br>
><br>
> Tom<br>
<br>
I don't see anything of interest in the prime's log and the signal<br>
strength seems good. Yes, the recordings are being correctly detected<br>
as damaged (thanks for that thought... changing to a theme which shows<br>
the damaged status makes it easier to get an idea of how widespread<br>
this issue is). It turns out it is not all recordings... it is maybe<br>
1/3 of them. More interesting is that it occurs in chunks. Last<br>
night every recording from about 7pm to 10pm was damaged but none of<br>
the others throughout the day were. I'm not sure what to make of that<br>
other than myth is purposefully damaging the "important" recordings?<br>
:)<br><br></blockquote><div><br></div><div>Is it possible that the combined bandwidth of all of the concurrent recordings is saturating your IO (network or disk). I know that my system records more concurrent recordings, and much larger recordings during prime-time than any other part of the day.</div>
<div><br></div><div> I also know that we have been experiencing tons of bad weather the last few days, mostly in the evenings as the temperatures drop, and that has caused some recordings to fail for me.</div></div>