OpenDCT: An open source digital cable tuner.

[EnterNoEscape]

Originally Posted by sflamm

Switched to: OpenDCT_0.5.13_x86.msi

Now the tuners show up in SageTV... however it is only creating 2 instead of 3 for the HDHR Prime.

The console says HDHR "did not respond with any tuners. Assuming 2". (seems like a bug)

I'm running an old firmware version 20130328 - is that the issue? (haven't upgraded in a long long time)

Here is the full console output:

STATUS | wrapper  | 2016/12/04 02:48:13.973 | --> Wrapper Started as Console
STATUS | wrapper  | 2016/12/04 02:48:14.182 | Launching a JVM...
INFO   | wrapper  | 2016/12/04 02:48:14.182 | command: "C:\Windows\system32\java.exe" -Dopendct_log_root=c:/ProgramData/OpenDCT/logs -Dconfig_dir=c:/ProgramData
/OpenDCT/config -Ddaemon_mode=true -XX:ErrorFile=c:/ProgramData/OpenDCT/logs/hs_err_pid%p.log -verbose:gc -XX:+UseG1GC -Xms128m -Xmx768m -Djava.library.path="./
lib;../lib" -classpath "./lib/wrapper.jar;../lib/opendct-0.5.13.jar;../lib/cling-core-2.1.0.jar;../lib/log4j-api-2.5.jar;../lib/log4j-core-2.5.jar;../lib/jna-4.
2.1.jar;../lib/jna-platform-4.2.1.jar;../lib/nanohttpd-2.3.0.jar;../lib/nanohttpd-nanolets-2.3.0.jar;../lib/gson-2.6.2.jar;../lib/javacpp-1.2.jar;../lib/ffmpeg-
3.1.2-1.2.jar;../lib/ffmpeg-3.1.2-1.2-windows-x86.jar;../lib/seamless-util-1.1.1.jar;../lib/seamless-http-1.1.1.jar;../lib/seamless-xml-1.1.1.jar" -Dwrapper.key
="7VSPolkDYNHxRoJi" -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.pid=3160 -Dwrapper.version="3.2.3" -Dwrapper.native
_library="wrapper" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp opendct.Main
INFO   | jvm 1    | 2016/12/04 02:48:14.595 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
INFO   | jvm 1    | 2016/12/04 02:48:14.595 |   Copyright 1999-2006 Tanuki Software, Inc.  All Rights Reserved.
INFO   | jvm 1    | 2016/12/04 02:48:14.595 |
INFO   | jvm 1    | 2016/12/04 02:48:15.403 | 02:48:15.346 [WrapperSimpleAppMain] INFO  Main - Starting OpenDCT 0.5.13...
INFO   | jvm 1    | 2016/12/04 02:48:15.508 | 02:48:15.493 [WrapperSimpleAppMain] INFO  Main - OpenDCT logging to the directory 'c:/ProgramData/OpenDCT/logs'.
INFO   | jvm 1    | 2016/12/04 02:48:15.508 | 02:48:15.507 [WrapperSimpleAppMain] INFO  UpnpManager - Logging Cling UPnP to 'c:/ProgramData/OpenDCT/logs\opendct
_cling.log'.
INFO   | jvm 1    | 2016/12/04 02:48:15.609 | 02:48:15.510 [FFmpegAsyncInit-20] INFO  Main - FFmpeg loading...
INFO   | jvm 1    | 2016/12/04 02:48:15.912 | 02:48:15.823 [WrapperSimpleAppMain] INFO  NetworkPowerEventManger - Network interfaces which are up and have an IP
4 address are:
INFO   | jvm 1    | 2016/12/04 02:48:15.912 | name:eth5 (Intel(R) Ethernet Connection I217-LM) 10.0.0.2
INFO   | jvm 1    | 2016/12/04 02:48:15.912 | [GC pause (young) 24M->4961K(128M), 0.0164186 secs]
INFO   | jvm 1    | 2016/12/04 02:48:15.912 | 02:48:15.911 [DynamicAsyncInit-20] INFO  DynamicConsumerImpl - Dynamic consumer default set to use opendct.consume
r.FFmpegTransSageTVConsumerImpl
INFO   | jvm 1    | 2016/12/04 02:48:15.913 | 02:48:15.912 [DynamicAsyncInit-20] INFO  DynamicConsumerImpl - Dynamic consumer set to use opendct.consumer.FFmpeg
TransSageTVConsumerImpl for []
INFO   | jvm 1    | 2016/12/04 02:48:15.913 | 02:48:15.912 [DynamicAsyncInit-20] INFO  DynamicConsumerImpl - Dynamic consumer set to use opendct.consumer.MediaS
erverConsumerImpl for []
INFO   | jvm 1    | 2016/12/04 02:48:15.913 | 02:48:15.912 [DynamicAsyncInit-20] INFO  DynamicConsumerImpl - Dynamic consumer set to use opendct.consumer.RawSag
eTVConsumerImpl for []
INFO   | jvm 1    | 2016/12/04 02:48:16.016 | 02:48:15.915 [LineupAsyncInit:dct_hdhomerun-26] INFO  ChannelManager - Updating the HDHomeRun channel lineup HDHom
eRun DRI Tuner 13185194 (dct_hdhomerun).
INFO   | jvm 1    | 2016/12/04 02:48:16.016 | 02:48:15.996 [WindowsPowerMessagePump] INFO  WindowsPowerMessagePump - Message pump started.
INFO   | jvm 1    | 2016/12/04 02:48:16.317 | 02:48:16.288 [WrapperSimpleAppMain] INFO  UpnpManager - Starting UPnP services...
INFO   | jvm 1    | 2016/12/04 02:48:16.418 | 02:48:16.404 [WrapperSimpleAppMain] INFO  DCTDefaultUpnpServiceConfiguration - Using the interface 'eth5' with IP
address 10.0.0.2 for UPnP discovery.
INFO   | jvm 1    | 2016/12/04 02:48:16.620 | 02:48:16.535 [UPnPDiscovery-36] INFO  UpnpManager - UPnP discovery thread has started.
INFO   | jvm 1    | 2016/12/04 02:48:16.821 | 02:48:16.738 [HDHomeRunDiscoverySend-37] INFO  HDHomeRunDiscovery - HDHomeRun discovery sender thread started.
INFO   | jvm 1    | 2016/12/04 02:48:16.821 | 02:48:16.738 [HDHomeRunDiscoveryReceive-37] INFO  HDHomeRunDiscovery - HDHomeRun discovery receive thread for /10.
0.0.255:65001 broadcast started.
INFO   | jvm 1    | 2016/12/04 02:48:16.821 | 02:48:16.740 [WrapperSimpleAppMain] INFO  NanoHTTPDManager - Starting webserver on port 9091...
INFO   | jvm 1    | 2016/12/04 02:48:16.821 | 02:48:16.741 [HDHomeRunDiscoverySend-37] INFO  HDHomeRunDiscovery - Broadcasting HDHomeRun discovery packet to /10
.0.0.255:65001... (startup)
INFO   | jvm 1    | 2016/12/04 02:48:16.821 | 02:48:16.759 [HDHomeRunDiscoveryReceive-37] WARN  HDHomeRunDiscovery - The capture device 'HDHomeRun DRI Tuner 131
104FC' did not respond with any tuners. Assuming 2.
INFO   | jvm 1    | 2016/12/04 02:48:16.822 | 02:48:16.760 [HDHomeRunDiscoveryReceive-37] INFO  HDHomeRunDiscoverer - Discovered a new HDHomeRun device 'HDHomeR
un DRI Tuner 131104FC' with 2 tuners.
INFO   | jvm 1    | 2016/12/04 02:48:16.822 | 02:48:16.790 [WrapperSimpleAppMain] INFO  Main - Running in daemon mode...
INFO   | jvm 1    | 2016/12/04 02:48:17.024 | 02:48:16.941 [HDHomeRunDiscoverySend-37] INFO  HDHomeRunDiscovery - Broadcasting HDHomeRun discovery packet to /10
.0.0.255:65001... (requested)
INFO   | jvm 1    | 2016/12/04 02:48:17.125 | 02:48:17.045 [FFmpegAsyncInit-20] INFO  Main - FFmpeg loaded in 1536ms.
INFO   | jvm 1    | 2016/12/04 02:48:17.226 | 02:48:17.142 [HDHomeRunDiscoverySend-37] INFO  HDHomeRunDiscovery - Broadcasting HDHomeRun discovery packet to /10
.0.0.255:65001... (startup)
INFO   | jvm 1    | 2016/12/04 02:48:17.327 | [GC pause (young)
INFO   | jvm 1    | 2016/12/04 02:48:17.428 |  42M->12M(128M), 0.0168614 secs]
INFO   | jvm 1    | 2016/12/04 02:48:17.428 | 02:48:17.342 [HDHomeRunDiscoverySend-37] INFO  HDHomeRunDiscovery - Broadcasting HDHomeRun discovery packet to /10
.0.0.255:65001... (startup)
INFO   | jvm 1    | 2016/12/04 02:48:19.247 | 02:48:19.205 [HDHomeRunDiscoveryReceive-37] INFO  ChannelManager - Updating the HDHomeRun channel lineup HDHomeRun
 DRI Tuner 131104FC (dct_hdhomerun).
INFO   | jvm 1    | 2016/12/04 02:48:19.247 | 02:48:19.212 [HDHomeRunDiscoveryReceive-37] INFO  HDHRNativeCaptureDevice - Encoder Manufacturer: 'Silicondust', N
umber: 0, Remote IP: '/10.0.0.50', Local IP: '10.0.0.2', CableCARD: true, Lineup: 'dct_hdhomerun', Offline Scan Enabled: false, RTP Port: 8336
INFO   | jvm 1    | 2016/12/04 02:48:19.248 | 02:48:19.222 [HDHomeRunDiscoveryReceive-37] INFO  SageTVManager - The capture device 'DCT-HDHomeRun Prime Tuner 13
1104FC-0' is ready.
INFO   | jvm 1    | 2016/12/04 02:48:19.249 | 02:48:19.229 [HDHomeRunDiscoveryReceive-37] INFO  SageTVSocketServer - Opening ServerSocket on port 9000...
INFO   | jvm 1    | 2016/12/04 02:48:19.249 | 02:48:19.229 [SageTVTuningMonitor-63] INFO  SageTVTuningMonitor - Tuning monitor thread started.
INFO   | jvm 1    | 2016/12/04 02:48:19.250 | 02:48:19.230 [SageTVSocketServer-64:9000] INFO  SageTVSocketServer - Started listening on port 9000...
INFO   | jvm 1    | 2016/12/04 02:48:19.455 | 02:48:19.412 [HDHomeRunDiscoveryReceive-37] INFO  ChannelManager - Updating the HDHomeRun channel lineup HDHomeRun
 DRI Tuner 131104FC (dct_hdhomerun).
INFO   | jvm 1    | 2016/12/04 02:48:19.456 | 02:48:19.415 [HDHomeRunDiscoveryReceive-37] INFO  HDHRNativeCaptureDevice - Encoder Manufacturer: 'Silicondust', N
umber: 1, Remote IP: '/10.0.0.50', Local IP: '10.0.0.2', CableCARD: true, Lineup: 'dct_hdhomerun', Offline Scan Enabled: false, RTP Port: 8302
INFO   | jvm 1    | 2016/12/04 02:48:19.458 | 02:48:19.416 [HDHomeRunDiscoveryReceive-37] INFO  SageTVManager - The capture device 'DCT-HDHomeRun Prime Tuner 13
1104FC-1' is ready.
INFO   | jvm 1    | 2016/12/04 02:48:19.663 | 02:48:19.601 [HDHomeRunDiscoveryReceive-37] WARN  HDHomeRunDiscovery - The capture device 'HDHomeRun DRI Tuner 131
85194' did not respond with any tuners. Assuming 2.
INFO   | jvm 1    | 2016/12/04 02:48:19.663 | 02:48:19.602 [HDHomeRunDiscoveryReceive-37] INFO  HDHomeRunDiscoverer - Discovered a new HDHomeRun device 'HDHomeR
un DRI Tuner 13185194' with 2 tuners.
INFO   | jvm 1    | 2016/12/04 02:48:19.866 | 02:48:19.801 [HDHomeRunDiscoveryReceive-37] INFO  ChannelManager - Updating the HDHomeRun channel lineup HDHomeRun
 DRI Tuner 13185194 (dct_hdhomerun).
INFO   | jvm 1    | 2016/12/04 02:48:19.867 | 02:48:19.804 [HDHomeRunDiscoveryReceive-37] INFO  HDHRNativeCaptureDevice - Encoder Manufacturer: 'Silicondust', N
umber: 0, Remote IP: '/10.0.0.53', Local IP: '10.0.0.2', CableCARD: true, Lineup: 'dct_hdhomerun', Offline Scan Enabled: false, RTP Port: 8492
INFO   | jvm 1    | 2016/12/04 02:48:19.869 | 02:48:19.804 [HDHomeRunDiscoveryReceive-37] INFO  SageTVManager - The capture device 'DCT-HDHomeRun Prime Tuner 13
185194-0' is ready.
INFO   | jvm 1    | 2016/12/04 02:48:20.075 | 02:48:19.992 [HDHomeRunDiscoveryReceive-37] INFO  ChannelManager - Updating the HDHomeRun channel lineup HDHomeRun
 DRI Tuner 13185194 (dct_hdhomerun).
INFO   | jvm 1    | 2016/12/04 02:48:20.075 | 02:48:19.996 [HDHomeRunDiscoveryReceive-37] INFO  HDHRNativeCaptureDevice - Encoder Manufacturer: 'Silicondust', N
umber: 1, Remote IP: '/10.0.0.53', Local IP: '10.0.0.2', CableCARD: true, Lineup: 'dct_hdhomerun', Offline Scan Enabled: false, RTP Port: 8368
INFO   | jvm 1    | 2016/12/04 02:48:20.077 | 02:48:19.996 [HDHomeRunDiscoveryReceive-37] INFO  SageTVManager - The capture device 'DCT-HDHomeRun Prime Tuner 13
185194-1' is ready.
INFO   | jvm 1    | 2016/12/04 02:48:20.183 | 02:48:20.169 [HDHomeRunDiscoveryReceive-37] WARN  HDHomeRunDiscovery - The capture device 'HDHomeRun DRI Tuner 131
104FC' did not respond with any tuners. Assuming 2.
INFO   | jvm 1    | 2016/12/04 02:48:20.183 | 02:48:20.176 [HDHomeRunDiscoveryReceive-37] WARN  HDHomeRunDiscovery - The capture device 'HDHomeRun DRI Tuner 131
85194' did not respond with any tuners. Assuming 2.
INFO   | jvm 1    | 2016/12/04 02:48:20.185 | 02:48:20.182 [HDHomeRunDiscoveryReceive-37] WARN  HDHomeRunDiscovery - The capture device 'HDHomeRun DRI Tuner 131
85194' did not respond with any tuners. Assuming 2.
INFO   | jvm 1    | 2016/12/04 02:48:20.290 | 02:48:20.192 [HDHomeRunDiscoveryReceive-37] WARN  HDHomeRunDiscovery - The capture device 'HDHomeRun DRI Tuner 131
104FC' did not respond with any tuners. Assuming 2.
INFO   | jvm 1    | 2016/12/04 02:48:20.290 | 02:48:20.199 [HDHomeRunDiscoveryReceive-37] WARN  HDHomeRunDiscovery - The capture device 'HDHomeRun DRI Tuner 131
85194' did not respond with any tuners. Assuming 2.
INFO   | jvm 1    | 2016/12/04 02:48:20.292 | 02:48:20.206 [HDHomeRunDiscoveryReceive-37] WARN  HDHomeRunDiscovery - The capture device 'HDHomeRun DRI Tuner 131
104FC' did not respond with any tuners. Assuming 2.
INFO   | jvm 1    | 2016/12/04 02:48:22.109 | 02:48:22.042 [HDHomeRunDiscoverySend-37] INFO  HDHomeRunDiscovery - Broadcasting HDHomeRun discovery packet to /10
.0.0.255:65001... (requested)
INFO   | jvm 1    | 2016/12/04 02:48:22.110 | 02:48:22.049 [HDHomeRunDiscoveryReceive-37] WARN  HDHomeRunDiscovery - The capture device 'HDHomeRun DRI Tuner 131
104FC' did not respond with any tuners. Assuming 2.
INFO   | jvm 1    | 2016/12/04 02:48:22.111 | 02:48:22.056 [HDHomeRunDiscoveryReceive-37] WARN  HDHomeRunDiscovery - The capture device 'HDHomeRun DRI Tuner 131
85194' did not respond with any tuners. Assuming 2.
INFO   | jvm 1    | 2016/12/04 02:48:55.023 | 02:48:54.931 [UPnPDiscovery-36] INFO  DCTDefaultUpnpServiceConfiguration - Using the interface 'eth5' with IP addr
ess 10.0.0.2 for UPnP discovery.
INFO   | jvm 1    | 2016/12/04 02:49:27.022 | 02:49:26.947 [UPnPDiscovery-36] WARN  DiscoveryRegistryListener - Before UPnP shutdown, the registry did not conta
in any devices.

That's because your HDHomeRun is not reporting the tuner count. Older firmwares are known to do this. You need to upgrade your firmware.

[BobbyDing]

Hi, I've been using opendct for a year now and it's been great. I want to use the android miniclient more and thus I wanted to enable transcoding in opendct to take advantage of the h264. When I did, the steams became choppy. It's running on an older quad core that has no trouble with multiple plex transcodings. I disabled all other obvious programs that might be draining cycles and also dropped to the 720p transoder, but it remained choppy. There is no choppiness when returning standard mpeg2 steams. So I thought I'd drop back and make sure there aren't other issues that need attention first. I see some errors in opendct logs that may or may not be healthy. I've attached log files. I'd very much appreciate if somebody could take a peak and let me know if there are issues that need attention?

General info:

I have 1 prime and 3 connects that are presently being used by sage.
2 extends, a prime and 1 older dual that are being used by other software and not in sage.

192.168.1.190 is the sage server
192.168.1.194 is another machine on the network running emby and nPVR.


Thanks!

Bobby

[EnterNoEscape]

Originally Posted by BobbyDing

Hi, I've been using opendct for a year now and it's been great. I want to use the android miniclient more and thus I wanted to enable transcoding in opendct to take advantage of the h264. When I did, the steams became choppy. It's running on an older quad core that has no trouble with multiple plex transcodings. I disabled all other obvious programs that might be draining cycles and also dropped to the 720p transoder, but it remained choppy. There is no choppiness when returning standard mpeg2 steams. So I thought I'd drop back and make sure there aren't other issues that need attention first. I see some errors in opendct logs that may or may not be healthy. I've attached log files. I'd very much appreciate if somebody could take a peak and let me know if there are issues that need attention?

General info:

I have 1 prime and 3 connects that are presently being used by sage.
2 extends, a prime and 1 older dual that are being used by other software and not in sage.

192.168.1.190 is the sage server
192.168.1.194 is another machine on the network running emby and nPVR.


Thanks!

Bobby

I could not find transcoding evidence in the opendct.log file probably because the service was restarted. It looks like it just detected everything and that was it. In wrapper.log which covers a much larger time range because it doesn't log any debug info, I can see while you are transcoding, the buffer is constantly getting backed up. Since you are transcoding, it would suggest that your CPU is just barely keeping up. I say barely because it doesn't looks like you're losing data, but the buffer keeps almost getting there. These conditions will definitely create a poor playback experience.

INFO   | jvm 1    | 2016/12/04 02:42:42.752 | 02:42:42.718 [NIOHTTPProducerImpl-322:HDHomeRun HDHR4-2US Tuner 1042D117-0] WARN  SeekableCircularBufferNIO - The buffer has 7863748 bytes left to be read, has only 573 bytes left for writing and 1316 bytes cannot be added. Deferring bytes to queue buffer.

I did a few quick tests on an Ivy Bridge i5 processor and I noticed that it's using a lot more CPU than I recall in the past. I re-compiled switching back from FFmpeg 3.1 to 2.8 and the usage went down to what I remembered. There were also some inexplicable issues I ran into relating to the FFmpeg upgrade a few releases ago. Normally problems with frames don't cause any serious issues, but they seem to be crashing things.

I think I'm going to roll the project back to 2.8 in the next release because I do not have the time to work out these issues and they are likely related to things that are now deprecated in 3.1 and some new default settings in x264. As I have been reading, the deprecated features are not really fully replaced and the examples still use all of the deprecated functionality. Needless to say there's just not enough guidance to make the correct adjustments without lots of trial and error.

I don't transcode other than for testing because it's very CPU intensive and completely unnecessary most of the time. It's probably not fair to compare OpenDCT with Plex. There are so many variables that effect overall performance in transcoding and I'm sure I have not tapped every possible optimization in the packaged profiles. You'll see lines that periodically report the current frame-rate that look like: DEBUG FFmpegTranscoder - FPS: 71.42857142857143. Those entries should not drop below 1 FPS of your target FPS to have smooth playback. Those entries might help you a little on determining if your profile changes are improving things are making them worse.

Also, just for reference, the fastest packaged profile is ultrafast720p30fps. I can reliably get 3-4 streams on the same i5 using that profile. 60fps is really hard on a lot of processors even at 720p. SD channels are really cheap to transcode which is why the profiles have a different costs associated with different resolutions. Most SD channels use less than 10% of the CPU on my i5 whereas HD such as 1080i30 scaled to 720p30 takes around 30%.

[BobbyDing]

Thanks so much for the response. Unfortunately for me the ultrafast720p30fps also stuttered, though it did seem to be less. I'll have another go at it after the next release. If that also stutters it gives me a reason to upgrade the hardware. What can you tell me about the following "unhandled exceptions" in my log file ?

18:47:51.070 [HDHomeRunDiscoveryReceive-47] DEBUG HDHomeRunDiscovery - HDHomerun device returned an unknown tag with the length 34
18:47:51.070 [HDHomeRunDiscoveryReceive-47] DEBUG HDHomeRunDiscovery - HDHomerun device returned an unknown tag with the length 36
18:47:51.070 [HDHomeRunDiscoveryReceive-47] DEBUG HDHomeRunDiscovery - HDHomerun device returned an unknown tag with the length 46
18:48:21.822 [SageTVRequestHandler-229:Unknown] DEBUG SageTVRequestHandler - An unhandled exception was created => java.net.SocketException: Connection reset
	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:48:21.822 [SageTVRequestHandler-230:Unknown] DEBUG SageTVRequestHandler - An unhandled exception was created => java.net.SocketException: Connection reset
	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:48:21.822 [SageTVRequestHandler-228:Unknown] DEBUG SageTVRequestHandler - An unhandled exception was created => java.net.SocketException: Connection reset
	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:48:21.822 [SageTVRequestHandler-217:Unknown] DEBUG SageTVRequestHandler - An unhandled exception was created => java.net.SocketException: Connection reset
	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:48:21.822 [SageTVRequestHandler-231:Unknown] DEBUG SageTVRequestHandler - An unhandled exception was created => java.net.SocketException: Connection reset
	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)

Thanks so much!

Bobby

[EnterNoEscape]

Originally Posted by BobbyDing

Thanks so much for the response. Unfortunately for me the ultrafast720p30fps also stuttered, though it did seem to be less. I'll have another go at it after the next release. If that also stutters it gives me a reason to upgrade the hardware. What can you tell me about the following "unhandled exceptions" in my log file ?

18:47:51.070 [HDHomeRunDiscoveryReceive-47] DEBUG HDHomeRunDiscovery - HDHomerun device returned an unknown tag with the length 34
18:47:51.070 [HDHomeRunDiscoveryReceive-47] DEBUG HDHomeRunDiscovery - HDHomerun device returned an unknown tag with the length 36
18:47:51.070 [HDHomeRunDiscoveryReceive-47] DEBUG HDHomeRunDiscovery - HDHomerun device returned an unknown tag with the length 46
18:48:21.822 [SageTVRequestHandler-229:Unknown] DEBUG SageTVRequestHandler - An unhandled exception was created => java.net.SocketException: Connection reset
	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:48:21.822 [SageTVRequestHandler-230:Unknown] DEBUG SageTVRequestHandler - An unhandled exception was created => java.net.SocketException: Connection reset
	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:48:21.822 [SageTVRequestHandler-228:Unknown] DEBUG SageTVRequestHandler - An unhandled exception was created => java.net.SocketException: Connection reset
	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:48:21.822 [SageTVRequestHandler-217:Unknown] DEBUG SageTVRequestHandler - An unhandled exception was created => java.net.SocketException: Connection reset
	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:48:21.822 [SageTVRequestHandler-231:Unknown] DEBUG SageTVRequestHandler - An unhandled exception was created => java.net.SocketException: Connection reset
	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)

Thanks so much!

Bobby

The "unknown tag" coming from the HDHomeRun is normal and can be ignored. In fact Silicondust has a comment in their own code to not log this event. I do it anyway in case it's interesting.

Those exception are normal. If it takes a little longer than SageTV would have liked for the network encoder to respond, it closes the connection, then creates a new one. Also if you restart the SageTV service while OpenDCT is still running, the connections get dropped there too. Also you might see it just because OpenDCT is shutting down. While these are exceptions, you'll notice they are flagged DEBUG which generally means these exceptions are there in case there actually is a problem, but are unlikely to ever be the source of a problem.

[BobbyDing]

OK. Thank you. Since I have 2 extends I thought I'd try those out in transcode mode with sage. Can you tell me what the possible options are for "hdhr.extend_transcode_profile="? and would I still need to select a transcode setting in the extend's setup web page? Or would opendct take care of that when it makes the tuning request?

[EnterNoEscape]

Originally Posted by BobbyDing

OK. Thank you. Since I have 2 extends I thought I'd try those out in transcode mode with sage. Can you tell me what the possible options are for "hdhr.extend_transcode_profile="? and would I still need to select a transcode setting in the extend's setup web page? Or would opendct take care of that when it makes the tuning request?

I know at least one user verified this this works well. It's a little buried in the change log, but the options are the following:

• heavy: transcode to AVC with the same resolution, frame-rate, and interlacing as the original stream. For example 1080i60 AVC 1080i60, 720p60 AVC 720p60.
• mobile: trancode to AVC progressive not exceeding 1280x720 30fps.
• internet720: transcode to low bitrate AVC progressive not exceeding 1280x720 30fps.
• internet480: transcode to low bitrate AVC progressive not exceeding 848x480 30fps for 16:9 content, not exceeding 640x480 30fps for 4:3 content.
• internet360: transcode to low bitrate AVC progressive not exceeding 640x360 30fps for 16:9 content, not exceeding 480x360 30fps for 4:3 content.
• internet240: transcode to low bitrate AVC progressive not exceeding 432x240 30fps for 16:9 content, not exceeding 320x240 30fps for 4:3 content.

I recommend heavy if you are strictly just wanting the streams to be in H.264. It would be nice to have heavy with deinterlacing, but it doesn't appear that they considered that people might not want to trust their playback device to do a decent job in that area. You should not need to select anything on the device web page itself.

[BobbyDing]

Ah, I should have thought of that. I also found where you suggested to another use to set the extend tuner values for sagetv.device.<unique_id>.consumer to opendct.consumer.RawSageTVConsumerImpl. So I'll try that as well.

Thanks!!

Bobby
.

[EnterNoEscape]

Originally Posted by BobbyDing

Ah, I should have thought of that. I also found where you suggested to another use to set the extend tuner values for sagetv.device.<unique_id>.consumer to opendct.consumer.RawSageTVConsumerImpl. So I'll try that as well.

Thanks!!

Bobby
.

No problem. I think that suggestion was prior to me fixing FFmpeg to be smart enough to figure out when the program came in as a different number than originally expected. It wasted a fair amount of time not getting it in that case and would eventually stream, but only after something like 15-20 seconds.

[NetworkGuy]

Originally Posted by sflamm

I'm running an old firmware version 20130328 - is that the issue? (haven't upgraded in a long long time)

When I switched to OpenDCT, I also had old firmware on the HDHomeRun tuners and it would not work. Once I upgraded the firmware, it worked fine.

[HokiePerogi]

I keep having sporadic issues with SageTV only recording a screen that says COPY NEVER. I'm trying to troubleshoot where my issue really lies.

Is my InfiniTV4 (PCIe) the one outputting this video with the COPY NEVER text and then OpenDCT is transcoding it? Or is it OpenDCT that is producing the video with the COPY NEVER text.

This is happening on network tv. In last night's case, trying to record Survivor on channel 509 (CBS). I have FiosTV and live in Round Hill, VA.

I haven't been able to piece together a pattern to when this happens. It seems to happen on different channels and different shows each each. Could FiosTV really be messing around with the copy never flags that often? Maybe there's an issue with my cable card or InfiniTV4 (PCIe)?

Interesting enough, I just discovered that if I jump 45 seconds or so into the recording, it fixed itself. SageTV also reported a halt detected in the recording.

[EnterNoEscape]

Originally Posted by HokiePerogi

I keep having sporadic issues with SageTV only recording a screen that says COPY NEVER. I'm trying to troubleshoot where my issue really lies.

Is my InfiniTV4 (PCIe) the one outputting this video with the COPY NEVER text and then OpenDCT is transcoding it? Or is it OpenDCT that is producing the video with the COPY NEVER text.

This is happening on network tv. In last night's case, trying to record Survivor on channel 509 (CBS). I have FiosTV and live in Round Hill, VA.

I haven't been able to piece together a pattern to when this happens. It seems to happen on different channels and different shows each each. Could FiosTV really be messing around with the copy never flags that often? Maybe there's an issue with my cable card or InfiniTV4 (PCIe)?

Interesting enough, I just discovered that if I jump 45 seconds or so into the recording, it fixed itself. SageTV also reported a halt detected in the recording.

The InfiniTV 4 doesn't ignore CGMS (analog copy protection) and unlike the InfiniTV 6, there isn't any firmware you can upgrade to get it to stop. CBS is notorious for carrying that flag on FiOS. The message you are seeing is coming from OpenDCT as a helpful message on why the channel will not record. Because of this flag, the InfiniTV generally will stop streaming and all OpenDCT can do it re-tune in the channel which provides for a rocky TV watching experience. You can disable the messages from OpenDCT, but your experience with CBS will likely continue to be poor at times.

To disable the copy protection videos, do the following:
1. Stop the OpenDCT service.
2. Open opendct.properties.
3. Change the property error_videos_enabled=true to error_videos_enabled=false
4. Save the changes.
5. Start the OpenDCT service.

[HokiePerogi]

Originally Posted by EnterNoEscape

The InfiniTV 4 doesn't ignore CGMS (analog copy protection) and unlike the InfiniTV 6, there isn't any firmware you can upgrade to get it to stop. CBS is notorious for carrying that flag on FiOS. The message you are seeing is coming from OpenDCT as a helpful message on why the channel will not record. Because of this flag, the InfiniTV generally will stop streaming and all OpenDCT can do it re-tune in the channel which provides for a rocky TV watching experience. You can disable the messages from OpenDCT, but your experience with CBS will likely continue to be poor at times.

To disable the copy protection videos, do the following:
1. Stop the OpenDCT service.
2. Open opendct.properties.
3. Change the property error_videos_enabled=true to error_videos_enabled=false
4. Save the changes.
5. Start the OpenDCT service.

So are you saying that if I get a new, firmware upgradable, CC network tuning device, the problem would go away?

[EnterNoEscape]

Originally Posted by HokiePerogi

So are you saying that if I get a new, firmware upgradable, CC network tuning device, the problem would go away?

Essentially, yes.

You wouldn't need to get rid of your InfiniTV 4. I still have one. I'm using it as a ClearQAM tuner (through OpenDCT). Even without a CableCARD installed, if it sees a CGMS flag that is copy once or copy never, it will still stop streaming, so I just don't use it to tune into CBS. Other than that, it has been working great for my local channels which FiOS sends unencrypted.

[Jabroni]

Thanks for this great addon for the SageTV! Just got my first HDMI Network Encoder Tuner working and its great

Now I got a question, is it possible to add a remote HDHomeRun Extend to the encoder list? I see it uses just UPNP to discover local devices and seems it just switches then to HTTP for the API communication

[EnterNoEscape]

Originally Posted by Jabroni

Thanks for this great addon for the SageTV! Just got my first HDMI Network Encoder Tuner working and its great

Now I got a question, is it possible to add a remote HDHomeRun Extend to the encoder list? I see it uses just UPNP to discover local devices and seems it just switches then to HTTP for the API communication

For Ceton devices, it uses UPnP for detection. For HDHomeRun devices, it uses their proprietary discovery protocol. It will then use HTTP if a URL provided by the HDHomeRun matches the channel requested by SageTV, otherwise it uses the the proprietary HDHomeRun protocol to configure RTP.

The extend should already be on your list of devices since you are at least running 0.5.3 to be using the generic HTTP capture device. You might need to scroll down within the sources when adding in SageTV. I chose not to specially denote the non-Prime HDHomeRun capture devices since the names are already long enough. You should be able to tell they are coming from OpenDCT because they will look like other network encoders do with the <ip_address/hostname>:<port> being appended.

[Jabroni]

Originally Posted by EnterNoEscape

For Ceton devices, it uses UPnP for detection. For HDHomeRun devices, it uses their proprietary discovery protocol. It will then use HTTP if a URL provided by the HDHomeRun matches the channel requested by SageTV, otherwise it uses the the proprietary HDHomeRun protocol to configure RTP.

The extend should already be on your list of devices since you are at least running 0.5.3 to be using the generic HTTP capture device. You might need to scroll down within the sources when adding in SageTV. I chose not to specially denote the non-Prime HDHomeRun capture devices since the names are already long enough. You should be able to tell they are coming from OpenDCT because they will look like other network encoders do with the <ip_address/hostname>:<port> being appended.

For example this is how the .properties file added for a local HDHomeRun Extend i have on my LAN

sagetv.device.-1711104409.always_force_external_unlock=false
sagetv.device.-1711104409.consumer=opendct.consumer.DynamicConsumerImpl
sagetv.device.-1711104409.delay_to_wait_after_tuning=0
sagetv.device.-1711104409.device_name=HDHomeRun HDTC-2US Tuner 11111111-1
sagetv.device.-1711104409.encoder_listen_port=9000
sagetv.device.-1711104409.encoder_merit=0
sagetv.device.-1711104409.encoder_pool=atsc_11111111
sagetv.device.-1711104409.exclusive_server_address=
sagetv.device.-1711104409.fast_network_encoder_switch=true
sagetv.device.-1711104409.last_channel=-1
sagetv.device.-1711104409.transcode_profile=
sagetv.device.-1711104410.always_force_external_unlock=false
sagetv.device.-1711104410.consumer=opendct.consumer.DynamicConsumerImpl
sagetv.device.-1711104410.delay_to_wait_after_tuning=0
sagetv.device.-1711104410.device_name=HDHomeRun HDTC-2US Tuner 11111111-0
sagetv.device.-1711104410.encoder_listen_port=9000
sagetv.device.-1711104410.encoder_merit=0
sagetv.device.-1711104410.encoder_pool=atsc_11111111
sagetv.device.-1711104410.exclusive_server_address=
sagetv.device.-1711104410.fast_network_encoder_switch=true
sagetv.device.-1711104410.last_channel=-1
sagetv.device.-1711104410.transcode_profile=

How would I define an external HDHomerun Extend that it isnt on my local network? Lets say its on another subnet or over the net (where discovery protocol wont see it, however im able to stream from it via other means like VLC)

[Fuzzy]

Originally Posted by Jabroni

How would I define an external HDHomerun Extend that it isnt on my local network? Lets say its on another subnet or over the net (where discovery protocol wont see it, however im able to stream from it via other means like VLC)

I don't think OpenDCT will work with a device it can't discover.

[Jabroni]

Originally Posted by Fuzzy

I don't think OpenDCT will work with a device it can't discover.

Guess then the feature it would require to work is to allow parameters for the Generic HTTP Capture Device .streaming_url just as in the .tunning_executable ( %c% ) in order to pass the channel number in the url??

HDHomeRuns Extends lets you open a stream via HTTP like:

http://<device.ip>:5004/auto/v<channel to transcode>?transcode=heavy

That wouldn't need its software installed locally or the need to discover the device

[EnterNoEscape]

Originally Posted by Jabroni

Guess then the feature it would require to work is to allow parameters for the Generic HTTP Capture Device .streaming_url just as in the .tunning_executable ( %c% ) in order to pass the channel number in the url??

HDHomeRuns Extends lets you open a stream via HTTP like:

http://<device.ip>:5004/auto/v<channel to transcode>?transcode=heavy

That wouldn't need its software installed locally or the need to discover the device

You mostly described how OpenDCT streams using HTTP. It also supports defining the transcode property for extend users like yourself. OpenDCT was not really designed to work with capture devices that it cannot detect. The design was to make it as easy as possible for users to get working without a GUI. If you run a channel scan on the extend, then you will have those URL's you are describing, but if for some reason a channel would not be on that list, the URL will fail and OpenDCT will fallback to RTP which will not work in the scenario you are describing.

If you have devices on another subnet, the easiest solution would be to run OpenDCT on a computer that is also on that subnet. Then you would need to manually create the capture device entries for SageTV because it won't be able to detect OpenDCT when it's running on a different subnet. You will have a more stable stream (especially if there's any significant latency) by having OpenDCT stream it instead of accessing the stream remotely using OpenDCT because OpenDCT will buffer the stream whereas the HDHomeRun will drop the data much more readily.

The variable doesn't work in the URL's, but I can't really see any reason why I couldn't add support for that. It just will not work cleanly for ATSC since SageTV and the HDHomeRun disagree on notation in that regard.