Unusual Problem

[NetworkGuy]

@EnterNoEscape

This is definitely a different problem:

• Different HDHR Tuner (No errors in tuner log)
• 100% Signal Quality on HDHomeRun
• Non-Premium Station

Logs are attached. Let me know what you see.

Thanks,
John

[EnterNoEscape]

Originally Posted by NetworkGuy

@EnterNoEscape

This is definitely a different problem:

• Different HDHR Tuner (No errors in tuner log)
• 100% Signal Quality on HDHomeRun
• Non-Premium Station

Logs are attached. Let me know what you see.

Thanks,
John

Re-tuning kicked in because stream writing froze for about 45 seconds. You should disable it all together by setting retune_enable=true to false. The reason re-tuning exists is because of the InfiniTV 6 Eth. It is enabled by default and generally doesn't do anything bad, but sometimes you'll see a situation like this where for some reason the share doesn't want to write anything for just long enough to trigger it.

Using a network share likely isn't helping with the latency, but I wouldn't take this as a recommendation to stop doing that. I will share some of my own experience with UNC paths and SageTV. I ran into interesting problems just using local shares so that the SageTV client could see the files for Comskip 5 years ago that led me to change back to not using shares and just mapping the shares with the same drive letters. Of course this is no longer a problem with Comskip since it's now using the API to read the files remotely, but there were also other reasons like latency and reliability that made me realize that this configuration was problematic even with the shares being on the same computer that was running SageTV.

[NetworkGuy]

Originally Posted by EnterNoEscape

Re-tuning kicked in because stream writing froze for about 45 seconds. You should disable it all together by setting retune_enable=true to false. The reason re-tuning exists is because of the InfiniTV 6 Eth. It is enabled by default and generally doesn't do anything bad, but sometimes you'll see a situation like this where for some reason the share doesn't want to write anything for just long enough to trigger it.

I made the change.

Originally Posted by EnterNoEscape

Using a network share likely isn't helping with the latency, but I wouldn't take this as a recommendation to stop doing that. I will share some of my own experience with UNC paths and SageTV. I ran into interesting problems just using local shares so that the SageTV client could see the files for Comskip 5 years ago that led me to change back to not using shares and just mapping the shares with the same drive letters. Of course this is no longer a problem with Comskip since it's now using the API to read the files remotely, but there were also other reasons like latency and reliability that made me realize that this configuration was problematic even with the shares being on the same computer that was running SageTV.

I am only using Network Shares for playback. There should not be anything recording to them. The UNC recording paths (\\SageTV\Recorded TV 1, etc.) are pointing to local disks (d:\Recorded TV1, etc.) on the SageTV server. I am running a drive monitor and it is not showing any error or problems with the disk.

What type of problems are there with using the UNC instead of the local path name for recording?

Thanks Again for the FANTASTIC SUPPORT!

[EnterNoEscape]

Originally Posted by NetworkGuy

I am only using Network Shares for playback. There should not be anything recording to them. The UNC recording paths (\\SageTV\Recorded TV 1, etc.) are pointing to local disks (d:\Recorded TV1, etc.) on the SageTV server. I am running a drive monitor and it is not showing any error or problems with the disk.

What type of problems are there with using the UNC instead of the local path name for recording?

I don't think there's anything wrong with your disks. I think something went wrong with your SMB session and it didn't recover nicely. This is among the problems you can have when using local shares. I used to have things set up just like you're describing when I was having these kinds of problems.

[NetworkGuy]

Originally Posted by EnterNoEscape

I don't think there's anything wrong with your disks. I think something went wrong with your SMB session and it didn't recover nicely. This is among the problems you can have when using local shares. I used to have things set up just like you're describing when I was having these kinds of problems.

I remember why I setup it up this way, to make it easier to create a test system that did not have all of the same hardware. I will convert it back once I upgrade to V9.