2014-04-19, 04:09 AM
Greetings to all.
This is my first post here and I just wanted to say Hi to everyone using these forums.
I have been using NPVR for about 3-4 weeks and there is one issue that I have seen twice now and appears to be a bug of some sort.
For reference, it sounds like it could be the same thing as this person's issue:
http://forums.nextpvr.com/showthread.php...this-error
I am not sure what might be the cause though. It happened on the last NextPVR version (3.1.1), and also happens on this new version (3.2.9).
I am using the default padding, 1 minute pre and 2 minutes post.
To preface, I am subscribed to Schedule Direct and they are indeed sending me the correct info. I just checked the XML file.
This is the second time this has happened that I know of. There was an airing of Doctor Zhivago on TCM today, which takes up nearly a 4 hour time slot. The actual movie may be a bit shorter than that. The recording I ended up with on my hard drive was 2:04:43 long. It started on time, but ended early.
Here is the Schedule Direct time code entry for that airing:
I have a Hauppauge HD-PVR2 Gaming Edition with the latest firmware from their website. The green light was on bright the whole time, indicating that it would have been capturing signal. Unfortunately I didn't actually have the TV on, but I was sitting in the room reading.
Also directly after that there was another movie which didn't record at all, "Meet Me in St. Louis". All I got was a zero-byte TS file. For that recording, I got a red "failed" indication and this message in NEWA:
Again, the bright green recording light on the Hauppauge was lit the entire time for this movie too.
See attachment for NRECORD log. (NEWA log not included due to already being FIFO'd)
So for now it appears that movies much larger than 2 hours might be causing something to lock up. I haven't noticed this for shorter movies by themselves, and have recorded about 40 other movies without noticing this happening.
Hope that helps!
Thanks
Chris
This is my first post here and I just wanted to say Hi to everyone using these forums.
I have been using NPVR for about 3-4 weeks and there is one issue that I have seen twice now and appears to be a bug of some sort.
For reference, it sounds like it could be the same thing as this person's issue:
http://forums.nextpvr.com/showthread.php...this-error
I am not sure what might be the cause though. It happened on the last NextPVR version (3.1.1), and also happens on this new version (3.2.9).
I am using the default padding, 1 minute pre and 2 minutes post.
To preface, I am subscribed to Schedule Direct and they are indeed sending me the correct info. I just checked the XML file.
This is the second time this has happened that I know of. There was an airing of Doctor Zhivago on TCM today, which takes up nearly a 4 hour time slot. The actual movie may be a bit shorter than that. The recording I ended up with on my hard drive was 2:04:43 long. It started on time, but ended early.
Here is the Schedule Direct time code entry for that airing:
Code:
<programme start="20140418161500 -0400" stop="20140418200000 -0400" channel="I50.12852.tmsdatadirect.com">
<title lang="en">Doctor Zhivago</title>
I have a Hauppauge HD-PVR2 Gaming Edition with the latest firmware from their website. The green light was on bright the whole time, indicating that it would have been capturing signal. Unfortunately I didn't actually have the TV on, but I was sitting in the room reading.
Also directly after that there was another movie which didn't record at all, "Meet Me in St. Louis". All I got was a zero-byte TS file. For that recording, I got a red "failed" indication and this message in NEWA:
Code:
Recording Error: No errors, but no data delivered. This is usually because the device failed to lock a signal.
See attachment for NRECORD log. (NEWA log not included due to already being FIFO'd)
So for now it appears that movies much larger than 2 hours might be causing something to lock up. I haven't noticed this for shorter movies by themselves, and have recorded about 40 other movies without noticing this happening.
Hope that helps!
Thanks
Chris