OpenDCT: An open source digital cable tuner.

[EnterNoEscape]

Originally Posted by BobbyDing

Here's all the logs. Prime Tuner 131F16FF-2 is the tuner presently assigned to sage. Thanks so much!
.

Unless you created it, ultrafast720p30 isn't a valid profile. It's ultrafast720p30fps

[BobbyDing]

Originally Posted by EnterNoEscape

Unless you created it, ultrafast720p30 isn't a valid profile. It's ultrafast720p30fps

Yes, that was it. Such a dumb mistake

Two questions:

I notice that the stations that are already 720 do not get trans coded to .264 and remain mpg2 (ABC). Is this decision made because it's already 720?

Also, although the lineup.properties files are created, they are not being populated (they are populated on my windows machine). I don't think this effects me at all (is that just for Ceton? tuners?). Just curious why it's not happening.

Thanks so much!

Bobby

[EnterNoEscape]

Originally Posted by BobbyDing

Yes, that was it. Such a dumb mistake

Two questions:

I notice that the stations that are already 720 do not get trans coded to .264 and remain mpg2 (ABC). Is this decision made because it's already 720?

Also, although the lineup.properties files are created, they are not being populated (they are populated on my windows machine). I don't think this effects me at all (is that just for Ceton? tuners?). Just curious why it's not happening.

Thanks so much!

Bobby

I believe that particular profile is geared towards getting rid of interlaced MPEG2 1080i content. The profiles are very commented inside, but it still might be hard to follow if you aren't a little familiar with FFmpeg. You'll want to make a copy of the profile before making changes. The reason is also in the comments. This is the line you're interested in changing:

# A codec can be mapped to another codec so that if for example you want all mpeg2video to be
# converted to H.264, you can uncomment the line below. When this option is defined, transcoding
# will happen regardless of other options whenever the video format is in this example mpeg2video.
#v.conf.t.codec_map.mpeg2video=libx264

I wouldn't worry about the lineup files. Those are mostly only useful for ClearQAM configurations.

[BobbyDing]

Thanks so much!!!

Bobby

[willieb]

Originally Posted by willieb

I will see if I can get this working. If I am reading him right I just need to replace the files on my flash boot drive and give it a go. Should be able to try tomorrow night.
...
I'll post back any progress.

Well, I tried but couldn't get it working. If I lspci -v after booting, I can see a Non-VGA Unclassified Device that is the Ceton. It purports to be using the driver (can't remember exactly what the file name of the driver was, but it is "ctn" something). But SageTV doesn't see the tuner. In the meantime I ordered the Prime and got it working in no time, so I might be retiring my Ceton.

[EnterNoEscape]

Originally Posted by willieb

Well, I tried but couldn't get it working. If I lspci -v after booting, I can see a Non-VGA Unclassified Device that is the Ceton. It purports to be using the driver (can't remember exactly what the file name of the driver was, but it is "ctn" something). But SageTV doesn't see the tuner. In the meantime I ordered the Prime and got it working in no time, so I might be retiring my Ceton.

That's how the InfiniTV 4 devices show up in Linux. The InfiniTV 6 devices show up as Multimedia video controller. What do you see when you run: ip addr? Do you see anything like ctn0? If you don't you might not have the udev rules installed.

To fix that, you should just need to copy 98-ctn91xx.rules into /etc/udev/rules.d/ and then run: depmod -a

[realcap]

Having "No Signal" issues with a number of Charter Spectrum channels (789, 752) over the past 12 hours. Using HD Primes and all channels have strong signals and can be viewed using HDHomerun softeware. I stopped the Sagetv and OpenDCT services, did a HDPrime scan using HDhomerun Setup. Restarted HDPrime, router, computer and Opendct and Sagetv services and having same issues. Attached are the logs. Please review and let me know if you have any advice as to how to resolve. Thank you, Mike

[EnterNoEscape]

Originally Posted by realcap

Having "No Signal" issues with a number of Charter Spectrum channels (789, 752) over the past 12 hours. Using HD Primes and all channels have strong signals and can be viewed using HDHomerun softeware. I stopped the Sagetv and OpenDCT services, did a HDPrime scan using HDhomerun Setup. Restarted HDPrime, router, computer and Opendct and Sagetv services and having same issues. Attached are the logs. Please review and let me know if you have any advice as to how to resolve. Thank you, Mike
Attachment 16198
Attachment 16196
Attachment 16197

You're using the media server consumer. OpenDCT is having no problems getting the stream, so this is a problem on the SageTV side of things. We will need to see your SageTV logs.

[hb4]

I worked through getting the SageTV and OpenDCT dockers up on Unraid, and am accessing the UI via Placeshifter. Selected sources and created lineups for my HDHR and HDHR Prime. When I go to watch or record a channel, I get a 'No Signal' message. I do see the tuner light come on for both tuners.

I did not go through the 'load console' step. If that's potentially the issue, how do I back out of OpenDCT and run the ./console-only script? Do I need to remove and re-install the OpenDCT docker and start fresh to run that script?

What logs can I provide to help figure out the issue, and are there any other important steps in the first post or GitHub configuration info that I need to do first?

I am able to access, view, and record from the above HDHR and Prime from my V9 upgrade on W7, and have assumed that I can share these tuners between the Windows and UnRaid SageTV installations.

[realcap]

Originally Posted by EnterNoEscape

You're using the media server consumer. OpenDCT is having no problems getting the stream, so this is a problem on the SageTV side of things. We will need to see your SageTV logs.

Thanks for taking a look.

[EnterNoEscape]

I kind of expected this. We have a situation where the built in remuxer can't deal with the stream being provided by a cable company. I would just change the consumer back to FFmpeg and enable upload ID.

I would change opendct.consumer.MediaServerConsumerImpl to opendct.consumer.FFmpegTransSageTVConsumerImpl and consumer.ffmpeg.upload_id_enabled=false to consumer.ffmpeg.upload_id_enabled=true.

I was working on this at one point, but I'm just getting tired of tracking down all of the fun things the cable companies are shooting down the pipes and just because it plays on their boxes doesn't mean they are doing it correctly. I can all but be certain that the PAT and/or PMT packets are messed up.

[Fuzzy]

next time i get back into dev mode, I will likely change the opendct docker defaults to keep the dynamic set to ffmpeg, and simply force on the upload_id_enabled switch instead.

I still would like to try to get rid of the 'download on start' mechanic of the docker, and make the docker image build a part of the opendct build, so they simply get released together, and opendct version would be upgraded simply by upgrading the image from the unraid ui, as it is done with most dockers, instead of it being done on its own when the docker is restarted, sometimes without user intention to apply an upgrade. Honestly, I'd like this to be the case for sagetv as well, but the problem there is the issue with the actual app folder needing to persist. opendct doesn't really have that complication, since app and config are properly separated.

[realcap]

Originally Posted by EnterNoEscape

I kind of expected this. We have a situation where the built in remuxer can't deal with the stream being provided by a cable company. I would just change the consumer back to FFmpeg and enable upload ID.

I would change opendct.consumer.MediaServerConsumerImpl to opendct.consumer.FFmpegTransSageTVConsumerImpl and consumer.ffmpeg.upload_id_enabled=false to consumer.ffmpeg.upload_id_enabled=true.

I was working on this at one point, but I'm just getting tired of tracking down all of the fun things the cable companies are shooting down the pipes and just because it plays on their boxes doesn't mean they are doing it correctly. I can all but be certain that the PAT and/or PMT packets are messed up.

Thank you for your expert troubleshooting and all that you do to keep SageTV updated and working.

[hb4]

Did a little reading, and based on this thread I copied my opendct.properties file in its entirety from my operating W7 installation to my test UnRAID installation.

Still have the No Signal notice, but I do see a light on one of the Prime tuners.

Here are the properties and log files.

Any suggestions?

Thanks!

[EnterNoEscape]

Originally Posted by hb4

Did a little reading, and based on this thread I copied my opendct.properties file in its entirety from my operating W7 installation to my test UnRAID installation.

Still have the No Signal notice, but I do see a light on one of the Prime tuners.

Here are the properties and log files.

Any suggestions?

Thanks!

Change consumer.ffmpeg.upload_id_enabled=false to consumer.ffmpeg.upload_id_enabled=true.

[hb4]

Originally Posted by EnterNoEscape

Change consumer.ffmpeg.upload_id_enabled=false to consumer.ffmpeg.upload_id_enabled=true.

Did that; still no signal. This time, the tuner light did not come on. Changed back to check, and with the setting 'false' the tuner light comes on.

Is it necessary to manually overwrite the opendct.properties file with a W7 version to make the openDCT docker work at this point? Is that what substitutes for running the W7 version in console mode first, is there another method, or is that step no longer needed?

BTW, the out-of-the-box open.properties file has that configuration line set to false.

[EnterNoEscape]

Originally Posted by hb4

Did that; still no signal. This time, the tuner light did not come on. Changed back to check, and with the setting 'false' the tuner light comes on.

Is it necessary to manually overwrite the opendct.properties file with a W7 version to make the openDCT docker work at this point? Is that what substitutes for running the W7 version in console mode first, is there another method, or is that step no longer needed?

BTW, the out-of-the-box open.properties file has that configuration line set to false.

The console step is there mostly to populate opendct.properties. It's not really required. Upload ID is set to false by default because it was causing stability issues on v7 Windows installs.

[hb4]

OK; I'll set it back to 'true'.

So.... any idea why I still get 'no signal'?

[Fuzzy]

Originally Posted by hb4

OK; I'll set it back to 'true'.

So.... any idea why I still get 'no signal'?

What firmware is in the tuners? I ask, because it looks like they are not really speaking well to openDCT (not reporting how many tuners they have, for instance).

[hb4]

Originally Posted by Fuzzy

What firmware is in the tuners? I ask, because it looks like they are not really speaking well to openDCT (not reporting how many tuners they have, for instance).

Version 20150604 for the HDHR and 20150826 for the Prime. I see there are later releases;

Updated software (which updated firmware for both the HDHR and Prime) to 20161117.

And....... SUCCESS!

This was the solution to the No Signal issue when I upgraded to OpenDCT from SageDCT (on W7) last November as well, by installing what was then the beta version of the Prime firmware. No problems when I upgraded to V9 on W7 last week, however.

Thanks for the help and all you do for improving and modernizing SageTV.

Now on to figuring out how to tell my HD200 to look at the UnRaid server.