OpenDCT: An open source digital cable tuner.

[EnterNoEscape]

Unfortunately I don't see anything particularly bad in in your logs. I see the streams being quickly detected and the recordings starting fairly quickly. What specifically are the problems you're having?

[Telecore]

Towards the end of the file there is an example of errors when trying to tune the Wisconsin-Michigan game on ABC - I got "no signal" on repeated attempts but tuned many other channels just to make sure they were OK. I see some errors in the log file, such as "Returning AVERROR_EOF in readCallback.call()", "PES packet size mismatch" and others - just providing this to you in case there is anything significant. I ended up re-booting the sage server and now I can tune in the game.

[EnterNoEscape]

Originally Posted by Telecore

Towards the end of the file there is an example of errors when trying to tune the Wisconsin-Michigan game on ABC - I got "no signal" on repeated attempts but tuned many other channels just to make sure they were OK. I see some errors in the log file, such as "Returning AVERROR_EOF in readCallback.call()", "PES packet size mismatch" and others - just providing this to you in case there is anything significant. I ended up re-booting the sage server and now I can tune in the game.

Those are normal errors. I know it's hard to tell why you're seeing what you're seeing. This is doubly true when you're looking at things being returned from FFmpeg. I filter a lot of that logging because it will tell you every little detail you don't need to know about your stream. Here's why you see those errors in the logs.

Returning AVERROR_EOF in readCallback.call() - This is returned when the writer has been told to stop writing (usually because SageTV asked for us to stop). It triggers the FFmpeg remuxing process to stop accepting any further data and to clean up.

PES packet size mismatch - This typically happens at the start of a stream, but can happen in the middle for similar reasons. This essentially means we missed a little data that was a part of a video packet. At the start of a stream, this usually is because we are cutting into the stream in the middle of a video packet, so we aren't going to have the entire packet. If it happens during a recording, usually that means we might have had a brief signal issue or network disruption. If it happens constantly throughout one recording that's a sign that there is either significant signal degradation, network problems or the computer is under a lot of stress and when this happens you will know it when you're watching the recording. This can also result in a perfectly fine video packet that just didn't have the size FFmpeg was told to expect.

Based on what I saw in the logs, those files should have been ok. I suspect that might have been an issue on the SageTV side of things in properly getting the video and audio format of those files. Are you on the latest version of SageTV 9? There were some fixes several months ago for those kinds of issues.

[Telecore]

Yes I'm running 9.0.8.429 - used the latest Windows EXE a few days ago. Thanks for looking at this - I'll keep an eye open, other then this, OpenDCT has worked extremely well for a long time.

[EnterNoEscape]

Originally Posted by Telecore

Yes I'm running 9.0.8.429 - used the latest Windows EXE a few days ago. Thanks for looking at this - I'll keep an eye open, other then this, OpenDCT has worked extremely well for a long time.

Any time. The biggest changes recently are the FFmpeg version was bumped up to the latest and I greatly reduced the amount of data that needs to be written out before OpenDCT will return OK when starting a recording due to some problems people were having with very long delays. The latter change might have the biggest chance of creating problems if SageTV is still having detection issues.

[tmiranda]

The cable company changed my channels around again OpenDCT hasn't picked up the changes. What do I need to do?

I'm getting errors in the logfile:

09:06:52.978 [WrapperSimpleAppMain] INFO Main - Starting OpenDCT 0.4.49...
09:06:53.010 [WrapperSimpleAppMain] DEBUG Config - OSVersion is parsing the name 'Windows 7'.
09:06:53.010 [WrapperSimpleAppMain] DEBUG Config - OSVersion determined that 'Windows 7' is WINDOWS.
09:06:53.056 [WrapperSimpleAppMain] INFO Main - OpenDCT logging to the directory 'c:/ProgramData/OpenDCT/logs'.
09:06:53.089 [WrapperSimpleAppMain] INFO UpnpManager - Logging Cling UPnP to 'c:/ProgramData/OpenDCT/logs\opendct_cling.log'.
09:06:53.089 [WrapperSimpleAppMain] DEBUG UpnpManager - Logging level for Cling UPnP is set to 'severe'.
09:06:53.090 [FFmpegAsyncInit-20] INFO Main - FFmpeg loading...
09:06:53.211 [WrapperSimpleAppMain] INFO NetworkPowerEventManger - Network interfaces which are up and have an IP4 address are:
name:eth4 (Realtek PCIe GBE Family Controller) 192.168.1.17
09:06:53.212 [WrapperSimpleAppMain] DEBUG WindowsPowerMessagePump - 'class opendct.power.NetworkPowerEventManger' is now listening.
09:06:53.215 [WrapperSimpleAppMain] DEBUG WindowsPowerMessagePump - 'class opendct.sagetv.SageTVManager' is now listening.
09:06:53.360 [WrapperSimpleAppMain] INFO UpnpManager - Starting UPnP services...
09:06:53.453 [WrapperSimpleAppMain] INFO DCTDefaultUpnpServiceConfiguration - Using the interface 'eth4' with IP address 192.168.1.17 for UPnP discovery.
09:06:53.583 [WrapperSimpleAppMain] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
09:06:53.596 [WrapperSimpleAppMain] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-dkeystone-com' devices...
09:06:53.597 [WrapperSimpleAppMain] DEBUG WindowsPowerMessagePump - 'class opendct.tuning.upnp.UpnpManager' is now listening.
09:06:53.598 [UPnPDiscovery-34] INFO UpnpManager - UPnP discovery thread has started.
09:06:53.709 [cling-7] DEBUG RegisterDevice - Checking if the schema 'schemas-upnp-org' can be used...
09:06:53.972 [WrapperSimpleAppMain] DEBUG Config - OSVersion is parsing the name 'Windows 7'.
09:06:53.972 [WrapperSimpleAppMain] DEBUG Config - OSVersion determined that 'Windows 7' is WINDOWS.
09:06:53.972 [WrapperSimpleAppMain] DEBUG Config - OSVersion is parsing the name 'Windows 7'.
09:06:53.972 [WrapperSimpleAppMain] DEBUG Config - OSVersion determined that 'Windows 7' is WINDOWS.
09:06:54.026 [cling-6] DEBUG RegisterDevice - Checking if the schema 'schemas-dkeystone-com' can be used...
09:06:54.055 [WrapperSimpleAppMain] DEBUG WindowsPowerMessagePump - 'class opendct.tuning.discovery.DiscoveryManager' is now listening.
09:06:54.055 [HDHomeRunDiscoverySend-41] INFO HDHomeRunDiscovery - HDHomeRun discovery sender thread started.
09:06:54.056 [HDHomeRunDiscoveryReceive-41] INFO HDHomeRunDiscovery - HDHomeRun discovery receive thread for /192.168.1.255:65001 broadcast started.
09:06:54.056 [WrapperSimpleAppMain] DEBUG WindowsPowerMessagePump - 'class opendct.channel.ChannelManager' is now listening.
09:06:54.057 [HDHomeRunDiscoverySend-41] INFO HDHomeRunDiscovery - Broadcasting HDHomeRun discovery packet to /192.168.1.255:65001...
09:06:54.064 [WrapperSimpleAppMain] INFO Main - Running in daemon mode...
09:06:54.064 [HDHomeRunDiscoveryReceive-41] DEBUG HDHomeRunControl - key: '/tuner0/lockkey' value: 'null' lockKey: '0' sendLength: 26
09:06:54.067 [HDHomeRunDiscoveryReceive-41] DEBUG HDHomeRunControl - key: '/tuner1/lockkey' value: 'null' lockKey: '0' sendLength: 26
09:06:54.068 [HDHomeRunDiscoveryReceive-41] DEBUG HDHomeRunControl - key: '/tuner2/lockkey' value: 'null' lockKey: '0' sendLength: 26
09:06:54.069 [HDHomeRunDiscoveryReceive-41] DEBUG HDHomeRunDiscovery - HDHomerun device returned an unknown tag with the length 34
09:06:54.069 [HDHomeRunDiscoveryReceive-41] DEBUG HDHomeRunControl - key: '/sys/hwmodel' value: 'null' lockKey: '0' sendLength: 23
09:06:54.070 [HDHomeRunDiscoveryReceive-41] INFO HDHomeRunDiscoverer - Discovered a new HDHomeRun device 'HDHomeRun DRI Tuner 131276A4'.
09:06:54.257 [HDHomeRunDiscoverySend-41] INFO HDHomeRunDiscovery - Broadcasting HDHomeRun discovery packet to /192.168.1.255:65001...
09:06:57.599 [UPnPDiscovery-34] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
09:06:57.599 [UPnPDiscovery-34] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-dkeystone-com' devices...
09:07:01.608 [UPnPDiscovery-34] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
09:07:01.608 [UPnPDiscovery-34] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-dkeystone-com' devices...
09:07:05.618 [UPnPDiscovery-34] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
09:07:05.618 [UPnPDiscovery-34] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-dkeystone-com' devices...
09:07:09.627 [UPnPDiscovery-34] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
09:07:09.627 [UPnPDiscovery-34] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-dkeystone-com' devices...
09:07:13.636 [UPnPDiscovery-34] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
09:07:13.636 [UPnPDiscovery-34] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-dkeystone-com' devices...
09:07:17.645 [UPnPDiscovery-34] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
09:07:17.645 [UPnPDiscovery-34] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-dkeystone-com' devices...
09:07:18.410 [WindowsPowerMessagePump] INFO WindowsPowerMessagePump - Message pump started.
09:07:21.654 [UPnPDiscovery-34] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
09:07:21.654 [UPnPDiscovery-34] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-dkeystone-com' devices...
09:07:25.664 [UPnPDiscovery-34] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-cetoncorp-com' devices...
09:07:25.664 [UPnPDiscovery-34] DEBUG UpnpManager - Sending a SecureContainer search message for 'schemas-dkeystone-com' devices...
09:07:25.664 [UPnPDiscovery-34] INFO UpnpManager - UPnP discovery thread has stopped.
09:07:32.035 [cling-11] DEBUG RegisterDevice - Checking if the schema 'schemas-upnp-org' can be used...
09:08:24.071 [ChannelManager-44] INFO ChannelManager - Updating the HDHomeRun channel lineup HDHomeRun DRI Tuner 131276A4 (dct_hdhomerun).
09:08:24.071 [ChannelManager-44] INFO HDHomeRunChannels - Connecting to Prime DCT using the URL 'http://192.168.1.3:80/lineup.xml'
09:08:28.564 [cling-11] DEBUG RegisterDevice - Checking if the schema 'schemas-upnp-org' can be used...
09:08:45.085 [ChannelManager-44] DEBUG HDHomeRunChannels - populateChannels created an unexpected exception => java.net.ConnectException: Connection timed out: connect
at java.net.DualStackPlainSocketImpl.connect0(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at sun.net.NetworkClient.doConnect(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.<init>(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.http://www.protocol.http.HttpURLConn...Client(Unknown Source)
at sun.net.http://www.protocol.http.HttpURLConn...nnect0(Unknown Source)
at sun.net.http://www.protocol.http.HttpURLConn...onnect(Unknown Source)
at sun.net.http://www.protocol.http.HttpURLConn...onnect(Unknown Source)
at opendct.channel.updater.http.HDHomeRunChannels.populateChannels(HDHomeRunChannels.java:143)
at opendct.channel.ChannelManager.updateChannelLineup(ChannelManager.java:476)
at opendct.channel.ChannelManager.updateChannelLineups(ChannelManager.java:462)
at opendct.channel.ChannelManager$2.run(ChannelManager.java:669)
at java.lang.Thread.run(Unknown Source)

09:08:45.085 [ChannelManager-44] INFO ChannelManager - The static channel lineup HDHomeRun HDHR-US 10102DF2 (qam_hdhomerun_legacy) will remain unchanged.
09:09:45.738 [cling-20] DEBUG RegisterDevice - Checking if the schema 'schemas-upnp-org' can be used...

[EnterNoEscape]

Is 192.168.1.3 the IP address of the HDHomeRun Prime? The error would suggest that OpenDCT has the wrong IP address. Version 0.4 stores the IP address of the HDHomeRun which can change. This was addressed later in 0.5 which uses the ID and looks up the IP address every time, but you can also just change the IP address in the lineup folder. The file name will likely be prime_dct.properties, what you can do is delete that file and OpenDCT should re-create it with the new IP address.

[tmiranda]

Originally Posted by EnterNoEscape

Is 192.168.1.3 the IP address of the HDHomeRun Prime? The error would suggest that OpenDCT has the wrong IP address. Version 0.4 stores the IP address of the HDHomeRun which can change. This was addressed later in 0.5 which uses the ID and looks up the IP address every time, but you can also just change the IP address in the lineup folder. The file name will likely be prime_dct.properties, what you can do is delete that file and OpenDCT should re-create it with the new IP address.

I deleted the file and got the same error.

[EnterNoEscape]

Originally Posted by tmiranda

I deleted the file and got the same error.

I forgot to mention, stop the OpenDCT service, then delete the file, the start it back up.

Can you open http://192.168.1.3:80/lineup.xml in a browser on the same computer?

[EnterNoEscape]

I should also mention that just because the channel map isn't being downloaded, should not prevent you from being able to tune into the channels in SageTV. Not having that list only effects what channels get enabled during channel scanning.

[tmiranda]

Originally Posted by EnterNoEscape

I should also mention that just because the channel map isn't being downloaded, should not prevent you from being able to tune into the channels in SageTV. Not having that list only effects what channels get enabled during channel scanning.

I took the opportunity to upgrade to 0.5.11 and now it's all working again. Thanks

[tmiranda]

Forgot to mention. I like the way that OpenDCT displays "Copy Once" if you try to tune DRMed content. That's a nice touch.

[EnterNoEscape]

Originally Posted by tmiranda

Forgot to mention. I like the way that OpenDCT displays "Copy Once" if you try to tune DRMed content. That's a nice touch.

I had no idea how convenient that would be until it was there.

[BobbyDing]

Hi,


I'm presently running openDCT on a windows box that is the main server for the home with openDCT running. Can I run (test) Fuzzy's Docker version without conflict with windows version (assuming they don't try to access the same tuner at the same time)? or should the windows version be stopped while testing the Docker version???

Thanks!!

Bobby

[EnterNoEscape]

Originally Posted by BobbyDing

Hi,


I'm presently running openDCT on a windows box that is the main server for the home with openDCT running. Can I run (test) Fuzzy's Docker version without conflict with windows version (assuming they don't try to access the same tuner at the same time)? or should the windows version be stopped while testing the Docker version???

Thanks!!

Bobby

They can both be running, just make sure you positively know what is using what. It can get a little confusing with so many IP addresses. You could alternatively use upload ID and just use one copy of OpenDCT on either Windows or Linux.

[Fuzzy]

They should both exist on the network at the same time. OpenDCT will only lock a tuner when it is in use, and leave it free when not, so if the Docker OpenDCT is recording something, the Windows OpenDCT might not be able to (the pooling feature in OpenDCT, if used, would help get around this). As far as sage is concerned, the two different OpenDCT servers would be represented as two different sources per actual tuner, just with different IP addresses. This actually makes migration easy, as you can fire up the OpenDCT in the docker, restart sage (so it can detect the new network encoder), then add those sources to sage, using the same lineup you use for the windows openDCT sources. You can then remove the windows OpenDCT sources from sage, and shut down that server.

[Fuzzy]

The current docker image is using an older version of OpenDCT (0.5.7 I think). I intend to duplicate the way Stuckless is updating sage in his docker, but have not gotten a chance to do so yet.

[EnterNoEscape]

Originally Posted by Fuzzy

So, I created a docker template for OpenDCT. As far as I can tell on my end, it's working okay (only tested media server mode - because I can't see a reason to use anything else). If anyone wants to give it a try, the repository for it should be at:

https://github.com/crazifuzzy/opendct-docker

In unRAID, add that to your docker repositories, and you can probably create a new container using all defaults.

I took a quick look at your template and I just wanted to say that you shouldn't actually need to persist /opt/opendct. All configuration data is under /etc/opendct since that's where Debian wants you to put that kind of data.

[Fuzzy]

Originally Posted by EnterNoEscape

I took a quick look at your template and I just wanted to say that you shouldn't actually need to persist /opt/opendct. All configuration data is under /etc/opendct since that's where Debian wants you to put that kind of data.

Been a while since I built it, so i'll need to look at it later to see what I was doing. I think I got inspiration from the sagetv docker. I think I just did that for troubleshooting perhaps. I think wrapper.log is written in there, so that may have been what I was looking for. Never really did clean it up for public use (I am really bad about getting something functional but not complete, and forgetting about it).

[BobbyDing]

So of course I couldn't wait to try it. Installed fine. Runs immediately. I get nothing when selecting the webUI. Should I? It looks like from the log file that openDCT starts and sees the tuners, but they don't show in the ADD TUNERS section of Sage. Do I need to change a line in sage.properties so it looks for the networked tuners?

Thanks,

Bobby


UPDATE: I went ahead and changed the line discover_networked_tuners to true and it does find the windows openDCT (can tell by the IP), but not the docker openDCT. Is there something else that needs to be changed? The openDCT log file shows no errors.