First 5 min missing, finally saw it happen!

[gplasky]

Before you do upgrade to the latest release-6.3.10. It is out of beta and an official release.

Gerry

[timnelsonic]

I've now captured logs surrounding this error for two different shows. In both cases, the logs had this message at precisely the time the show was supposed to start recording:

Built:sage.EncodingException: ERROR (-3,0x80070020): There was a problem accessing the filesystem for capture.

It appears that Sage tries to record the show, something goes wrong with the write operation, so it gives up and tries again five minutes later. I've provided support with this info so hopefully they can help out.

I've been running 6.3.10 Release Candidate, so I plan on installing 6.3.10 Final tonight on the off-chance it will fix things, but I'm not too optimistic.

[Mark57]

Originally Posted by timnelsonic

I've now captured logs surrounding this error for two different shows. In both cases, the logs had this message at precisely the time the show was supposed to start recording:

Built:sage.EncodingException: ERROR (-3,0x80070020): There was a problem accessing the filesystem for capture.

It appears that Sage tries to record the show, something goes wrong with the write operation, so it gives up and tries again five minutes later. I've provided support with this info so hopefully they can help out.

I've been running 6.3.10 Release Candidate, so I plan on installing 6.3.10 Final tonight on the off-chance it will fix things, but I'm not too optimistic.

Interesting. That's a different error than some of us were getting previously. I was getting "SEEKER HAS DETECTED A HALT IN THE ENCODER...TRYING TO RESET IT" but I've not gotten it again since RC9. It seems to be fixed for me but I still watch for it. Let us know what you hear from support.

[hemicuda]

Originally Posted by timnelsonic

I've been running 6.3.10 Release Candidate, so I plan on installing 6.3.10 Final tonight on the off-chance it will fix things, but I'm not too optimistic.

Is there a difference in 6.3.10 vs 6.3.10rc? one of the Mods mentioned it, but the statement wasn't quite clear for me

[carlgar]

Originally Posted by hemicuda

Is there a difference in 6.3.10 vs 6.3.10rc? one of the Mods mentioned it, but the statement wasn't quite clear for me

No, see http://forums.sage.tv/forums/showthread.php?t=31305

[gateslinger]

Just had this happen to me on my 1600 card on a standard def recording with a fresh version of 6.3.10RC. I nuked all of the video source info in the sage.properties file since I had some problems with remapped HD channels and re-did the HD channel maps. Now I'm wondering if that was causing issue?

[Mark57]

For what it's worth, I'm still watching mine with full logging and it has not reoccurred. I have two HVR-1600's and one HVR-1800.

[bbig119]

I've been seeing this happen with some moderate frequency on my SD captures using a pvr150. As others have done, I will enable logging and try to determine if there is an error and what might cause it.

I've got the pvr150, fusion 5 and HDHR in my system, but haven't seen the missing 5min from any recorded digital content, only that from the pvr150.

[Goodspike]

Are you people seeing exactly 5 minutes, or some variation less than 5 minutes?

For about the past month I've had an issue where it sometimes misses the first few minutes of a program. I haven't figured out a pattern.

I'm using a HDHR (with very old software) and a version of Sage that is probably a year or so old. The only thing that's changed is Windows updates.

[hemicuda]

Happened to me last night on Idol. started 3min into (2min start padding) so it's right on 5min for me; when it happens. I'd logged the afternoon HD recording earlier that day which recorded properly and stupid me turned off logging. This morning I turned it on and I'll leave the darn thing enabled until I messes another HD show. Haven't had any issues w/ SD so far (knock on wood).

I did notice in the last log that it tried to tune ATSC first instead of QAM.

[bshiek]

Happened to me last night.

6.3.10

HD Homerun, both tuners recording 2 different HD OTA shows at the same time. One of the recordings skipped the first 5 minutes.

I haven't turned on logging yet, but now I have a reason to.

[carlgar]

bshiek, what version of the HDHR drivers are you using? There was a 20080305 version that I believe could cause the problem. The current version is 20080307.

[donkey]

we found one kind of "missing recording problem" is caused by the tuning timing/sync issue, which most likely happens on HDHR due to network traffic delay, we added 500 ms delay in default in 6.3.10 for tuning sync, but it may be not enough, you could add more time delay to check by dropping a file "xxxx-x.par" in sage directory for a tuner "xxx-x", such as "Silicondust HDHomeRun Tuner 10106DE2-0.par" for my HDHR tuner Silicondust HDHomeRun Tuner 10106DE2-0, put a line "delay 800" into the file to setup delay 800 ms.

Qian

[bshiek]

Originally Posted by carlgar

bshiek, what version of the HDHR drivers are you using? There was a 20080305 version that I believe could cause the problem. The current version is 20080307.

I should have posted that. I am using 20080226beta1 which had a fix for a Win2k installer problem that I was experiencing. I am upgrading to 20080307, and I will test with that. Thank you for the idea, carlgar!

Qian, I will try the delay, too. Thanks!

[bshiek]

Originally Posted by donkey

we found one kind of "missing recording problem" is caused by the tuning timing/sync issue, which most likely happens on HDHR due to network traffic delay, we added 500 ms delay in default in 6.3.10 for tuning sync, but it may be not enough, you could add more time delay to check by dropping a file "xxxx-x.par" in sage directory for a tuner "xxx-x", such as "Silicondust HDHomeRun Tuner 10106DE2-0.par" for my HDHR tuner Silicondust HDHomeRun Tuner 10106DE2-0, put a line "delay 800" into the file to setup delay 800 ms.

Qian

Are you suggesting I create 2 of these files? One for each tuner on the HDHR?

[donkey]

Originally Posted by bshiek

Are you suggesting I create 2 of these files? One for each tuner on the HDHR?

yes, two files.

[CsquaredIN]

Originally Posted by donkey

we found one kind of "missing recording problem" is caused by the tuning timing/sync issue, which most likely happens on HDHR due to network traffic delay, we added 500 ms delay in default in 6.3.10 for tuning sync, but it may be not enough, you could add more time delay to check by dropping a file "xxxx-x.par" in sage directory for a tuner "xxx-x", such as "Silicondust HDHomeRun Tuner 10106DE2-0.par" for my HDHR tuner Silicondust HDHomeRun Tuner 10106DE2-0, put a line "delay 800" into the file to setup delay 800 ms.

Qian

How do I create a .par file? Do I just use Notepad? Do I one need one line in this file that says "delay 800"? Please forgive me as I'm a little new to all this. I've only been using Sage (6.3.5) and HDHR (20080305) since last week. Every time I record two shows that begin at the same time, I get one show that is missing exactly the first 5 minutes. All other recordings seem to be fine. I updated to 6.3.10 last night, but haven't been able to check how my recordings turned out yet. I assume I still have issues since others are as well. Thanks for your help.

[bshiek]

I created the 2 .par files using a text editor like Notepad with the one line, "delay 800" in both. I also upgraded the HDHR to 20080307. Today's testing worked fine without any problems. I was able to record 2 shows simultaneously. I will continue to test. Thanks!

[timnelsonic]

Sage support suggested the following changes to my sage.properties file:

seeker/fast_mux_switch=false
videoframe/safe_fast_file_switching=false

These seemed to help at first, but I'm still seeing the issue on a daily basis, so I think I just got lucky the day I introduced the changes. Other may want to try these, though, to see if they help them.

Are you people seeing exactly 5 minutes, or some variation less than 5 minutes?

In almost all cases it's exactly 5 minutes, although I've seen 3 minutes a couple of times. I suspect that's a different problem.

[Apap]

I have had this problem on occasion as well but I really have not tried too hard to find the solution.

Narflex might have nailed it in this post.