OpenDCT: An open source digital cable tuner.

[thomaszoo]

So in the log I noticed "The channel '1742' does not have a frequency on the lineup 'qam_hdhomerun_1073439b". Attached is the qam_hdhomerun_1073439b.properties from the lineup directory. I'm not sure how it is generated or what it should look like.

[KryptoNyte]

1) Is there a Ceton tuner installed in some computer on your home network, the same network that the Quatro is on?

2) Is the Ceton tuner installed in the same machine that you are using to try and get the Quatro working in SageTV?

[thomaszoo]

Originally Posted by KryptoNyte

1) Is there a Ceton tuner installed in some computer on your home network, the same network that the Quatro is on?

2) Is the Ceton tuner installed in the same machine that you are using to try and get the Quatro working in SageTV?

I did have a working Ceton tuner until 2 or 3 weeks ago. It stopped working; I removed the card and uninstalled the software.

[KryptoNyte]

Okay, because remnants of a Ceton tuner are showing up in your log, and that is one thing that may be creating the tuning [frequency] confusion. I think OpenDCT somehow sees that tuner on initial configuration and it may have a negative impact on how the Quatro is tuned.

Make sure that you don't have any other tuners on your test system, and aren't attempting to use Premium TV and Antenna TV on the Quatro at the same time.

[thomaszoo]

I see that. It is even showing up on machines that did not have the ceton card in them (I guess OpenDCT made them into networked tuners). I'm not sure what I can do to further purge Ceton from my system. Are there registry keys OpenDCT uses?

[EnterNoEscape]

Originally Posted by tmiranda

I checked and it was set to true. I changed it back to false and it didn't help. The recordings are still very pixelated. Log attached.

We're still dropping packets like crazy. I'm not sure what else to have you do other than try a different NIC (preferably an Intel NIC).

[KryptoNyte]

Originally Posted by thomaszoo

I see that. It is even showing up on machines that did not have the ceton card in them (I guess OpenDCT made them into networked tuners). I'm not sure what I can do to further purge Ceton from my system. Are there registry keys OpenDCT uses?

I don't know, but I'm thinking that if you would set this up on a machine that never had a Ceton card in it, you would be mirroring my setup and we'd have the best chance at getting this running. Ceton actually installs the device as a network encoder, which is why OpenDCT sees it. If it's not installed or running on the network, other PC's on the network should not be able to see it, and should have no record of it.

You sure you have the Windows Defender Firewall SERVICE completely disabled, and after rebooting, checking to make sure?

Your log files aren't throwing any Java errors, and the Windows 10 firewall is the only other thing my install had issue with. And possibly the ceton card being on the network I suppose, never confirmed that.

Next time you take a run at this, please post the OpenDCT and the Sagetv log file from the same run.

[JustFred]

Originally Posted by EnterNoEscape

We're still dropping packets like crazy. I'm not sure what else to have you do other than try a different NIC (preferably an Intel NIC).

If there's any networking equipment (switches, etc) in the path, it might be worth rebooting them. I've got a couple of Trendnet 24-port switches that occasionally start eating packets for no apparent reason.

[tmiranda]

Originally Posted by EnterNoEscape

We're still dropping packets like crazy. I'm not sure what else to have you do other than try a different NIC (preferably an Intel NIC).

Something weird is happening for sure. It's a brand new machine with an Intel NIC onboard. When I checked for dropped packets (using ifconfig, or something like that) the output tells me there are no dropped packets.

[thomaszoo]

Originally Posted by KryptoNyte

I don't know, but I'm thinking that if you would set this up on a machine that never had a Ceton card in it, you would be mirroring my setup and we'd have the best chance at getting this running. Ceton actually installs the device as a network encoder, which is why OpenDCT sees it. If it's not installed or running on the network, other PC's on the network should not be able to see it, and should have no record of it.

You sure you have the Windows Defender Firewall SERVICE completely disabled, and after rebooting, checking to make sure?

Your log files aren't throwing any Java errors, and the Windows 10 firewall is the only other thing my install had issue with. And possibly the ceton card being on the network I suppose, never confirmed that.

Next time you take a run at this, please post the OpenDCT and the Sagetv log file from the same run.

So I set out to do just that this morning. Using my laptop that obviously never had the card installed in it I ran through the whole setup. It keeps finding some remnants of the card even though it isn't installed anywhere. I even tried setting up an isolated network with only my laptop and the Quatro on it. Still had entries in the DCT log about ceton.

There's gremlins in there for sure (UPNP maybe?). For now I've set it up to record via plex. Not ideal, but it is a short term solution. I'll give it a try in a day or two.

Wayne

[jusjoken]

Originally Posted by thomaszoo

So I set out to do just that this morning. Using my laptop that obviously never had the card installed in it I ran through the whole setup. It keeps finding some remnants of the card even though it isn't installed anywhere. I even tried setting up an isolated network with only my laptop and the Quatro on it. Still had entries in the DCT log about ceton.

There's gremlins in there for sure (UPNP maybe?). For now I've set it up to record via plex. Not ideal, but it is a short term solution. I'll give it a try in a day or two.

Wayne

Just a stab in the dark but perhaps check any running sage system on the network and see if there are properties entries related to the removed card and delete those lines (after having a backup of course) while sage and opendct are off and then restart sage and opendct.

k

[jusjoken]

Originally Posted by tmiranda

I checked and it was set to true. I changed it back to false and it didn't help. The recordings are still very pixelated. Log attached.

Are you sure the setting is sticking. I seem to recall other issues on an unraid setup where opendct settings were not sticking.

k

[EnterNoEscape]

Originally Posted by jusjoken

Are you sure the setting is sticking. I seem to recall other issues on an unraid setup where opendct settings were not sticking.

k

Unless you're talking about something else, that's because Fuzzy set up the startup script of the Docker container to override the opendct properties because of a misunderstanding. The override is no longer needed and should be removed from the Docker startup script. I believe it only changes the default consumer to use the SageTV MediaServer remuxer which I really don't recommend since it is not as good as FFmpeg at correcting stream errors.

Based on the fact that I am seeing FFmpeg being used here, I'm not sure that's how this particular problem happened.

[jusjoken]

Originally Posted by EnterNoEscape

Unless you're talking about something else, that's because Fuzzy set up the startup script of the Docker container to override the opendct properties because of a misunderstanding. The override is no longer needed and should be removed from the Docker startup script. I believe it only changes the default consumer to use the SageTV MediaServer remuxer which I really don't recommend since it is not as good as FFmpeg at correcting stream errors.

Based on the fact that I am seeing FFmpeg being used here, I'm not sure that's how this particular problem happened.

Yes, thats the one I was partially recalling... incorrectly it seems

[tmiranda]

Originally Posted by jusjoken

Are you sure the setting is sticking. I seem to recall other issues on an unraid setup where opendct settings were not sticking.

k

I'm not using the docker. It's the latest Ubuntu LTS release.

Networking is not my strong point and I'm not sure where to look next. When I ran ifconf -i I looked at the output and the numbers under TX drops and RX drops were 0.

Pointers welcome. I've not been able to make new recordings for months

[thomaszoo]

Originally Posted by jusjoken

Just a stab in the dark but perhaps check any running sage system on the network and see if there are properties entries related to the removed card and delete those lines (after having a backup of course) while sage and opendct are off and then restart sage and opendct.

k

All other SageTV and OpenDCT services were shut down. Yesterday I even did it on an isolated system and I still saw it.

I've actually deleted all of the tuners, shut down the firewall (public and private), uninstalled OpenDCT and removed the remaining directories, rebooted, and then reinstalled OpenDCT, ran as console, started service, restarted sage and added a tuner back in. And still seeing Ceton in the logs. And it still doesn't work.

[KryptoNyte]

It looks to me like all the references to Ceton in that log are normal for OpenDCT searching the network and not finding it, so I think you're okay in that respect.

At this point, I think we'll have to ask ENE if he can determine what it is that's creating that message;

ERROR HDHRNativeCaptureDevice - The channel '1110' does not have a frequency on the lineup 'qam_hdhomerun_1073439b'.

and how we can resolve it.

Just out of curiosity, every time you post an OpenDCT log, it appears that you attempt to tune channel 2 before anything else. I do not understand that.

[thomaszoo]

Originally Posted by KryptoNyte

It looks to me like all the references to Ceton in that log are normal for OpenDCT searching the network and not finding it, so I think you're okay in that respect.

So it sounds like I don't need to worry about Ceton going forward.

At this point, I think we'll have to ask ENE if he can determine what it is that's creating that message;

ERROR HDHRNativeCaptureDevice - The channel '1110' does not have a frequency on the lineup 'qam_hdhomerun_1073439b'.

and how we can resolve it.

Just out of curiosity, every time you post an OpenDCT log, it appears that you attempt to tune channel 2 before anything else. I do not understand that.

I don't even have anything on channel two, so I'm not sure what that is. I'm not doing anything to try and tune channel 2.

[KarylFStein]

Have you done a channel scan from the HDHR interface, (not in SageTV)? Maybe try that.

[thomaszoo]

Originally Posted by KarylFStein

Have you done a channel scan from the HDHR interface, (not in SageTV)? Maybe try that.

I've done that multiple times. the SCN files only contains "# Generated by HDHomeRun Setup". I have two of the older duals that have frq files for OTA with lots of information about the channels. for example, it contains the line
"CH:33 major:3 minor:1 prog:1 phy:35 frq:597250000 #:KCRA-TV"

I would expect something similar for the SCN files. I'd like to see someone else's with a working system. Maybe I could even use theirs.

Wayne