OpenDCT: An open source digital cable tuner.

[EnterNoEscape]

• Added more delays for detection of available network interfaces when InfiniTV devices could be discovered.
• The property hdhr.always_tune_legacy=false when set to true now also forces HDHomeRun legacy channel scanning with the exception of the HDHomeRun Prime when it has a CableCARD inserted.
• Improved HDHomeRun QAM and DVB scanning in legacy mode.
• Fixed situation whereby the lock can be lost while performing a channel scan on HDHomeRun devices.
• Improved channel scanning in general. (thanks Fuzzy)

[EnterNoEscape]

• Added support for URL's for tuning executables in Generic HTTP Capture Devices.
• Fixed HDHomeRun tuner count detection logic to run a lot faster when a device is not responding.
• Fixed some issues with rejecting devices that act like an HDHomeRun, but are not.

[technazz]

Im getting this error and no recording.

21:20:06.796 [SageTVTuningMonitor-51] DEBUG SageTVTuningMonitor - The producer appears to be stuck at 32168332.

Attached is the log.

Thanks

Chris

[Greg2dot0]

I was reviewing my log after updating to RC2 this morning and I saw an error. The error was a timeout error so really wasn't a big deal, but as I looked at it more closely, it would seem that the timeout is for my HDHR Prime but on it's OLD subnet 192.168.1.5. I recently re-IP'd (in November) my whole network. My current address for this box is 10.0.0.80. After trying to figure out if there was a configuration file that was out of date, I couldn't find anything that seems weird.

Any insight into where I might look to remove any old ip addresses?

00:08:24.569 [WrapperSimpleAppMain] INFO  Config - Removed log file 'opendct.2016-12-05-1.log.gz' because it is over 30 days old.
01:07:00.147 [ChannelManager-46] INFO  ChannelManager - Updating the HDHomeRun channel lineup HDHomeRun DRI Tuner 13142E5A (dct_hdhomerun).
01:07:00.148 [ChannelManager-46] INFO  HDHomeRunChannels - Connecting to Prime DCT using the URL 'http://192.168.1.5:80/lineup.xml'
01:09:07.470 [ChannelManager-46] DEBUG HDHomeRunChannels - populateChannels created an unexpected exception => java.net.ConnectException: Connection timed out (Connection timed out)
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:589)
	at java.net.Socket.connect(Socket.java:538)
	at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
	at sun.net.www.http.HttpClient.<init>(HttpClient.java:211)
	at sun.net.www.http.HttpClient.New(HttpClient.java:308)
	at sun.net.www.http.HttpClient.New(HttpClient.java:326)
	at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1202)
	at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1138)
	at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1032)
	at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:966)
	at opendct.channel.updater.http.HDHomeRunChannels.populateChannels(HDHomeRunChannels.java:178)
	at opendct.channel.ChannelManager.updateChannelLineup(ChannelManager.java:489)
	at opendct.channel.ChannelManager.updateChannelLineups(ChannelManager.java:475)
	at opendct.channel.ChannelManager$3.run(ChannelManager.java:712)
	at java.lang.Thread.run(Thread.java:745)

UPDATE: I did find the source in the lineup file

lineup.address=192.168.1.5
lineup.friendly_name=HDHomeRun DRI Tuner 13142E5A

I stopped the service, deleted the dct_hdhomerun.properties file and restarted to see what happens. it looks like in the log, that it now is picking up the new address

05:58:02.518 [ChannelManager-49] INFO HDHomeRunChannels - Connecting to HDHomeRun using the URL 'http://10.0.0.80:80/lineup.xml'

No update on the dct_hdhomerun.properties file yet as it doesn't seem like the scan has been triggered.

Here's what it looks like now

#dct_hdhomerun Configuration File
#Thu Jan 05 05:56:32 EST 2017
lineup.address=13142E5A
lineup.friendly_name=HDHomeRun DRI Tuner 13142E5A
lineup.offline_update_interval=604800000
lineup.source=HDHOMERUN
lineup.update_interval=28800000
sagetv.available_channels_ref=
sagetv.unavailable_channels_ref=

Update 2: This may have been related to IPV6 being enabled on the box. I did pick up a note in the opendct.log that IPV6 was detected and an untested configuration so I disabled IPV6 and now the lineup seems to be updated correctly.


Thanks!

[EnterNoEscape]

Originally Posted by technazz

Im getting this error and no recording.

21:20:06.796 [SageTVTuningMonitor-51] DEBUG SageTVTuningMonitor - The producer appears to be stuck at 32168332.

Attached is the log.

Thanks

Chris

That means the remote server stopped streaming data. The line just before it is saying essentially that the remote server disconnected.

[EnterNoEscape]

Originally Posted by Greg2dot0

Update 2: This may have been related to IPV6 being enabled on the box. I did pick up a note in the opendct.log that IPV6 was detected and an untested configuration so I disabled IPV6 and now the lineup seems to be updated correctly.


Thanks!

I can explain this a little. First, the IP address that was in this file did not point to the HDHomeRun Prime anymore. More recent versions of OpenDCT don't use the IP address; they use the device ID and look up the device to update the lineup. The IPv6 thing isn't actually a problem. It's just there because I wasn't sure if it would ever cause any unexpected issues. There is somewhere between a 30-120 second delay on startup before the lineups are populated, so it's possible that on the first go, you just didn't wait long enough.

[Greg2dot0]

Originally Posted by EnterNoEscape

I can explain this a little. First, the IP address that was in this file did not point to the HDHomeRun Prime anymore. More recent versions of OpenDCT don't use the IP address; they use the device ID and look up the device to update the lineup.

Ah, that makes sense. One of the things I really appreciate is being able to reset the configuration by deleting the properties file and opendct will go and rebuild it. (Of course I also have to remember to stop the service) Since I hadn't had to mess with much in there, it took me a while to refamiliarize myself with the various properties files.

Thanks for clearing that up!

[technazz]

Originally Posted by EnterNoEscape

That means the remote server stopped streaming data. The line just before it is saying essentially that the remote server disconnected.

It may have stopped at one point but did not recover. When I saw this I checked the stream and it was working but it continued to get the error.

When I stopped the OpenDCT service and restarted it picked it back up again right away.

Is there a way to reset the process without restarting the service?

Chris

[EnterNoEscape]

Originally Posted by technazz

It may have stopped at one point but did not recover. When I saw this I checked the stream and it was working but it continued to get the error.

When I stopped the OpenDCT service and restarted it picked it back up again right away.

Is there a way to reset the process without restarting the service?

Chris

I must not have looked at the logs hard enough. What's actually happening is that traffic didn't go anywhere for over 15 seconds which was enough to make OpenDCT restart the stream for you. This functionality really only exists because of a capture device you don't use. I would try just disabling the recovery feature since SageTV will take care of a stalled recording after one minute anyway. Just change retune_enable=true to false.

[nyplayer]

How do I setup the channel changes in WMC Tuner ? if this is not using powershell ? The ip for my WMC machine is 10.0.0.169

	
	
sagetv.device.-782839283.consumer=opendct.consumer.DynamicConsumerImpl
sagetv.device.-782839283.custom_channels=
sagetv.device.-782839283.device_name=Encoder 1
sagetv.device.-782839283.encoder_listen_port=9000
sagetv.device.-782839283.encoder_merit=0
sagetv.device.-782839283.encoder_pool=generic_http
sagetv.device.-782839283.fast_network_encoder_switch=true
sagetv.device.-782839283.http_password=
sagetv.device.-782839283.http_username=
sagetv.device.-782839283.last_channel=-1
sagetv.device.-782839283.pretuning_executable=
sagetv.device.-782839283.stopping_executable=
sagetv.device.-782839283.stopping_executable_delay_ms=15000
sagetv.device.-782839283.streaming_url=http\://10.0.0.168/0.ts
sagetv.device.-782839283.streaming_url2=
sagetv.device.-782839283.streaming_url2_channels=
sagetv.device.-782839283.transcode_profile=
sagetv.device.-782839283.tuning_delay_ms=0
sagetv.device.-782839283.tuning_executable=

[EnterNoEscape]

Originally Posted by nyplayer

How do I setup the channel changes in WMC Tuner ? if this is not using powershell ? The ip for my WMC machine is 10.0.0.169

sagetv.device.-782839283.consumer=opendct.consumer.DynamicConsumerImpl
sagetv.device.-782839283.custom_channels=
sagetv.device.-782839283.device_name=Encoder 1
sagetv.device.-782839283.encoder_listen_port=9000
sagetv.device.-782839283.encoder_merit=0
sagetv.device.-782839283.encoder_pool=generic_http
sagetv.device.-782839283.fast_network_encoder_switch=true
sagetv.device.-782839283.http_password=
sagetv.device.-782839283.http_username=
sagetv.device.-782839283.last_channel=-1
sagetv.device.-782839283.pretuning_executable=
sagetv.device.-782839283.stopping_executable=
sagetv.device.-782839283.stopping_executable_delay_ms=15000
sagetv.device.-782839283.streaming_url=http\://10.0.0.168/0.ts
sagetv.device.-782839283.streaming_url2=
sagetv.device.-782839283.streaming_url2_channels=
sagetv.device.-782839283.transcode_profile=
sagetv.device.-782839283.tuning_delay_ms=0
sagetv.device.-782839283.tuning_executable=

sagetv.device.-782839283.stopping_executable=http://10.0.0.169:40510/stop
sagetv.device.-782839283.tuning_executable=http://10.0.0.169:40510/tune%20%c%

I also updated my example in the usage thread:
https://forums.sagetv.com/forums/showthread.php?t=63855

I should probably update the WMC Live Tuner thread too.

[nyplayer]

Thanks that works .... Can I send a request before I send the channel it does not always work on the initial request after the WMC tuner ha not been used for a while? Like maybe a Home Command or guide command.

[EnterNoEscape]

The pretuning executable always runs before the tuning executable. This would take you to the start screen:

sagetv.device.-782839283.pretuning_executable=http://10.0.0.169:40510/goto%20Start

[nyplayer]

Originally Posted by EnterNoEscape

The pretuning executable always runs before the tuning executable. This would take you to the start screen:

sagetv.device.-782839283.pretuning_executable=http://10.0.0.169:40510/goto%20Start

That made it worst LOL ... I guess I could play with the tuning delay.

[nyplayer]

I was following and it appears after a while when you go to tune the third number never makes it in time. I see inputting the first 2 digits but by the time it inputs the 3rd it tries and tune.

[rfutscher]

I have been trying for weeks to get SageTV or Opendct to tune my DirecTV Genie mini STB and the RC2 got everything working. It stopped tuning channels and stopping and restarting OpenDCT got it working again. Maybe be something I did while testing. Maybe it was trying to tune a four digit channel that wasn't authorized.

Good work, I am a happy camper.

[EnterNoEscape]

Originally Posted by nyplayer

I was following and it appears after a while when you go to tune the third number never makes it in time. I see inputting the first 2 digits but by the time it inputs the 3rd it tries and tune.

Interesting. I'll see if there's anything I can do to try and make that work better. I haven't seen this issue myself, but I'm sure it will bite me eventually.

[nyplayer]

Originally Posted by EnterNoEscape

Interesting. I'll see if there's anything I can do to try and make that work better. I haven't seen this issue myself, but I'm sure it will bite me eventually.

Yeah happens when it is Idle a while ... in my case my DRM Channels are all 3 digits so when it tries to tune only the first 2 digits go through so it just tunes the last channel it was on.

[EnterNoEscape]

Originally Posted by nyplayer

Yeah happens when it is Idle a while ... in my case my DRM Channels are all 3 digits so when it tries to tune only the first 2 digits go through so it just tunes the last channel it was on.

Something I had observed was that WMC will automatically switch to a channel if you input the max number of digits for any channel in the guide. For example, if you don't have any guide data set (which I believe is what you did), and you input a channel number preceded by enough zeros to make it 7 digits total, the channel will tune right in without the need to press enter. I wonder if using padding would help your situation at all. The property to set this would be:

sagetv.device.<device_id>.channel_padding=7

[Jabroni]

Finally I had some time to test and configure the tuners correctly within my SageTV with the latest RC2 features..

* HDMI Network Encoder:
Works GREAT using the Generic HTTP Tuner, I moved the channel tunning to HTTP request too (used the powershell method before but had issues since it seems it wasnt allowed to run as service). I have a DirecTV Genie DVR which has HTTP interface and I was able to change channel using the following tuning_executable:

sagetv.device.-469286294.tuning_executable=http\://ip.of.dvr\:8080/tv/tune?major\=%c%%26clientAddr\=XXXXXXXXXXXX  (mac address of the DirecTV Extender)

* Remote HDHomeRun Extend using hdhr.static_addresses_csv
A HDHomeRun that is hosted on different subnet than my local LAN

Pretty impressed on how Im able to use this plugin for most of my network tunning needs