OpenDCT: An open source digital cable tuner.

[Zogg]

Quick question, I'm seeing 5 entries in Sage.properties for each of my HDHR tuners, times 4. At least one is for a previous network encoding system that now has a new name, along with DCT entries.

Should I do as the example post and delete all these extra entries, or do they not really make a difference other than cluttering up the properties file?

[EnterNoEscape]

Originally Posted by tmiranda

Question. If I change the lineup that is being used by my HDHR Prime, do I need to do anything special to tell Open DCT?

No. It shouldn't matter at all from OpenDCT's perspective.

Originally Posted by Zogg

Quick question, I'm seeing 5 entries in Sage.properties for each of my HDHR tuners, times 4. At least one is for a previous network encoding system that now has a new name, along with DCT entries.

Should I do as the example post and delete all these extra entries, or do they not really make a difference other than cluttering up the properties file?

They are just clutter. I would delete them if you don't like seeing them, but otherwise, it shouldn't cause any issues.

[GKenny]

Can you describe to me what the parameters are for the #qam_infinitv Configuration file? I'm trying to create this file by hand because I do not have access to a cable card. I can tune channels by hand using the Ceton InfiniTV web interface.

#qam_infinitv Configuration File
#Wed Jan 11 10:26:26 EST 2017
channel.0504=504,,true,Unknown,,QAM,507000000,1004,,86,UNKNOWN,false
channel.0505=505,,true,Unknown,,QAM,513000000,1006,,88,UNKNOWN,false
channel.0507=507,,true,Unknown,,QAM,519000000,1009,,88,UNKNOWN,false
lineup.address=dct_infinitv
lineup.friendly_name=Ceton InfiniTV PCIe (00-80-27-6c)
lineup.offline_update_interval=604800000
lineup.source=COPY
lineup.update_interval=28800000
sagetv.available_channels_ref=504,505,507
sagetv.unavailable_channels_ref=

I'm looking mostly for the channel.0504=504 parameter details.

Thanks,
Glen


.... Nevermind. I forgot the source was online. It was easy enough to figure out.

[Telecore]

I previously put this on the Hauppauge QuadHD but it turns out I have a problem watching a live recording on HD300s from my Ceton PCIe6 using OpenDCT. "Hang Detected" in log file. This has happened multiple times today trying to watch football games. The recording is watchable from the windows client but not from two different HD300's - they get the spinning circle of death. Log file is attached. Any ideas here?

[EnterNoEscape]

Originally Posted by Telecore

I previously put this on the Hauppauge QuadHD but it turns out I have a problem watching a live recording on HD300s from my Ceton PCIe6 using OpenDCT. "Hang Detected" in log file. This has happened multiple times today trying to watch football games. The recording is watchable from the windows client but not from two different HD300's - they get the spinning circle of death. Log file is attached. Any ideas here?

I'm not sure if this is directly related to any of your tuners. Based on what I see in the logs, this could just as likely be related to a plugin. I'm not very savvy with debugging UI problems, but the last line before the hangs started on the rendering thread was this:

Fri 11/24 19:25:07.774 [ActiveRender-0023a5000864@ede989] VideoFrame got registration of a cc UI component: sage.ZCCLabel[loc=java.awt.Point[x=24,y=13] size=java.awt.Dimension[width=196,height=110]]

I don't know if it's the smoking gun, but maybe someone expand on this.

[Telecore]

I think you're right it is probably not the tuners - one other piece of information - when this happens, the live recording that can't be viewed is split into more than one file - so perhaps that is also a clue.

On an unrelated note, how does SageTV completely bypass four ATSC encoders of merit=5 and use 1 of 6 CC encoders at merit=3 when there are no other recordings scheduled for the entire day and no one else watching TV???

[EnterNoEscape]

Originally Posted by Telecore

I think you're right it is probably not the tuners - one other piece of information - when this happens, the live recording that can't be viewed is split into more than one file - so perhaps that is also a clue.

On an unrelated note, how does SageTV completely bypass four ATSC encoders of merit=5 and use 1 of 6 CC encoders at merit=3 when there are no other recordings scheduled for the entire day and no one else watching TV???

My guess would be SageTV doesn't think they are responding, but I don't see anything in the logs to support that.

[willieb]

I frequently see this same behavior. I have 2 ATSC tuners with merit 70 that I use for my local channels. I have an HDHR Prime with 3 tuners and merit 60 for my fios channels (including the fios versions of the locals). I prefer the ATSC feeds because they are compressed less, but I have found that it is completely random as to which tuner Sage chooses to use for recordings on my local channels. Like you, I see it choose the Prime at least a majority of the time when there are zero scheduled recordings and no one is watching anything else. I suspect there is something wrong with the merit logic, but don't know what to do about it.

[muzicman0]

I have just installed on a fresh install af Kubuntu 17.10, and have everything working as long as I don't reboot. I have to manually start the OpenDCT service to get it working. I tried adding it via update-rc.d, however, it still doesn't work on reboot. Any ideas?

[EnterNoEscape]

Originally Posted by muzicman0

I have just installed on a fresh install af Kubuntu 17.10, and have everything working as long as I don't reboot. I have to manually start the OpenDCT service to get it working. I tried adding it via update-rc.d, however, it still doesn't work on reboot. Any ideas?

I haven't done any testing on non-LTS versions of Ubuntu which as I understand, Kubuntu is based on (the difference being the GUI is KDE). My guess would be something isn't right with how it's working with systemd if that exists in that distro. Unfortunately I don't really have any suggestions on how to troubleshoot this other than things you have likely already done like enabling the service so that it should start again on reboot.

[egeller]

If I could not figure out how to get the Linux service task to start automatically, I'd try creating a CRON job, that runs on reboot, to automate the task's startup.

[muzicman0]

I know enough on Linux to be dangerous...used to use Kubuntu full time, but that was a few years ago. So...I don't know much about 'run levels'. it is currently set to run on run level 2, but I am not sure if that is correct.

Also, the priority is the same as SageTV...is that correct, or should I raise it so that it starts later (IE: After SageTV loads)?

[egeller]

Originally Posted by muzicman0

I know enough on Linux to be dangerous...used to use Kubuntu full time, but that was a few years ago. So...I don't know much about 'run levels'. it is currently set to run on run level 2, but I am not sure if that is correct.

Also, the priority is the same as SageTV...is that correct, or should I raise it so that it starts later (IE: After SageTV loads)?

Not sure about run levels. I was in an Application support group, when I worked on Linux apps, so we worked to keep Linux simple. We never paid attention to runlevels. We DID have the habit of loading Webmin on our Linux machines, in an attempt to make administration easier and browser based.

Regarding startup order, reverse your direction. I'd think you'll want OpenDCT to start before SageTV, so Sage can find the tuners.

hmm... maybe it's possible to customize / edit the sage startup script and have it start Opendct just before it starts up Sage. (thinking out loud)

[EnterNoEscape]

Originally Posted by muzicman0

I know enough on Linux to be dangerous...used to use Kubuntu full time, but that was a few years ago. So...I don't know much about 'run levels'. it is currently set to run on run level 2, but I am not sure if that is correct.

Also, the priority is the same as SageTV...is that correct, or should I raise it so that it starts later (IE: After SageTV loads)?

OpenDCT should be started before SageTV if possible. Run levels correlate with what's expected to be available in the OS and if we're powering up, rebooting or shutting down. However all of the distros have their own ideas about what they should be. I would have been of the impression you're using systemd, but if we're talking about runlevels, you must be using init.d.

The more important line is # Required-Start: $local_fs $remote_fs $network which indicates what the service needs before it can start. It could start in runlevel 2, 3, 4 or 5 if as soon as one of them has everything it needs. Anyway, try this:

sudo ln -fs /opt/opendct/service /etc/init.d/opendct
sudo chmod 755 /etc/init.d/opendct

[sic0048]

I'm trying to get a camera to show on SageTV. I've gotten the OpenDTC to recognize the stream, but I'm not getting a good stream to view in Sage. I'm hoping someone can look at the files and see what I am doing wrong.

The stream works on rtsp://admin:123456@192.168.1.5:7070 and this is confirmed in VLC.

Here are my files to review.

Thanks!

[EnterNoEscape]

Originally Posted by sic0048

I'm trying to get a camera to show on SageTV. I've gotten the OpenDTC to recognize the stream, but I'm not getting a good stream to view in Sage. I'm hoping someone can look at the files and see what I am doing wrong.

The stream works on rtsp://admin:123456@192.168.1.5:7070 and this is confirmed in VLC.

Here are my files to review.

Thanks!

Can you open the TS file created from FFmpeg with any other video playback software?

Edit: I ask because I suspect that mpeg4 doesn't work well in a TS container (at least for SageTV).

[sic0048]

Originally Posted by EnterNoEscape

Can you open the TS file created from FFmpeg with any other video playback software?

Edit: I ask because I suspect that mpeg4 doesn't work well in a TS container (at least for SageTV).

I can open it in VLC, but not windows media player.

On another side note, my camera does have audio that is part of the rtsp stream. It would be great to include the original audio instead of mixing in a blank audio track.

EDIT - so removing the "-f lavfi" part of the command line makes it viewable in Sage. There is about a 15 second delay, but that is understandable I guess. I would still like to get sound from the camera to play in Sage, so I will continue to play with some settings. If you have any suggestions, I would appreciate it!

Here is my current properties line: sagetv.device.-1712929228.streaming_executable=C\:\\Program Files\\ffmpeg-20171204-71421f3-win64-static\\bin\\ffmpeg.exe -i rtsp\://admin\:123456@192.168.1.5\:7070 -shortest -c\:av copy -f mpegts pipe\:1

[EnterNoEscape]

Originally Posted by sic0048

I can open it in VLC, but not windows media player.

On another side note, my camera does have audio that is part of the rtsp stream. It would be great to include the original audio instead of mixing in a blank audio track.

EDIT - so removing the "-f lavfi" part of the command line makes it viewable in Sage. There is about a 15 second delay, but that is understandable I guess. I would still like to get sound from the camera to play in Sage, so I will continue to play with some settings. If you have any suggestions, I would appreciate it!

Here is my current properties line: sagetv.device.-1712929228.streaming_executable=C\:\\Program Files\\ffmpeg-20171204-71421f3-win64-static\\bin\\ffmpeg.exe -i rtsp\://admin\:123456@192.168.1.5\:7070 -shortest -c\:av copy -f mpegts pipe\:1

pcm_u8 (native) is supported in a TS as far as I know. I'm not sure I can provide any additional comment on how to get SageTV to like the stream more.

[reggie14]

Originally Posted by EnterNoEscape

Thanks. Unfortunately, other than confirming that a full GC happened before it determined that a buffer couldn't be allocated, I don't know why it was unable to find enough space in RAM to do so. The actual heap RAM usage is extremely lean in your logs.

I did enable G1GC for this build which did cause some issues for SageTV a few months back. Based on what those looked like, this kind of looks like the same idea. Stop OpenDCT, backup, then overwrite "C:\Program Files (x86)\OpenDCT Authors\OpenDCT\jsw\conf\wrapper.conf" with the wrapper.conf I have attached. Start OpenDCT again and let me know if things get better.

I got busy and didn't try this until recently. Life happened, and I suddenly had a lot of guests watching lots of TV on lots of extenders. This led to a large number of errors.

So, I finally applied this configuration change a few days ago. I haven't had any more problems.

[EnterNoEscape]

Originally Posted by reggie14

I got busy and didn't try this until recently. Life happened, and I suddenly had a lot of guests watching lots of TV on lots of extenders. This led to a large number of errors.

So, I finally applied this configuration change a few days ago. I haven't had any more problems.

That's good to know. I'll be releasing a new version of SageTV changing back to the default GC because I'm sure you're not the only person who has seen this.