OpenDCT: An open source digital cable tuner.

[EnterNoEscape]

Originally Posted by stanger89

What does this mean? Setup the tuner(s) in OpenDCT, and then in Sage do a Channel scan and remap? I believe I tried that but I'll have to try again.

For what it's worth I get a "good" lineup from the HDHR via lineup.xml (if I grab it manually), as in I get real channel numbers. At some point "recently" my provider started providing the logical channel numbers in the PSIP (I believe) data, at least in such a way that the HDHR software would recognize them.

I'm just talking about the native HDHomeRun support in SageTV (nothing to do with OpenDCT), but I see you're trying to see if OpenDCT can handle a channel better than the built in support. If you wouldn't mind sharing your XML file, I might be able to work something new into OpenDCT. I didn't know that some providers might actually give you the right channels without a CableCARD.

[matt91]

Originally Posted by nyplayer

out of curiosity do you have this property ... also I recommend pooling if you are not using it
always_force_external_unlock=true

I set that to true and it makes sure it takes the tuner forcibly if it needs to .... works great

OK, thanks. I'll check. I have whatever the default install provides for. I haven't touched anything in the config file.

[EnterNoEscape]

Originally Posted by matt91

Hi -

I'm still getting some occasional missed recordings, including at 2100 [Chicago Med] last night. The show at 2200 [Chicago Fire] on the same channel (804) recorded OK, so I'm not sure what's up. (there are a few other shows that recorded last night too, but I honestly didn't notice if they did or didn't record - and I'm at work now and can't confirm.)

Is there anything telling in here? I can post the sagetv_0 log once I get home if that is needed.

thanks again for any help.

edit: I'm running 0.5.0 beta

What I just saw in your log is something I've seen a few times when people had very similar issues. Basically FFmpeg trails off on detection not really getting anywhere, but for whatever reason it never returns. It's always been a little strange to me that when I tell it to only probe x number of bytes, it typically comes back saying it probed 3x that. I've been working on a way to figure out when this is happening, so the detection will be restarted when it's being unresponsive, but I'm still tweaking things to get a good balance between fixing problems reasonably fast and not intervening too early.

I also noticed that the buffer expanded crazy fast. Less than 200ms, and the buffer already needed to double in size. I saw something like this happen on my production server while I was messing around with the InfiniTV tuner. I somehow got it into a state that it would do exactly what your buffer did, but it would do it for any channel I tuned into including if I was trying to tune in using an HDHomeRun which I would have assumed would be unaffected especially since it's not a UDP connection. Restarting the OpenDCT service did not help. The problem persisted until I rebooted the InfiniTV tuner. I didn't think to open up Wireshark, but it at least appeared that the InfiniTV tuner was somehow spewing garbage into everything related to networking including TCP connections. I was trying to think of a way to detect this kind of situation and possibly try to tolerate/fix it. I'm not sure if this gives anyone any ideas, but I just thought I'd share my experience.

[stanger89]

Originally Posted by EnterNoEscape

I'm just talking about the native HDHomeRun support in SageTV (nothing to do with OpenDCT), but I see you're trying to see if OpenDCT can handle a channel better than the built in support. If you wouldn't mind sharing your XML file, I might be able to work something new into OpenDCT. I didn't know that some providers might actually give you the right channels without a CableCARD.

Sorry, I think we're confusing each other, I might have provided too much info.

What I'm really trying to solve is how to setup OpenDCT with ClearQAM. I thought I followed the instructions, but when I go to view something I just get a black screen.

Here's what I'm seeing in the log:

16:04:26.435 [SageTVRequestHandler-3941:Unknown] DEBUG SageTVRequestHandler - SageTV sent: 'START DCT-HDHomeRun Prime Tuner 13139E6D-2 Digital TV Tuner|1607990423|886|2922372532864|F:\AmericanPickers-YouBetcha-18514436-1.ts|Great'
16:04:26.435 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] INFO  HDHRNativeCaptureDevice - Capture device is now locked.
16:04:26.435 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG SageTVRequestHandler - Starting network encoder to file name 'F:\AmericanPickers-YouBetcha-18514436-1.ts'.
16:04:26.435 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] INFO  HDHRNativeCaptureDevice - Starting the encoding for the channel '886' from the device 'DCT-HDHomeRun Prime Tuner 13139E6D-2' to the file 'F:\AmericanPickers-YouBetcha-18514436-1.ts'...
16:04:26.443 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'null' lockKey: '0' sendLength: 26
16:04:26.443 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: '1062731684' lockKey: '1062731684' sendLength: 45
16:04:26.443 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] INFO  HDHRNativeCaptureDevice - HDHomeRun is now locked.
16:04:26.443 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG RTPCaptureDeviceServices - Producer was not running.
16:04:26.443 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG BasicCaptureDevice - Consumer is was not in progress.
16:04:26.443 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] ERROR HDHRNativeCaptureDevice - The channel '886' does not have a frequency on the lineup 'qam_hdhomerun_13139e6d'.
16:04:26.443 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] ERROR SageTVRequestHandler - SageTV sent: 'START DCT-HDHomeRun Prime Tuner 13139E6D-2 Digital TV Tuner|1607990423|886|2922372532864|F:\AmericanPickers-YouBetcha-18514436-1.ts|Great', Replied: 'ERROR Device Start Failed'
16:04:26.443 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] ERROR SageTVRequestHandler - Encoder device is unable to start.
16:04:40.084 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG SageTVRequestHandler - SageTV sent: 'STOP DCT-HDHomeRun Prime Tuner 13139E6D-2 Digital TV Tuner'
16:04:40.084 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHRNativeCaptureDevice - Stopping encoding...
16:04:40.084 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG RTPCaptureDeviceServices - Producer was not running.
16:04:40.084 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG BasicCaptureDevice - Consumer is was not in progress.
16:04:40.084 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/channel' value: 'none' lockKey: '1062731684' sendLength: 39
16:04:40.084 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/target' value: 'none' lockKey: '1062731684' sendLength: 38
16:04:40.092 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'null' lockKey: '0' sendLength: 26
16:04:40.092 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'none' lockKey: '1062731684' sendLength: 39
16:04:40.092 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'null' lockKey: '0' sendLength: 26
16:04:40.092 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] INFO  HDHRNativeCaptureDevice - HDHomeRun is now unlocked.
16:04:40.092 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] INFO  HDHRNativeCaptureDevice - Capture device is now unlocked.
16:04:40.092 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG SageTVRequestHandler - Replied: 'OK'

And here's what the XML looks like for that channel:

<Program><GuideNumber>886</GuideNumber><GuideName>886_His</GuideName><HD>1</HD><URL>http://192.168.0.8:5004/auto/v886</URL></Program>

Here's what the lineup .properties file has for that channel:

channel.0886=886,,true,886_His,http\://192.168.0.8\:5004/auto/v886,,-1,,,0,UNKNOWN,false

[EnterNoEscape]

Originally Posted by stanger89

Sorry, I think we're confusing each other, I might have provided too much info.

What I'm really trying to solve is how to setup OpenDCT with ClearQAM. I thought I followed the instructions, but when I go to view something I just get a black screen.

Here's what I'm seeing in the log:

16:04:26.435 [SageTVRequestHandler-3941:Unknown] DEBUG SageTVRequestHandler - SageTV sent: 'START DCT-HDHomeRun Prime Tuner 13139E6D-2 Digital TV Tuner|1607990423|886|2922372532864|F:\AmericanPickers-YouBetcha-18514436-1.ts|Great'
16:04:26.435 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] INFO  HDHRNativeCaptureDevice - Capture device is now locked.
16:04:26.435 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG SageTVRequestHandler - Starting network encoder to file name 'F:\AmericanPickers-YouBetcha-18514436-1.ts'.
16:04:26.435 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] INFO  HDHRNativeCaptureDevice - Starting the encoding for the channel '886' from the device 'DCT-HDHomeRun Prime Tuner 13139E6D-2' to the file 'F:\AmericanPickers-YouBetcha-18514436-1.ts'...
16:04:26.443 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'null' lockKey: '0' sendLength: 26
16:04:26.443 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: '1062731684' lockKey: '1062731684' sendLength: 45
16:04:26.443 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] INFO  HDHRNativeCaptureDevice - HDHomeRun is now locked.
16:04:26.443 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG RTPCaptureDeviceServices - Producer was not running.
16:04:26.443 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG BasicCaptureDevice - Consumer is was not in progress.
16:04:26.443 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] ERROR HDHRNativeCaptureDevice - The channel '886' does not have a frequency on the lineup 'qam_hdhomerun_13139e6d'.
16:04:26.443 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] ERROR SageTVRequestHandler - SageTV sent: 'START DCT-HDHomeRun Prime Tuner 13139E6D-2 Digital TV Tuner|1607990423|886|2922372532864|F:\AmericanPickers-YouBetcha-18514436-1.ts|Great', Replied: 'ERROR Device Start Failed'
16:04:26.443 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] ERROR SageTVRequestHandler - Encoder device is unable to start.
16:04:40.084 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG SageTVRequestHandler - SageTV sent: 'STOP DCT-HDHomeRun Prime Tuner 13139E6D-2 Digital TV Tuner'
16:04:40.084 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHRNativeCaptureDevice - Stopping encoding...
16:04:40.084 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG RTPCaptureDeviceServices - Producer was not running.
16:04:40.084 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG BasicCaptureDevice - Consumer is was not in progress.
16:04:40.084 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/channel' value: 'none' lockKey: '1062731684' sendLength: 39
16:04:40.084 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/target' value: 'none' lockKey: '1062731684' sendLength: 38
16:04:40.092 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'null' lockKey: '0' sendLength: 26
16:04:40.092 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'none' lockKey: '1062731684' sendLength: 39
16:04:40.092 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'null' lockKey: '0' sendLength: 26
16:04:40.092 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] INFO  HDHRNativeCaptureDevice - HDHomeRun is now unlocked.
16:04:40.092 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] INFO  HDHRNativeCaptureDevice - Capture device is now unlocked.
16:04:40.092 [SageTVRequestHandler-3941:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG SageTVRequestHandler - Replied: 'OK'

And here's what the XML looks like for that channel:

<Program><GuideNumber>886</GuideNumber><GuideName>886_His</GuideName><HD>1</HD><URL>http://192.168.0.8:5004/auto/v886</URL></Program>

Here's what the lineup .properties file has for that channel:

channel.0886=886,,true,886_His,http\://192.168.0.8\:5004/auto/v886,,-1,,,0,UNKNOWN,false

Wow, that's pretty nice. I wish my provider actually numbered my ClearQAM channels like that. You ended up with exactly what I expected. I'll make an option for people that don't need to remap their channels in the next 0.5 beta. Unfortunately right now having the frequency and program defined are required for ClearQAM because there's an assumption that the channel number can't be relied on. Hopefully I'll have that out soon.

[Toddly]

I took the plunge and installed Open DCT but I get halts when trying view live tv or record a program. I have been reading this thread in the hope of getting a solution.

Setup went well and HDHomerun Prime was detected and I set up the channels.
I can view the video in the preview pane in the channel setup but when I exit and try view live tv I get the recording errors.

I'm not sure how to read the logs properly to determine where my problem lies. Any help would be appreciated.

[EnterNoEscape]

Originally Posted by Toddly

I took the plunge and installed Open DCT but I get halts when trying view live tv or record a program. I have been reading this thread in the hope of getting a solution.

Setup went well and HDHomerun Prime was detected and I set up the channels.
I can view the video in the preview pane in the channel setup but when I exit and try view live tv I get the recording errors.

I'm not sure how to read the logs properly to determine where my problem lies. Any help would be appreciated.

There's another thread where the issue sounds little like what you're describing. Basically what you'll want to try is start a recording, then try to watch it after it has been recording for about 30 seconds. If this isn't the issue, you can post a log with the problem in it, I might be able to get you in the right direction.

[EnterNoEscape]

• CONFIGURATION UPGRADE: The first time you run this version, it will upgrade your current configuration. Anything still referencing FFmpegSageTVConsumerImpl will be changed over to DynamicConsumerImpl. This will not change anything set to FFmpegTransSageTVConsumerImpl. hdhr.wait_for_streaming and upnp.dct.wait_for_streaming will be changed to 15000.
• Renamed FFmpegSageTVConsumerImpl to FFmpegOldSageTVConsumerImpl to force old installations to use the newer remuxer unless explicitly set otherwise.
• Fixed DynamicConsumerImpl not populating the sagetv.device.<unique_id>.consumer properties if the property did not already exist.
• Changed startup and resume from standby to not rely on a known number of capture devices. It will now check every time a new capture device is loaded to see if it's the one SageTV is requesting until the required devices timeout (sagetv.device.global.required_devices_loaded_timeout_ms). This should also result in faster resume tuning times since the program no longer needs to wait for all required devices to be loaded.
• Increased wait for response from InfiniTV devices to 10 seconds.
• Amount of data required to be written before returning OK to SageTV is now based on how much was needed for FFmpeg to detect the streams.
• Added some FFmpeg optimizations to ensure that a key video frame is at the very start of the container when possible. This appears to provide additional assurance so that MPEG-PS files are detected correctly.
• File growth monitoring is now more aggressive.
• Added some extra logging to tuning monitor.
• Fixed reading from buffer potentially getting stuck during detection.
• Added new option to disable HDHomeRun ClearQAM remapping and frequency/program verification for configuration without a reference tuner with a CableCARD installed. To disable the remapping feature, change the value of hdhr.allow_qam_remapping to false.

[EnterNoEscape]

stanger89,

You will want to install 0.5.1 and change the value of hdhr.allow_qam_remapping to false, then you should be able to use your HDHomeRun Prime without a CableCARD installed. OpenDCT will assume the channel numbers do not need to be remapped.

[nyplayer]

Originally Posted by EnterNoEscape

• CONFIGURATION UPGRADE: The first time you run this version, it will upgrade your current configuration. Anything still referencing FFmpegSageTVConsumerImpl will be changed over to DynamicConsumerImpl. This will not change anything set to FFmpegTransSageTVConsumerImpl. hdhr.wait_for_streaming and upnp.dct.wait_for_streaming will be changed to 15000.
• Renamed FFmpegSageTVConsumerImpl to FFmpegOldSageTVConsumerImpl to force old installations to use the newer remuxer unless explicitly set otherwise.
• Fixed DynamicConsumerImpl not populating the sagetv.device.<unique_id>.consumer properties if the property did not already exist.
• Changed startup and resume from standby to not rely on a known number of capture devices. It will now check every time a new capture device is loaded to see if it's the one SageTV is requesting until the required devices timeout (sagetv.device.global.required_devices_loaded_timeout_ms). This should also result in faster resume tuning times since the program no longer needs to wait for all required devices to be loaded.
• Increased wait for response from InfiniTV devices to 10 seconds.
• Amount of data required to be written before returning OK to SageTV is now based on how much was needed for FFmpeg to detect the streams.
• Added some FFmpeg optimizations to ensure that a key video frame is at the very start of the container when possible. This appears to provide additional assurance so that MPEG-PS files are detected correctly.
• File growth monitoring is now more aggressive.
• Added some extra logging to tuning monitor.
• Fixed reading from buffer potentially getting stuck during detection.
• Added new option to disable HDHomeRun ClearQAM remapping and frequency/program verification for configuration without a reference tuner with a CableCARD installed. To disable the remapping feature, change the value of hdhr.allow_qam_remapping to false.

Whatever changes you made my Android mini client can now watch livetv even on channels I could not get before ... Using EXOPLAYER. I can constantly change channels without any crashes or spinning circle. ... also stopping a recording is instant now. Previous channel even works

[EnterNoEscape]

Originally Posted by nyplayer

Whatever changes you made my Android mini client can now watch livetv even on channels I could not get before ... Using EXOPLAYER. I can constantly change channels without any crashes or spinning circle. ... also stopping a recording is instant now. Previous channel even works

Excellent. I'll try not to change anything.

Given that you've been dealing with a lot of H.264 content, I'd be willing to bet what made the biggest impact was "Added some FFmpeg optimizations to ensure that a key video frame is at the very start of the container when possible. This appears to provide additional assurance so that MPEG-PS files are detected correctly." And this one generally makes the channel tuning come back faster in a logical manner "Amount of data required to be written before returning OK to SageTV is now based on how much was needed for FFmpeg to detect the streams."

[nyplayer]

Originally Posted by EnterNoEscape

Excellent. I'll try not to change anything.

Given that you've been dealing with a lot of H.264 content, I'd be willing to bet what made the biggest impact was "Added some FFmpeg optimizations to ensure that a key video frame is at the very start of the container when possible. This appears to provide additional assurance so that MPEG-PS files are detected correctly." And this one generally makes the channel tuning come back faster in a logical manner "Amount of data required to be written before returning OK to SageTV is now based on how much was needed for FFmpeg to detect the streams."

Yeah I even tested switching H264 Channels then MPEG channels and the tunning is flawless. I am switching between NBA TV MPEG and TNT H264.

[stanger89]

Originally Posted by EnterNoEscape

stanger89,

You will want to install 0.5.1 and change the value of hdhr.allow_qam_remapping to false, then you should be able to use your HDHomeRun Prime without a CableCARD installed. OpenDCT will assume the channel numbers do not need to be remapped.

20:15:13.852 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] INFO  HDHRNativeCaptureDevice - Starting the encoding for the channel '885' from the device 'DCT-HDHomeRun Prime Tuner 13139E6D-2' to the file 'F:\ImpossibleEngineering-WorldsBiggestCruiseShip-18563119-0.ts'...
20:15:13.852 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'null' lockKey: '0' sendLength: 26
20:15:13.852 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: '1062731684' lockKey: '1062731684' sendLength: 45
20:15:13.852 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] INFO  HDHRNativeCaptureDevice - HDHomeRun is now locked.
20:15:13.852 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG RTPCaptureDeviceServices - Producer was not running.
20:15:13.852 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG BasicCaptureDevice - Consumer is was not in progress.
20:15:13.875 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'null' lockKey: '0' sendLength: 26
20:15:13.875 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'none' lockKey: '1062731684' sendLength: 39
20:15:13.875 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'null' lockKey: '0' sendLength: 26
20:15:13.875 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] INFO  NIOHTTPProducerImpl - Connecting to source using the URL 'http://192.168.0.8:5004/tuner2/v885'
20:15:13.875 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] ERROR HTTPProducerImpl - HTTP Error: 'HTTP/1.1 404 Not Found', 
20:15:13.875 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] ERROR NIOHTTPProducerImpl - Unable to connect to the URL 'http://192.168.0.8:5004/tuner2/v885' => java.io.IOException: Server responded HTTP/1.1 404 Not Found
    at opendct.video.http.NIOHttpDownloader.connect(NIOHttpDownloader.java:106)
    at opendct.producer.NIOHTTPProducerImpl.setSourceUrl(NIOHTTPProducerImpl.java:126)
    at opendct.producer.NIOHTTPProducerImpl.selectURL(NIOHTTPProducerImpl.java:81)
    at opendct.producer.NIOHTTPProducerImpl.setSourceUrls(NIOHTTPProducerImpl.java:64)
    at opendct.capture.HTTPCaptureDeviceServices.startProducing(HTTPCaptureDeviceServices.java:76)
    at opendct.capture.HDHRNativeCaptureDevice.tuneUrl(HDHRNativeCaptureDevice.java:1192)
    at opendct.capture.HDHRNativeCaptureDevice.startEncodingSync(HDHRNativeCaptureDevice.java:685)
    at opendct.capture.HDHRNativeCaptureDevice.startEncoding(HDHRNativeCaptureDevice.java:512)
    at opendct.capture.HDHRNativeCaptureDevice.startEncoding(HDHRNativeCaptureDevice.java:463)
    at opendct.sagetv.SageTVRequestHandler.run(SageTVRequestHandler.java:228)
    at java.lang.Thread.run(Unknown Source)

20:15:13.875 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] ERROR HTTPCaptureDeviceServices - Unable to open the URL '[http://192.168.0.8:5004/tuner2/v885]'. => java.io.IOException: Unable to connect to any of the provided addresses.
    at opendct.producer.NIOHTTPProducerImpl.selectURL(NIOHTTPProducerImpl.java:94)
    at opendct.producer.NIOHTTPProducerImpl.setSourceUrls(NIOHTTPProducerImpl.java:64)
    at opendct.capture.HTTPCaptureDeviceServices.startProducing(HTTPCaptureDeviceServices.java:76)
    at opendct.capture.HDHRNativeCaptureDevice.tuneUrl(HDHRNativeCaptureDevice.java:1192)
    at opendct.capture.HDHRNativeCaptureDevice.startEncodingSync(HDHRNativeCaptureDevice.java:685)
    at opendct.capture.HDHRNativeCaptureDevice.startEncoding(HDHRNativeCaptureDevice.java:512)
    at opendct.capture.HDHRNativeCaptureDevice.startEncoding(HDHRNativeCaptureDevice.java:463)
    at opendct.sagetv.SageTVRequestHandler.run(SageTVRequestHandler.java:228)
    at java.lang.Thread.run(Unknown Source)

20:15:13.875 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'null' lockKey: '0' sendLength: 26
20:15:13.875 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: '1062731768' lockKey: '1062731768' sendLength: 45
20:15:13.875 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/vchannel' value: '885' lockKey: '1062731768' sendLength: 39
20:15:13.883 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] ERROR HDHRNativeCaptureDevice - HDHomeRun is unable to tune into channel because the command did not work => opendct.tuning.hdhomerun.GetSetException: ERROR: invalid virtual channel
    at opendct.tuning.hdhomerun.HDHomeRunControl.setVariable(HDHomeRunControl.java:206)
    at opendct.tuning.hdhomerun.HDHomeRunTuner.set(HDHomeRunTuner.java:135)
    at opendct.tuning.hdhomerun.HDHomeRunTuner.setVirtualChannel(HDHomeRunTuner.java:485)
    at opendct.capture.HDHRNativeCaptureDevice.startEncodingSync(HDHRNativeCaptureDevice.java:692)
    at opendct.capture.HDHRNativeCaptureDevice.startEncoding(HDHRNativeCaptureDevice.java:512)
    at opendct.capture.HDHRNativeCaptureDevice.startEncoding(HDHRNativeCaptureDevice.java:463)
    at opendct.sagetv.SageTVRequestHandler.run(SageTVRequestHandler.java:228)
    at java.lang.Thread.run(Unknown Source)

20:15:13.883 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] ERROR SageTVRequestHandler - SageTV sent: 'START DCT-HDHomeRun Prime Tuner 13139E6D-2 Digital TV Tuner|1238548317|885|2922402627844|F:\ImpossibleEngineering-WorldsBiggestCruiseShip-18563119-0.ts|Great', Replied: 'ERROR Device Start Failed'
20:15:13.922 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] ERROR SageTVRequestHandler - Encoder device is unable to start.
20:15:31.375 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG SageTVRequestHandler - SageTV sent: 'STOP DCT-HDHomeRun Prime Tuner 13139E6D-2 Digital TV Tuner'
20:15:31.375 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHRNativeCaptureDevice - Stopping encoding...
20:15:31.375 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG RTPCaptureDeviceServices - Producer was not running.
20:15:31.375 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG BasicCaptureDevice - Consumer is was not in progress.
20:15:31.375 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/channel' value: 'none' lockKey: '1062731768' sendLength: 39
20:15:31.375 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/target' value: 'none' lockKey: '1062731768' sendLength: 38
20:15:31.375 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'null' lockKey: '0' sendLength: 26
20:15:31.375 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'none' lockKey: '1062731768' sendLength: 39
20:15:31.375 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'null' lockKey: '0' sendLength: 26
20:15:31.375 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] INFO  HDHRNativeCaptureDevice - HDHomeRun is now unlocked.
20:15:31.375 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] INFO  HDHRNativeCaptureDevice - Capture device is now unlocked.
20:15:31.375 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG SageTVRequestHandler - Replied: 'OK'

[EnterNoEscape]

Originally Posted by stanger89

20:15:13.852 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] INFO  HDHRNativeCaptureDevice - Starting the encoding for the channel '885' from the device 'DCT-HDHomeRun Prime Tuner 13139E6D-2' to the file 'F:\ImpossibleEngineering-WorldsBiggestCruiseShip-18563119-0.ts'...
20:15:13.852 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'null' lockKey: '0' sendLength: 26
20:15:13.852 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: '1062731684' lockKey: '1062731684' sendLength: 45
20:15:13.852 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] INFO  HDHRNativeCaptureDevice - HDHomeRun is now locked.
20:15:13.852 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG RTPCaptureDeviceServices - Producer was not running.
20:15:13.852 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG BasicCaptureDevice - Consumer is was not in progress.
20:15:13.875 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'null' lockKey: '0' sendLength: 26
20:15:13.875 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'none' lockKey: '1062731684' sendLength: 39
20:15:13.875 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'null' lockKey: '0' sendLength: 26
20:15:13.875 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] INFO  NIOHTTPProducerImpl - Connecting to source using the URL 'http://192.168.0.8:5004/tuner2/v885'
20:15:13.875 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] ERROR HTTPProducerImpl - HTTP Error: 'HTTP/1.1 404 Not Found', 
20:15:13.875 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] ERROR NIOHTTPProducerImpl - Unable to connect to the URL 'http://192.168.0.8:5004/tuner2/v885' => java.io.IOException: Server responded HTTP/1.1 404 Not Found
    at opendct.video.http.NIOHttpDownloader.connect(NIOHttpDownloader.java:106)
    at opendct.producer.NIOHTTPProducerImpl.setSourceUrl(NIOHTTPProducerImpl.java:126)
    at opendct.producer.NIOHTTPProducerImpl.selectURL(NIOHTTPProducerImpl.java:81)
    at opendct.producer.NIOHTTPProducerImpl.setSourceUrls(NIOHTTPProducerImpl.java:64)
    at opendct.capture.HTTPCaptureDeviceServices.startProducing(HTTPCaptureDeviceServices.java:76)
    at opendct.capture.HDHRNativeCaptureDevice.tuneUrl(HDHRNativeCaptureDevice.java:1192)
    at opendct.capture.HDHRNativeCaptureDevice.startEncodingSync(HDHRNativeCaptureDevice.java:685)
    at opendct.capture.HDHRNativeCaptureDevice.startEncoding(HDHRNativeCaptureDevice.java:512)
    at opendct.capture.HDHRNativeCaptureDevice.startEncoding(HDHRNativeCaptureDevice.java:463)
    at opendct.sagetv.SageTVRequestHandler.run(SageTVRequestHandler.java:228)
    at java.lang.Thread.run(Unknown Source)

20:15:13.875 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] ERROR HTTPCaptureDeviceServices - Unable to open the URL '[http://192.168.0.8:5004/tuner2/v885]'. => java.io.IOException: Unable to connect to any of the provided addresses.
    at opendct.producer.NIOHTTPProducerImpl.selectURL(NIOHTTPProducerImpl.java:94)
    at opendct.producer.NIOHTTPProducerImpl.setSourceUrls(NIOHTTPProducerImpl.java:64)
    at opendct.capture.HTTPCaptureDeviceServices.startProducing(HTTPCaptureDeviceServices.java:76)
    at opendct.capture.HDHRNativeCaptureDevice.tuneUrl(HDHRNativeCaptureDevice.java:1192)
    at opendct.capture.HDHRNativeCaptureDevice.startEncodingSync(HDHRNativeCaptureDevice.java:685)
    at opendct.capture.HDHRNativeCaptureDevice.startEncoding(HDHRNativeCaptureDevice.java:512)
    at opendct.capture.HDHRNativeCaptureDevice.startEncoding(HDHRNativeCaptureDevice.java:463)
    at opendct.sagetv.SageTVRequestHandler.run(SageTVRequestHandler.java:228)
    at java.lang.Thread.run(Unknown Source)

20:15:13.875 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'null' lockKey: '0' sendLength: 26
20:15:13.875 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: '1062731768' lockKey: '1062731768' sendLength: 45
20:15:13.875 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/vchannel' value: '885' lockKey: '1062731768' sendLength: 39
20:15:13.883 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] ERROR HDHRNativeCaptureDevice - HDHomeRun is unable to tune into channel because the command did not work => opendct.tuning.hdhomerun.GetSetException: ERROR: invalid virtual channel
    at opendct.tuning.hdhomerun.HDHomeRunControl.setVariable(HDHomeRunControl.java:206)
    at opendct.tuning.hdhomerun.HDHomeRunTuner.set(HDHomeRunTuner.java:135)
    at opendct.tuning.hdhomerun.HDHomeRunTuner.setVirtualChannel(HDHomeRunTuner.java:485)
    at opendct.capture.HDHRNativeCaptureDevice.startEncodingSync(HDHRNativeCaptureDevice.java:692)
    at opendct.capture.HDHRNativeCaptureDevice.startEncoding(HDHRNativeCaptureDevice.java:512)
    at opendct.capture.HDHRNativeCaptureDevice.startEncoding(HDHRNativeCaptureDevice.java:463)
    at opendct.sagetv.SageTVRequestHandler.run(SageTVRequestHandler.java:228)
    at java.lang.Thread.run(Unknown Source)

20:15:13.883 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] ERROR SageTVRequestHandler - SageTV sent: 'START DCT-HDHomeRun Prime Tuner 13139E6D-2 Digital TV Tuner|1238548317|885|2922402627844|F:\ImpossibleEngineering-WorldsBiggestCruiseShip-18563119-0.ts|Great', Replied: 'ERROR Device Start Failed'
20:15:13.922 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] ERROR SageTVRequestHandler - Encoder device is unable to start.
20:15:31.375 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG SageTVRequestHandler - SageTV sent: 'STOP DCT-HDHomeRun Prime Tuner 13139E6D-2 Digital TV Tuner'
20:15:31.375 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHRNativeCaptureDevice - Stopping encoding...
20:15:31.375 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG RTPCaptureDeviceServices - Producer was not running.
20:15:31.375 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG BasicCaptureDevice - Consumer is was not in progress.
20:15:31.375 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/channel' value: 'none' lockKey: '1062731768' sendLength: 39
20:15:31.375 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/target' value: 'none' lockKey: '1062731768' sendLength: 38
20:15:31.375 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'null' lockKey: '0' sendLength: 26
20:15:31.375 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'none' lockKey: '1062731768' sendLength: 39
20:15:31.375 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'null' lockKey: '0' sendLength: 26
20:15:31.375 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] INFO  HDHRNativeCaptureDevice - HDHomeRun is now unlocked.
20:15:31.375 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] INFO  HDHRNativeCaptureDevice - Capture device is now unlocked.
20:15:31.375 [SageTVRequestHandler-122:DCT-HDHomeRun Prime Tuner 13139E6D-2] DEBUG SageTVRequestHandler - Replied: 'OK'

That's very interesting. Everything did exactly what it was supposed to and the HDHomeRun refused to tune in the channels it claims to have. What happens when you put http://192.168.0.8:5004/auto/v885 into a browser? Does it start downloading? Maybe you're running an older firmware? Also the fall back to RTP using the virtual channel 885 failed which is extra odd. I can understand that maybe the URL doesn't work, but the virtual channel not working is very perplexing.

In case you're wondering, the error message that was returned for the RTP tuning was exactly what the HDHomeRun replied. It literally told me the channel doesn't exist.

[stanger89]

I'll have to check it out when I get home.

[CptKirk]

With the problems I'd been having I dug into the server some more yesterday. I found the device manager was constantly refreshing itself. Turned out it was one of the Hauppauge USB tuners appearing/disappearing/appearing/etc/etc.

Got that all fixed and went ahead and updated pretty much all the drivers on the system. Did 5 simultaneous recordings on all tuners. Everything was looking good.

But had a few more halt detected in program late last night afterwards.

I've attached the log files.

[EnterNoEscape]

Originally Posted by CptKirk

With the problems I'd been having I dug into the server some more yesterday. I found the device manager was constantly refreshing itself. Turned out it was one of the Hauppauge USB tuners appearing/disappearing/appearing/etc/etc.

Got that all fixed and went ahead and updated pretty much all the drivers on the system. Did 5 simultaneous recordings on all tuners. Everything was looking good.

But had a few more halt detected in program late last night afterwards.

I've attached the log files.

It looks similar to the other ones. At 21:59:18.776 the HDHomeRun is not streaming at all from the two tuners currently in use. A re-tune is initiated which first checks the current configuration of the HDHomeRun to aid in troubleshooting and it fails to get the target currently in use because the HDHomeRun is not responding. The HDHomeRun starts responding again at 22:01:06.194. That's about a two minute outage.

While the last few logs looked like the problem could have been made worse because of how OpenDCT handled the situation, based on what I'm seeing in this log that's not likely the case anymore. This could be either the network adapter, the network switch or the HDHomeRun at fault. There's no way to be sure without swapping components.

If you have the parts laying around, try installing a dedicated NIC for the HDHomeRun. I used to do this a while ago when I suspected I had a poor quality NIC and it certainly helped. It turns out at least in my case, it wasn't completely the NIC that was the problem. It was using UNC shares to local drives that was making things unreliable; particularly when also running Comskip. I did this so Comskip would be detected on the Windows SageTV Client without needing to map drives. It was apparently too many packets for it to deal with. Now I just record directly to the local drives and I have a lot fewer headaches.

Also of interest is that at 22:07:25.171, the buffer gets completely backed up at almost 40MB worth of data that was unable to be written due to probably either the CPU being too preoccupied or some bottleneck in writing to the file system. The buffer can't seem to completely recover since this issue happens over and over until 22:19:53.462. Thanks to some additional logging I added to the monitoring piece, I can positively say that data was being written to the file, just not quickly enough to keep the buffer from overflowing.

[Toddly]

Originally Posted by EnterNoEscape

There's another thread where the issue sounds little like what you're describing. Basically what you'll want to try is start a recording, then try to watch it after it has been recording for about 30 seconds. If this isn't the issue, you can post a log with the problem in it, I might be able to get you in the right direction.

I tried your suggestion but still no joy. Attached is the log file. Maybe there is a clue to my issue that you can see.

Thanks for your help.

[jm9843]

Originally Posted by EnterNoEscape

• CONFIGURATION UPGRADE: The first time you run this version, it will upgrade your current configuration. Anything still referencing FFmpegSageTVConsumerImpl will be changed over to FFmpegTransSageTVConsumerImpl. hdhr.wait_for_streaming and upnp.dct.wait_for_streaming will be changed to 15000.

Does this mean that it is no longer necessary to stop the service and rename your old config file before upgrading? (for the purpose of getting all the latest settings)

[EnterNoEscape]

Originally Posted by Toddly

I tried your suggestion but still no joy. Attached is the log file. Maybe there is a clue to my issue that you can see.

Thanks for your help.

You have an interesting, but likely permissions or disk space related issue. Every time OpenDCT tries to create a new file for a recording, I see something like this:

ERROR FFmpegSageTVConsumerImpl - Unable to create the recording file '\\Nacho\H\G3Sportsman-GatorGarFishing-21210612-1.ts'.

My speculation is that the .mpgbuf file used for channel previews is working because the file already exists and is fully allocated (it's a circular buffer basically). Are you running the OpenDCT service under an account that actually has network access?

Originally Posted by jm9843

Does this mean that it is no longer necessary to stop the service and rename your old config file before upgrading? (for the purpose of getting all the latest settings)

It's not really a requirement to wipe the properties file every time you upgrade, but it's probably not a bad idea if you want to always be sure you have the latest recommended settings. The reason I occasionally automate an upgrade in configuration is when I realize the old default values are really not working out for most people or if everyone would be better served using a newer way of doing things. I don't want to surprise anyone which is why sometimes even if the defaults change a little, I don't change whatever you already have saved.