OpenDCT: An open source digital cable tuner.

[HokiePerogi]

I can't for the life of me figure out why my ClearQAM tuning of my InfiniTV4 PCIe quit working on me. It seemed to work for the longest time. Now, no bueno. I was fiddling around some last night trying to fix some Phoenix configuration error messages I was seeing.

Once I noticed the issue this morning, I tried installing the latest RC this morning to see if it would resolve my issue, but it did not. My PRIME with CC can tune the channels just fine, but all I get in Sage for ClearQAM channels when using the InfiniTV tuners is a "No signal".

Any thoughts what might be going on?

Thanks.

[Tiki]

Originally Posted by HokiePerogi

I can't for the life of me figure out why my ClearQAM tuning of my InfiniTV4 PCIe quit working on me. It seemed to work for the longest time. Now, no bueno. I was fiddling around some last night trying to fix some Phoenix configuration error messages I was seeing.

Once I noticed the issue this morning, I tried installing the latest RC this morning to see if it would resolve my issue, but it did not. My PRIME with CC can tune the channels just fine, but all I get in Sage for ClearQAM channels when using the InfiniTV tuners is a "No signal".

Any thoughts what might be going on?

Thanks.

I didn't know the Ceton devices did clear QAM.

Are you sure your cable company hasn't made changes? They may have locked those channels down so they are no longer available in the clear. Or they may have remapped them to different frequencies.

I would try connecting a cable directly to a tv with a digital tuner to see what channels it can get.

Also try re-scanning for channels in your Ceton software.

[wayner]

Originally Posted by EnterNoEscape

Any time you are adding a new capture device, make sure both SageTV and OpenDCT are stopped. Make your changes, then start the OpenDCT service again. After that, start the SageTV service. You should now see the new capture device. The key here is that OpenDCT needs to be running before the SageTV service because the SageTV service only broadcasts for network encoder discovery at startup. There's no reason to nuke anything.

So if I stop both services, then start OpenDCT, wait for 30 seconds, start SageTV service, then I should definitely see the new tuners in Sage?

[EnterNoEscape]

Originally Posted by wayner

So if I stop both services, then start OpenDCT, wait for 30 seconds, start SageTV service, then I should definitely see the new tuners in Sage?

Almost certainly.

[EnterNoEscape]

Originally Posted by HokiePerogi

I can't for the life of me figure out why my ClearQAM tuning of my InfiniTV4 PCIe quit working on me. It seemed to work for the longest time. Now, no bueno. I was fiddling around some last night trying to fix some Phoenix configuration error messages I was seeing.

Once I noticed the issue this morning, I tried installing the latest RC this morning to see if it would resolve my issue, but it did not. My PRIME with CC can tune the channels just fine, but all I get in Sage for ClearQAM channels when using the InfiniTV tuners is a "No signal".

Any thoughts what might be going on?

Thanks.

Can you post lineup\qam_infinitv.properties too?

[HokiePerogi]

Originally Posted by EnterNoEscape

Can you post lineup\qam_infinitv.properties too?

As requested. Thanks.

[EnterNoEscape]

Originally Posted by Tiki

I didn't know the Ceton devices did clear QAM.

Are you sure your cable company hasn't made changes? They may have locked those channels down so they are no longer available in the clear. Or they may have remapped them to different frequencies.

I would try connecting a cable directly to a tv with a digital tuner to see what channels it can get.

Also try re-scanning for channels in your Ceton software.

The Ceton software doesn't do any scans that I know of. This is a feature enabled by the use of OpenDCT (MythTV is the only other software I know of that can do this too). What's happening is the modulation isn't being set to an expected value for some reason, so we just need to dig into that. This feature is the reason I started writing OpenDCT.

[wayner]

Originally Posted by EnterNoEscape

Almost certainly.

I just did that but still nothing. By nothing I mean that when I go in my Setup Sources-Add New Source I don't see these http sources. But the opendct log seems to have found them as it says:

11:10:43.312 [GenericHttpLoader-40] DEBUG SageTVManager - The requested capture device 'Kitchen' did not exist. Triggering re-discovery.
11:10:43.312 [GenericHttpLoader-40] DEBUG DynamicConsumerImpl - Using default consumer 'opendct.consumer.FFmpegTransSageTVConsumerImpl' for channel ''
11:10:43.318 [GenericHttpLoader-40] DEBUG SageTVManager - Port 9001 is available.
11:10:43.318 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/tuner1/lockkey' value: 'null' lockKey: '0' sendLength: 26 address: 192.168.1.150
11:10:43.319 [GenericHttpLoader-40] INFO  SageTVManager - The capture device 'Kitchen' is ready.
11:10:43.320 [GenericHttpLoader-40] DEBUG SageTVSocketServer - Setting listening flag...
11:10:43.320 [GenericHttpLoader-40] INFO  SageTVSocketServer - Opening ServerSocket on port 9001...
11:10:43.320 [SageTVTuningMonitor-47] INFO  SageTVTuningMonitor - Tuning monitor thread started.
11:10:43.321 [SageTVSocketServer-48:9001] INFO  SageTVSocketServer - Started listening on port 9001...
11:10:43.325 [WrapperSimpleAppMain] DEBUG WindowsPowerMessagePump - 'class opendct.nanohttpd.NanoHTTPDManager' is now listening.
11:10:43.325 [WrapperSimpleAppMain] DEBUG WindowsPowerMessagePump - 'class opendct.channel.ChannelManager' is now listening.
11:10:43.328 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunDiscovery - HDHomerun device returned an unknown tag with the length 35. This can be ignored.
11:10:43.329 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/sys/hwmodel' value: 'null' lockKey: '0' sendLength: 23 address: 192.168.1.150
11:10:43.331 [WrapperSimpleAppMain] INFO  Main - Running in daemon mode...
11:10:43.338 [HDHomeRunDiscoveryReceive-37] INFO  HDHomeRunDiscoverer - Discovered a new HDHomeRun device 'HDHomeRun HDHR4-2US 1040E3E1' with 2 tuners.
11:10:43.340 [GenericHttpLoader-40] DEBUG DeviceLoaderImpl - Advertising new capture device 'Bedroom'.
11:10:43.340 [GenericHttpLoader-40] DEBUG SageTVManager - The requested capture device 'Bedroom' did not exist. Triggering re-discovery.
11:10:43.340 [GenericHttpLoader-40] DEBUG DynamicConsumerImpl - Using default consumer 'opendct.consumer.FFmpegTransSageTVConsumerImpl' for channel ''
11:10:43.343 [GenericHttpLoader-40] INFO  SageTVManager - The capture device 'Bedroom' is ready.

Is there anything else I can post to help to troubleshoot the issues?

[videolog]

Originally Posted by EnterNoEscape

I didn't actually mean go buy a new hard drive (although new doesn't mean good). Anyway, it looks like everything is ok until tuner 6 starts recording, then things start to get really backed up again. I would be checking things like CPU usage and Resource Monitor to be sure the write queue length for your recording drive is staying at or below 1. Also if you're using Comskip or any other live/post processing programs, turn them off temporarily.

Okay I disabled tuner 6 in case that was a problem. Comskip was disabled so I uninstalled it just to be sure. Had the the error problem around 9 pm. Even after my wife shutoff the HD300 it still showed being recorded on the server. I stopped OpenDCT then restarted it. Reenabled tuner 6 since that didn't seam to make a difference. Noticed I had errors around 3 this morning.
Logs attached. Very weird.

[Fuzzy]

Originally Posted by wayner

I just did that but still nothing. By nothing I mean that when I go in my Setup Sources-Add New Source I don't see these http sources. But the opendct log seems to have found them as it says:

11:10:43.312 [GenericHttpLoader-40] DEBUG SageTVManager - The requested capture device 'Kitchen' did not exist. Triggering re-discovery.
11:10:43.312 [GenericHttpLoader-40] DEBUG DynamicConsumerImpl - Using default consumer 'opendct.consumer.FFmpegTransSageTVConsumerImpl' for channel ''
11:10:43.318 [GenericHttpLoader-40] DEBUG SageTVManager - Port 9001 is available.
11:10:43.318 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/tuner1/lockkey' value: 'null' lockKey: '0' sendLength: 26 address: 192.168.1.150
11:10:43.319 [GenericHttpLoader-40] INFO  SageTVManager - The capture device 'Kitchen' is ready.
11:10:43.320 [GenericHttpLoader-40] DEBUG SageTVSocketServer - Setting listening flag...
11:10:43.320 [GenericHttpLoader-40] INFO  SageTVSocketServer - Opening ServerSocket on port 9001...
11:10:43.320 [SageTVTuningMonitor-47] INFO  SageTVTuningMonitor - Tuning monitor thread started.
11:10:43.321 [SageTVSocketServer-48:9001] INFO  SageTVSocketServer - Started listening on port 9001...
11:10:43.325 [WrapperSimpleAppMain] DEBUG WindowsPowerMessagePump - 'class opendct.nanohttpd.NanoHTTPDManager' is now listening.
11:10:43.325 [WrapperSimpleAppMain] DEBUG WindowsPowerMessagePump - 'class opendct.channel.ChannelManager' is now listening.
11:10:43.328 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunDiscovery - HDHomerun device returned an unknown tag with the length 35. This can be ignored.
11:10:43.329 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/sys/hwmodel' value: 'null' lockKey: '0' sendLength: 23 address: 192.168.1.150
11:10:43.331 [WrapperSimpleAppMain] INFO  Main - Running in daemon mode...
11:10:43.338 [HDHomeRunDiscoveryReceive-37] INFO  HDHomeRunDiscoverer - Discovered a new HDHomeRun device 'HDHomeRun HDHR4-2US 1040E3E1' with 2 tuners.
11:10:43.340 [GenericHttpLoader-40] DEBUG DeviceLoaderImpl - Advertising new capture device 'Bedroom'.
11:10:43.340 [GenericHttpLoader-40] DEBUG SageTVManager - The requested capture device 'Bedroom' did not exist. Triggering re-discovery.
11:10:43.340 [GenericHttpLoader-40] DEBUG DynamicConsumerImpl - Using default consumer 'opendct.consumer.FFmpegTransSageTVConsumerImpl' for channel ''
11:10:43.343 [GenericHttpLoader-40] INFO  SageTVManager - The capture device 'Bedroom' is ready.

Is there anything else I can post to help to troubleshoot the issues?

We would need to see full logs. With both services stopped, start OpenDCT, then start SageTVService. Wait a bit for sage to start up and shut down sage and opendct, and zip up and post the opendct.log and sagetv_0.txt. This should show the discovery process. Log excerpts are not near as helpful.

[wayner]

Is there any info in the sagetv_0.txt log that I should be worried about posting publicly? Like any passwords?

[EnterNoEscape]

Originally Posted by videolog

Okay I disabled tuner 6 in case that was a problem. Comskip was disabled so I uninstalled it just to be sure. Had the the error problem around 9 pm. Even after my wife shutoff the HD300 it still showed being recorded on the server. I stopped OpenDCT then restarted it. Reenabled tuner 6 since that didn't seam to make a difference. Noticed I had errors around 3 this morning.
Logs attached. Very weird.

Try this instead:
1. Stop OpenDCT
2. Change consumer.ffmpeg.upload_id_enabled=true to false
3. Start OpenDCT

I apologize if I told you to turn that on before. I can see you're recording locally, so it should be fine to do it this way.

[videolog]

Originally Posted by EnterNoEscape

Try this instead:
1. Stop OpenDCT
2. Change consumer.ffmpeg.upload_id_enabled=true to false
3. Start OpenDCT

I apologize if I told you to turn that on before. I can see you're recording locally, so it should be fine to do it this way.

Okay I'll give that a shot. Thanks again!

[wayner]

Originally Posted by Fuzzy

We would need to see full logs. With both services stopped, start OpenDCT, then start SageTVService. Wait a bit for sage to start up and shut down sage and opendct, and zip up and post the opendct.log and sagetv_0.txt. This should show the discovery process. Log excerpts are not near as helpful.

Ok, here are my logs

[HokiePerogi]

Originally Posted by EnterNoEscape

The Ceton software doesn't do any scans that I know of. This is a feature enabled by the use of OpenDCT (MythTV is the only other software I know of that can do this too). What's happening is the modulation isn't being set to an expected value for some reason, so we just need to dig into that. This feature is the reason I started writing OpenDCT.

Ahh...okay. Let me know if there are any tests/scenarios you need me to run to try to pinpoint what is happening.

I appreciate the help.

[Fuzzy]

Originally Posted by wayner

Ok, here are my logs

sage's network discovery broadcast is not being received by OpenDCT. Either they are not on the same subnet, a firewall is blocking it, or you have network_encoder_discovery set to false in Sage.properties.

[EnterNoEscape]

Originally Posted by HokiePerogi

Ahh...okay. Let me know if there are any tests/scenarios you need me to run to try to pinpoint what is happening.

I appreciate the help.

Go ahead and delete that lineup file that I told you to post so it rebuilds. I think I see the problem and I'll fix it soon.

[AlphaCrew]

Completed stage 1 of my Sage 7 to Sage 9 upgrade, which of course was swapping out SageDCT with OpenDCT. I really thought this was going to be a disaster, and have been putting it off for months now..

Following Daweeze's directions it seemed like everything went perfectly, so much I made a video on the steps to make it easier for people like me who are visual learners., but I digress..

It appears that I may have a problem. I've been noticing missed shows that should have been picked up by my Infinti4, so I went looking around and found a bunch of OpenDCT crash logs.

It appears that each time sage starts up a crash log is created.

I have attached the crash logs.

EDIT: I have not started the Version 9 upgrade yet.

[EnterNoEscape]

Originally Posted by AlphaCrew

Completed stage 1 of my Sage 7 to Sage 9 upgrade, which of course was swapping out SageDCT with OpenDCT. I really thought this was going to be a disaster, and have been putting it off for months now..

Following Daweeze's directions it seemed like everything went perfectly, so much I made a video on the steps to make it easier for people like me who are visual learners., but I digress..

It appears that I may have a problem. I've been noticing missed shows that should have been picked up by my Infinti4, so I went looking around and found a bunch of OpenDCT crash logs.

It appears that each time sage starts up a crash log is created.

I have attached the crash logs.

EDIT: I have not started the Version 9 upgrade yet.

Your InfiniTV 4 is taking longer than 2 minutes to come back to life after standby. That's a really long time. Try this:

1. Stop the OpenDCT service.
2. Change pm.network.resume_timeout_ms=120000 to a larger value like 240000 in opendct.properties.
3. Start the OpenDCT service.

The default value is 2 minutes (in milliseconds) before the program assumes something has gone wrong and restarts. When that happens, it creates the crash log you posted.

[wayner]

Originally Posted by Fuzzy

sage's network discovery broadcast is not being received by OpenDCT. Either they are not on the same subnet, a firewall is blocking it, or you have network_encoder_discovery set to false in Sage.properties.

Ok, step 1 accomplished - I can now add the two new sources. I must have missed that instruction about network encoders in the guide.

However I don't seem to get a valid stream, when I try to preview the channel I get "Watch request failed. null".

The streaming URL is listed as http\://192.168.1.32/mjpeg.cgi. Is that correct with the extra backslash? Or should the URL not include http://? Or do I need an executable of some sort as an intermediary?

It also appears that both IP cameras are trying to use port 9001. Should I be changing one of them?

Here is the opendct.log

18:38:29.701 [WrapperSimpleAppMain] INFO  Main - Starting OpenDCT 0.5.21...
18:38:29.708 [WrapperSimpleAppMain] DEBUG Config - OSVersion determined that 'Windows 8.1' is WINDOWS.
18:38:29.726 [WrapperSimpleAppMain] INFO  Main - OpenDCT logging to the directory 'c:/ProgramData/OpenDCT/logs'.
18:38:29.729 [WrapperSimpleAppMain] INFO  UpnpManager - Logging Cling UPnP to 'c:/ProgramData/OpenDCT/logs\opendct_cling.log'.
18:38:29.729 [WrapperSimpleAppMain] DEBUG UpnpManager - Logging level for Cling UPnP is set to 'severe'.
18:38:29.729 [FFmpegAsyncInit-20] INFO  Main - FFmpeg loading...
18:38:29.731 [FFmpegAsyncInit-20] DEBUG FFmpegUtil - Initializing FFmpegLogger...
18:38:29.810 [WindowsPowerMessagePump] INFO  WindowsPowerMessagePump - Message pump started.
18:38:29.832 [FFmpegAsyncInit-20] DEBUG FFmpegUtil - Calling av_log_set_callback...
18:38:29.832 [FFmpegAsyncInit-20] DEBUG FFmpegUtil - Calling avcodec_register_all...
18:38:30.740 [FFmpegAsyncInit-20] DEBUG FFmpegUtil - Calling avfilter_register_all...
18:38:31.401 [FFmpegAsyncInit-20] DEBUG FFmpegUtil - Calling av_register_all...
18:38:31.401 [FFmpegAsyncInit-20] INFO  Main - FFmpeg loaded in 1672ms.
18:38:34.759 [WrapperSimpleAppMain] INFO  NetworkPowerEventManger - Network interfaces which are up and have an IP4 address are: 
name:eth5 (Intel(R) Ethernet Connection (2) I219-V) 192.168.1.98
18:38:34.759 [WrapperSimpleAppMain] DEBUG WindowsPowerMessagePump - 'class opendct.power.NetworkPowerEventManger' is now listening.
18:38:34.760 [WrapperSimpleAppMain] DEBUG WindowsPowerMessagePump - 'class opendct.sagetv.SageTVManager' is now listening.
18:38:34.763 [DynamicAsyncInit-20] INFO  DynamicConsumerImpl - Dynamic consumer default set to use opendct.consumer.FFmpegTransSageTVConsumerImpl
18:38:34.763 [DynamicAsyncInit-20] INFO  DynamicConsumerImpl - Dynamic consumer set to use opendct.consumer.FFmpegTransSageTVConsumerImpl for []
18:38:34.763 [DynamicAsyncInit-20] INFO  DynamicConsumerImpl - Dynamic consumer set to use opendct.consumer.MediaServerConsumerImpl for []
18:38:34.763 [DynamicAsyncInit-20] INFO  DynamicConsumerImpl - Dynamic consumer set to use opendct.consumer.RawSageTVConsumerImpl for []
18:38:37.082 [WrapperSimpleAppMain] INFO  UpnpManager - Starting UPnP services...
18:38:37.113 [WrapperSimpleAppMain] INFO  DCTDefaultUpnpServiceConfiguration - Using the interface 'eth5' with IP address 192.168.1.98 for UPnP discovery.
18:38:37.125 [WrapperSimpleAppMain] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
18:38:37.130 [UPnPDiscovery-36] INFO  UpnpManager - UPnP discovery thread has started.
18:38:37.151 [HDHomeRunDiscoverySend-37] INFO  HDHomeRunDiscovery - HDHomeRun discovery sender thread started.
18:38:37.151 [HDHomeRunDiscoveryReceive-37] INFO  HDHomeRunDiscovery - HDHomeRun discovery receive thread for /192.168.1.255:65001 broadcast started.
18:38:37.151 [WrapperSimpleAppMain] DEBUG WindowsPowerMessagePump - 'class opendct.tuning.discovery.DiscoveryManager' is now listening.
18:38:37.152 [HDHomeRunDiscoverySend-37] INFO  HDHomeRunDiscovery - Broadcasting HDHomeRun discovery packet to /192.168.1.255:65001... (startup)
18:38:37.152 [WrapperSimpleAppMain] INFO  NanoHTTPDManager - Starting webserver on port 9091...
18:38:37.154 [GenericHttpLoader-40] DEBUG DeviceLoaderImpl - Advertising new capture device 'Kitchen'.
18:38:37.156 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/tuner0/lockkey' value: 'null' lockKey: '0' sendLength: 26 address: 192.168.1.150
18:38:37.156 [GenericHttpLoader-40] DEBUG SageTVManager - The requested capture device 'Kitchen' did not exist. Triggering re-discovery.
18:38:37.156 [GenericHttpLoader-40] DEBUG DynamicConsumerImpl - Using default consumer 'opendct.consumer.FFmpegTransSageTVConsumerImpl' for channel ''
18:38:37.161 [GenericHttpLoader-40] DEBUG SageTVManager - Port 9001 is available.
18:38:37.162 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/tuner1/lockkey' value: 'null' lockKey: '0' sendLength: 26 address: 192.168.1.150
18:38:37.163 [GenericHttpLoader-40] INFO  SageTVManager - The capture device 'Kitchen' is ready.
18:38:37.164 [GenericHttpLoader-40] DEBUG SageTVSocketServer - Setting listening flag...
18:38:37.164 [GenericHttpLoader-40] INFO  SageTVSocketServer - Opening ServerSocket on port 9001...
18:38:37.164 [SageTVTuningMonitor-47] INFO  SageTVTuningMonitor - Tuning monitor thread started.
18:38:37.164 [SageTVSocketServer-48:9001] INFO  SageTVSocketServer - Started listening on port 9001...
18:38:37.169 [WrapperSimpleAppMain] DEBUG WindowsPowerMessagePump - 'class opendct.nanohttpd.NanoHTTPDManager' is now listening.
18:38:37.169 [WrapperSimpleAppMain] DEBUG WindowsPowerMessagePump - 'class opendct.channel.ChannelManager' is now listening.
18:38:37.169 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunDiscovery - HDHomerun device returned an unknown tag with the length 35. This can be ignored.
18:38:37.171 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/sys/hwmodel' value: 'null' lockKey: '0' sendLength: 23 address: 192.168.1.150
18:38:37.175 [WrapperSimpleAppMain] INFO  Main - Running in daemon mode...
18:38:37.180 [HDHomeRunDiscoveryReceive-37] INFO  HDHomeRunDiscoverer - Discovered a new HDHomeRun device 'HDHomeRun HDHR4-2US 1040E3E1' with 2 tuners.
18:38:37.184 [GenericHttpLoader-40] DEBUG DeviceLoaderImpl - Advertising new capture device 'Bedroom'.
18:38:37.184 [GenericHttpLoader-40] DEBUG SageTVManager - The requested capture device 'Bedroom' did not exist. Triggering re-discovery.
18:38:37.184 [GenericHttpLoader-40] DEBUG DynamicConsumerImpl - Using default consumer 'opendct.consumer.FFmpegTransSageTVConsumerImpl' for channel ''
18:38:37.186 [GenericHttpLoader-40] INFO  SageTVManager - The capture device 'Bedroom' is ready.
18:38:37.205 [HDHomeRunDiscoveryReceive-37] DEBUG DeviceLoaderImpl - Advertising new capture device 'HDHomeRun HDHR4-2US Tuner 1040E3E1-0'.
18:38:37.207 [HDHomeRunDiscoveryReceive-37] DEBUG SageTVManager - The requested capture device 'HDHomeRun HDHR4-2US Tuner 1040E3E1-0' did not exist. Triggering re-discovery.
18:38:37.207 [HDHomeRunDiscoveryReceive-37] INFO  BasicCaptureDevice - Skipping capture device 'HDHomeRun HDHR4-2US Tuner 1040E3E1-0' because it is on the ignore list.
18:38:37.208 [HDHomeRunDiscoveryReceive-37] WARN  HDHomeRunDiscoverer - Capture device will not be loaded => Capture device cannot be loaded because it is on the ignore list.
18:38:37.208 [HDHomeRunDiscoveryReceive-37] ERROR DeviceLoaderImpl - The capture device 'HDHomeRun HDHR4-2US Tuner 1040E3E1-0' did not load.
18:38:37.208 [HDHomeRunDiscoveryReceive-37] DEBUG DeviceLoaderImpl - Advertising new capture device 'HDHomeRun HDHR4-2US Tuner 1040E3E1-1'.
18:38:37.208 [HDHomeRunDiscoveryReceive-37] DEBUG SageTVManager - The requested capture device 'HDHomeRun HDHR4-2US Tuner 1040E3E1-1' did not exist. Triggering re-discovery.
18:38:37.208 [HDHomeRunDiscoveryReceive-37] INFO  BasicCaptureDevice - Skipping capture device 'HDHomeRun HDHR4-2US Tuner 1040E3E1-1' because it is on the ignore list.
18:38:37.208 [HDHomeRunDiscoveryReceive-37] WARN  HDHomeRunDiscoverer - Capture device will not be loaded => Capture device cannot be loaded because it is on the ignore list.
18:38:37.208 [HDHomeRunDiscoveryReceive-37] ERROR DeviceLoaderImpl - The capture device 'HDHomeRun HDHR4-2US Tuner 1040E3E1-1' did not load.
18:38:37.353 [HDHomeRunDiscoverySend-37] INFO  HDHomeRunDiscovery - Broadcasting HDHomeRun discovery packet to /192.168.1.255:65001... (requested)
18:38:37.354 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/tuner0/lockkey' value: 'null' lockKey: '0' sendLength: 26 address: 192.168.1.150
18:38:37.363 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/tuner1/lockkey' value: 'null' lockKey: '0' sendLength: 26 address: 192.168.1.150
18:38:37.373 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunDiscovery - HDHomerun device returned an unknown tag with the length 35. This can be ignored.
18:38:37.553 [HDHomeRunDiscoverySend-37] INFO  HDHomeRunDiscovery - Broadcasting HDHomeRun discovery packet to /192.168.1.255:65001... (startup)
18:38:37.554 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/tuner0/lockkey' value: 'null' lockKey: '0' sendLength: 26 address: 192.168.1.150
18:38:37.566 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/tuner1/lockkey' value: 'null' lockKey: '0' sendLength: 26 address: 192.168.1.150
18:38:37.575 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunDiscovery - HDHomerun device returned an unknown tag with the length 35. This can be ignored.
18:38:37.754 [HDHomeRunDiscoverySend-37] INFO  HDHomeRunDiscovery - Broadcasting HDHomeRun discovery packet to /192.168.1.255:65001... (startup)
18:38:37.755 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/tuner0/lockkey' value: 'null' lockKey: '0' sendLength: 26 address: 192.168.1.150
18:38:37.759 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunControl - key: '/tuner1/lockkey' value: 'null' lockKey: '0' sendLength: 26 address: 192.168.1.150
18:38:37.769 [HDHomeRunDiscoveryReceive-37] DEBUG HDHomeRunDiscovery - HDHomerun device returned an unknown tag with the length 35. This can be ignored.
18:38:41.131 [UPnPDiscovery-36] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
18:38:45.132 [UPnPDiscovery-36] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
18:38:49.132 [UPnPDiscovery-36] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
18:38:53.133 [UPnPDiscovery-36] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
18:38:57.133 [UPnPDiscovery-36] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
18:39:01.134 [UPnPDiscovery-36] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
18:39:05.135 [UPnPDiscovery-36] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
18:39:09.135 [UPnPDiscovery-36] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
18:39:09.135 [UPnPDiscovery-36] DEBUG UpnpManager - Stopping broadcast.
18:39:09.135 [UPnPDiscovery-36] DEBUG DiscoveryRegistryListener - Before shutdown, the registry has 3 device(s).
18:39:09.135 [UPnPDiscovery-36] DEBUG DiscoveryRegistryListener - Shutdown of UPnP registry complete.
18:39:15.148 [UPnPDiscovery-36] DEBUG UpnpManager - Broadcast requested.
18:39:15.166 [UPnPDiscovery-36] INFO  DCTDefaultUpnpServiceConfiguration - Using the interface 'eth5' with IP address 192.168.1.98 for UPnP discovery.
18:39:19.168 [UPnPDiscovery-36] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
18:39:23.169 [UPnPDiscovery-36] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
18:39:26.310 [SageTVSocketServer-48:9001] WARN  SageTVSocketServer - IPv6 connection detected. This is an untested configuration.
18:39:27.169 [UPnPDiscovery-36] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
18:39:31.170 [UPnPDiscovery-36] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
18:39:35.171 [UPnPDiscovery-36] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
18:39:39.171 [UPnPDiscovery-36] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
18:39:43.172 [UPnPDiscovery-36] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
18:39:47.173 [UPnPDiscovery-36] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
18:39:47.173 [UPnPDiscovery-36] DEBUG UpnpManager - Stopping broadcast.
18:39:47.173 [UPnPDiscovery-36] WARN  DiscoveryRegistryListener - Before UPnP shutdown, the registry did not contain any devices.
18:39:47.173 [UPnPDiscovery-36] DEBUG DiscoveryRegistryListener - Shutdown of UPnP registry complete.
18:40:02.051 [SageTVRequestHandler-73:Unknown] DEBUG SageTVRequestHandler - SageTV sent: 'START Bedroom HDMI|266592774|1|2968356004100|\\brora\tv\639600969_1_0111_1840-0.ts|Great-H.264'
18:40:02.051 [SageTVRequestHandler-73:Bedroom] DEBUG GenericHttpCaptureDevice - Capture device is now re-locked.
18:40:02.051 [SageTVRequestHandler-73:Bedroom] DEBUG SageTVRequestHandler - Starting network encoder via upload ID '266592774' to file name '\\brora\tv\639600969_1_0111_1840-0.ts'.
18:40:02.051 [SageTVRequestHandler-73:Bedroom] DEBUG BasicCaptureDevice - Consumer is was not in progress.
18:40:02.052 [SageTVRequestHandler-73:Bedroom] DEBUG DynamicConsumerImpl - Using default consumer 'opendct.consumer.FFmpegTransSageTVConsumerImpl' for channel '1'
18:40:02.055 [SageTVRequestHandler-73:Bedroom] INFO  GenericHttpCaptureDevice - Starting the encoding for the channel '1' from the device 'Bedroom' to the file '\\brora\tv\639600969_1_0111_1840-0.ts'...
18:40:02.055 [SageTVRequestHandler-73:Bedroom] INFO  GenericHttpCaptureDevice - Configuring and starting the new SageTV producer...
18:40:02.055 [SageTVRequestHandler-73:Bedroom] INFO  NIOHTTPProducerImpl - Connecting to source using the URL 'http://192.168.1.31/mjpeg.cgi'
18:40:02.055 [SageTVRequestHandler-73:Bedroom] INFO  NIOHTTPProducerImpl - Connecting with credentials.
18:40:02.078 [SageTVRequestHandler-73:Bedroom] DEBUG NIOHttpDownloader - HTTP response: 'HTTP/1.0 401 Authorization Required', 'Server: alphapd', 'Date: Wed Jan 11 18:40:00 2017', 'Pragma: no-cache', 'Cache-Control: no-cache', 'Content-type: text/html', 'WWW-Authenticate: Basic realm="TV-IP651WI"', 
18:40:02.078 [SageTVRequestHandler-73:Bedroom] INFO  GenericHttpCaptureDevice - Configuring and starting the new SageTV consumer...
18:40:02.078 [NIOHTTPProducerImpl-74:Bedroom] INFO  NIOHTTPProducerImpl - Producer thread is running.
18:40:02.078 [NIOHTTPProducerImpl-74:Bedroom] DEBUG NIOHTTPProducerImpl - Thread priority is 9.
18:40:02.078 [NIOHTTPProducerImpl-74:Bedroom] INFO  NIOHTTPProducerImpl - We have reached the end of the stream. Stopping thread.
18:40:02.078 [NIOHTTPProducerImpl-74:Bedroom] INFO  NIOHTTPProducerImpl - Producer thread has stopped.
18:40:02.080 [SageTVRequestHandler-73:Bedroom] DEBUG BasicCaptureDevice - Consumer is was not in progress.
18:40:02.081 [FFmpegTransSageTVConsumerImpl-76:Bedroom] INFO  FFmpegTransSageTVConsumerImpl - FFmpeg Transcoder consumer thread is now running.
18:40:02.081 [FFmpegTransSageTVConsumerImpl-76:Bedroom] DEBUG FFmpegTransSageTVConsumerImpl - Thread priority is 8.
18:40:02.088 [FFmpegTransSageTVConsumerImpl-76:Bedroom] DEBUG FFmpegStreamDetection - Calling avformat_open_input
18:40:02.590 [FFmpegTransSageTVConsumerImpl-76:Bedroom] INFO  FFmpegContext - Returning AVERROR_EOF in readCallback.call()
18:40:03.111 [FFmpegTransSageTVConsumerImpl-76:Bedroom] INFO  FFmpegContext - Returning AVERROR_EOF in readCallback.call()
18:40:03.612 [FFmpegTransSageTVConsumerImpl-76:Bedroom] INFO  FFmpegContext - Returning AVERROR_EOF in readCallback.call()
18:40:03.612 [FFmpegTransSageTVConsumerImpl-76:Bedroom] ERROR FFmpegContext - initTsStream: avformat_open_input returned error code -1094995529
18:40:03.612 [FFmpegTransSageTVConsumerImpl-76:Bedroom] DEBUG FFmpegStreamDetection - Calling avformat_open_input
18:40:04.114 [FFmpegTransSageTVConsumerImpl-76:Bedroom] INFO  FFmpegContext - Returning AVERROR_EOF in readCallback.call()
18:40:04.615 [FFmpegTransSageTVConsumerImpl-76:Bedroom] INFO  FFmpegContext - Returning AVERROR_EOF in readCallback.call()
18:40:05.116 [FFmpegTransSageTVConsumerImpl-76:Bedroom] INFO  FFmpegContext - Returning AVERROR_EOF in readCallback.call()
18:40:05.116 [FFmpegTransSageTVConsumerImpl-76:Bedroom] ERROR FFmpegContext - initTsStream: avformat_open_input returned error code -1094995529
18:40:07.171 [ChannelManager-50] INFO  ChannelManager - The static channel lineup Kitchen (generic_http) will remain unchanged.
18:40:07.171 [ChannelManager-50] INFO  ChannelManager - Updating the HDHomeRun channel lineup HDHomeRun HDHR4-2US 1040E3E1 (atsc_hdhomerun_1040e3e1).
18:40:07.172 [ChannelManager-50] INFO  HDHomeRunChannels - Connecting to HDHomeRun using the URL 'http://192.168.1.150:80/lineup.xml'
18:40:15.123 [FFmpegTransSageTVConsumerImpl-76:Bedroom] DEBUG FFmpegStreamDetection - Calling avformat_open_input
18:40:15.624 [FFmpegTransSageTVConsumerImpl-76:Bedroom] INFO  FFmpegContext - Returning AVERROR_EOF in readCallback.call()
18:40:16.126 [FFmpegTransSageTVConsumerImpl-76:Bedroom] INFO  FFmpegContext - Returning AVERROR_EOF in readCallback.call()
18:40:16.627 [FFmpegTransSageTVConsumerImpl-76:Bedroom] INFO  FFmpegContext - Returning AVERROR_EOF in readCallback.call()
18:40:16.627 [FFmpegTransSageTVConsumerImpl-76:Bedroom] ERROR FFmpegContext - initTsStream: avformat_open_input returned error code -1094995529
18:40:16.627 [FFmpegTransSageTVConsumerImpl-76:Bedroom] INFO  FFmpegTransSageTVConsumerImpl - Unable to detect any video.
18:40:16.627 [AsyncWriter-75:639600969_1_0111_1840-0.ts] INFO  FFmpegTransSageTVConsumerImpl - Closing the file '\\brora\tv\639600969_1_0111_1840-0.ts'
18:40:17.082 [SageTVRequestHandler-73:Bedroom] DEBUG SageTVRequestHandler - Replied: 'OK'
18:40:17.082 [SageTVRequestHandler-73:Bedroom] DEBUG SageTVRequestHandler - An unhandled exception was created => java.net.SocketException: Software caused connection abort: recv failed
	at java.net.SocketInputStream.socketRead0(Native Method)
	at java.net.SocketInputStream.read(Unknown Source)
	at java.net.SocketInputStream.read(Unknown Source)
	at sun.nio.cs.StreamDecoder.readBytes(Unknown Source)
	at sun.nio.cs.StreamDecoder.implRead(Unknown Source)
	at sun.nio.cs.StreamDecoder.read(Unknown Source)
	at java.io.InputStreamReader.read(Unknown Source)
	at java.io.BufferedReader.fill(Unknown Source)
	at java.io.BufferedReader.readLine(Unknown Source)
	at java.io.BufferedReader.readLine(Unknown Source)
	at opendct.sagetv.SageTVRequestHandler.run(SageTVRequestHandler.java:127)
	at java.lang.Thread.run(Unknown Source)

18:40:17.127 [FFmpegTransSageTVConsumerImpl-76:Bedroom] INFO  FFmpegTransSageTVConsumerImpl - FFmpeg Transcoder consumer thread stopped.
18:40:19.505 [SageTVRequestHandler-77:Unknown] DEBUG SageTVRequestHandler - SageTV sent: 'STOP Bedroom HDMI'
18:40:19.505 [SageTVRequestHandler-77:Bedroom] DEBUG GenericHttpCaptureDevice - Stopping encoding...
18:40:19.505 [SageTVRequestHandler-77:Bedroom] DEBUG BasicCaptureDevice - Consumer is was not in progress.
18:40:19.506 [SageTVRequestHandler-77:Bedroom] DEBUG GenericHttpCaptureDevice - Capture device is now re-unlocked.
18:40:19.506 [SageTVRequestHandler-77:Bedroom] DEBUG SageTVRequestHandler - Replied: 'OK'
18:40:19.506 [StoppingThread-79] DEBUG GenericHttpCaptureDevice - Stopping executable will be run in 15000 milliseconds.

What else can I do to try to fix? Should I try turning off passwords on my IP cam to see if it is an authentication issue?