2010-06-29, 09:05 AM
(This post was last modified: 2010-06-29, 09:33 AM by johnsonx42.)
sub Wrote:Is the time on your file 4:24 pm?Yes, June 29, 2010, 4:24pm. That's in the future for me, but I don't see how Windows would care about that.
Sub, let's not worry about this for now, you probably have better things to work on. I've worked around the potential problem on my end by unbinding the green button on my remote, it does nothing now, so there's no easy way to launch a second instance of NextPVR.exe by accident. So far so good on recordings, they've all proceeded normally on Monday, as did the majority on Sunday. I don't know if the recordings marked failed issue was related to having a second instance of NextPVR.exe running or not... I'm about 100% sure I did have a second instance running on Saturday when every recording was marked failed, so it seems at least possible that caused my particular version of the problem.
I don't know about anyone else's occurances though... ACTCMS's log is quite different from mine. His shows the recording being marked failed the moment it was supposed to finish except for the padding, almost as if it's just a bug in the padding logic. Mine shows the recording service suddenly waking up hours after all the recordings were done, apparently because I deleted a recording, and marking them all failed at the same time; simultaneously my NPVR.log was empty. Different flavors of the same problem, or completely different problems that both happen to result in the same symptom? I tend to think the latter.
server: NextPVR 5.0.7/Win10 2004/64-bit/AMD A6-7400k/hvr-2250 & hvr-1250/Winegard Flatwave antenna/Schedules Direct
main client: NextPVR 5.0.7 Desktop Client; LG 50UH5500 WebOS 3.0 TV
main client: NextPVR 5.0.7 Desktop Client; LG 50UH5500 WebOS 3.0 TV