OpenDCT: An open source digital cable tuner.

[EnterNoEscape]

Originally Posted by sflamm

Exceptions occurring when stream started with source from OpenDCT connected to HDHR:

I don't know that those are directly related. You can the the MMC thread asking for the size of the file and OpenDCT saying it's still 0. The other thread is the media server disconnecting frequently which could be the player trying to open a file that doesn't have any data in it yet. The media server is used for a lot of things.

Edit: I noticed that you're recording to network shares. If you want OpenDCT to be able to use them, you'll need to change the account being used for the OpenDCT service to one that has access to those shares. This is likely the source of all of your problems.

[EnterNoEscape]

• Adjusted timeout when InfiniTV network adapters are discovered.
• Added handling for unexpected standby events.
• Removed tuning monitor handling when using the media server remuxer.

[tmiranda]

I started migrating my EPG to Schedules Direct and noticed something odd. I have a HDHR Prime and a Hauppauge 2250 as my video sources. The HDHR uses OpenDCT, the 2250 does not.

A large number of channels that are reported as "Copy Once" by the HDHR are tuneable by the 2250. How can that be? How can my old 2250 be successfully tuning channels that are set to be Copy Once?

[AlphaCrew]

Originally Posted by tmiranda

I started migrating my EPG to Schedules Direct and noticed something odd. I have a HDHR Prime and a Hauppauge 2250 as my video sources. The HDHR uses OpenDCT, the 2250 does not.

A large number of channels that are reported as "Copy Once" by the HDHR are tuneable by the 2250. How can that be? How can my old 2250 be successfully tuning channels that are set to be Copy Once?

You have channels in the Clear set as 0x02? That doesn't sound right.

[tmiranda]

Originally Posted by AlphaCrew

You have channels in the Clear set as 0x02? That doesn't sound right.

All I know is that I can watch and record the channels using the 2250 yet when I try to use OpenDCT they fail. In the video source setup menu OpenDCT displays the "Copy Once" message.

How can I figure out what's going on?

[EnterNoEscape]

Originally Posted by tmiranda

All I know is that I can watch and record the channels using the 2250 yet when I try to use OpenDCT they fail. In the video source setup menu OpenDCT displays the "Copy Once" message.

How can I figure out what's going on?

The logs should show why it thinks the channels are copy once.

Edit: You can also just disable the messages by changing error_videos_enabled=true to false. For some people despite the device reporting that the channel shouldn't stream, it streams anyway.

[Tiki]

Originally Posted by tmiranda

All I know is that I can watch and record the channels using the 2250 yet when I try to use OpenDCT they fail. In the video source setup menu OpenDCT displays the "Copy Once" message.

How can I figure out what's going on?

The 2250 is a clear qam device.
The cci copy flags are only for cable card devices. I doubt that a qam-only device is even aware of them.

It's like how hdcp protection is only used on hdmi connections but can't be enforced when using an analog connection like component video cables.

Are you using your HDHR with a cable card or in clear qam mode?

[tmiranda]

Originally Posted by Tiki

The 2250 is a clear qam device.
The cci copy flags are only for cable card devices. I doubt that a qam-only device is even aware of them.

It's like how hdcp protection is only used on hdmi connections but can't be enforced when using an analog connection like component video cables.

Are you using your HDHR with a cable card or in clear qam mode?

That makes sense. I am using the HDHR with a CableCard.

[AlphaCrew]

Originally Posted by tmiranda

All I know is that I can watch and record the channels using the 2250 yet when I try to use OpenDCT they fail. In the video source setup menu OpenDCT displays the "Copy Once" message.

How can I figure out what's going on?

I don't think the stream is actually 0x02, I think OpenDCT is 'miss-interpreting' the stream and labeling it as 0x02.

Your cable provider should not be setting the 0x02 bit for channels in the clear. If it is you should call them and have them set to 0x00.

[EnterNoEscape]

Originally Posted by AlphaCrew

I don't think the stream is actually 0x02, I think OpenDCT is 'miss-interpreting' the stream and labeling it as 0x02.

Your cable provider should not be setting the 0x02 bit for channels in the clear. If it is you should call them and have them set to 0x00.

OpenDCT is using the CCI value provided by the capture device itself. That's why I was interested in the logs. If it is providing a value that's being interpreted at Copy Once, but in reality isn't, then I need to fix it, otherwise the HDHomeRun might have a firmware problem or the cable provider is flagging channels that shouldn't be flagged while they are still broadcasting them unencrypted.

[tmiranda]

Originally Posted by EnterNoEscape

OpenDCT is using the CCI value provided by the capture device itself. That's why I was interested in the logs. If it is providing a value that's being interpreted at Copy Once, but in reality isn't, then I need to fix it, otherwise the HDHomeRun might have a firmware problem or the cable provider is flagging channels that shouldn't be flagged while they are still broadcasting them unencrypted.

Here is the log. At the very end I tried to tune to channel 207 Discovery HD. My 2250 plays this fine. OpenDCT gives me the "Copy Once" message (from the channel setup menu).

[EnterNoEscape]

Originally Posted by tmiranda

Here is the log. At the very end I tried to tune to channel 207 Discovery HD. My 2250 plays this fine. OpenDCT gives me the "Copy Once" message (from the channel setup menu).

So there's a few problems. The first one is this:

08:30:16.262 [SageTVRequestHandler-51529:DCT-HDHomeRun Prime Tuner 131276A4-2] ERROR HDHRNativeCaptureDevice - HDHomeRun is unable to tune into channel because the command did not work '207' => opendct.tuning.hdhomerun.GetSetException: ERROR: invalid virtual channel

That is exactly what it looks like. The CableCARD at this time has no mapping for channel 207. I then see an attempt to tune into channel 120 which actually is copy protected. The copy protection message is from tuning channel 120, not 207. SageTV uses the same file for channel previews which is likely why you're seeing it for both channels.

Edit: I probably could add another video that would playback when this kind of things happens.

[tmiranda]

Originally Posted by EnterNoEscape

So there's a few problems. The first one is this:

08:30:16.262 [SageTVRequestHandler-51529:DCT-HDHomeRun Prime Tuner 131276A4-2] ERROR HDHRNativeCaptureDevice - HDHomeRun is unable to tune into channel because the command did not work '207' => opendct.tuning.hdhomerun.GetSetException: ERROR: invalid virtual channel

That is exactly what it looks like. The CableCARD at this time has no mapping for channel 207. I then see an attempt to tune into channel 120 which actually is copy protected. The copy protection message is from tuning channel 120, not 207. SageTV uses the same file for channel previews which is likely why you're seeing it for both channels.

Edit: I probably could add another video that would playback when this kind of things happens.

What causes the CableCard to not have the channel mapping? I can watch channel 207 on my TV. Do I need to call the cable company and have them reprogram the CableCard?

[Fuzzy]

Originally Posted by tmiranda

What causes the CableCard to not have the channel mapping? I can watch channel 207 on my TV. Do I need to call the cable company and have them reprogram the CableCard?

It could be that the channel is not REALLY 207 on their cablecard managed lineup (which is what a cable box or cablecard tuner would see it at), but that is what is encoded in the stream (which the cablecard tuners would ignore), so that's what your clearqam is mapping it as. Id recommend doing a channel scan in the Prime's web page, and look for the channel there and see what number it is at. Then map the station in sage's lineup to that physical number.

[KarylFStein]

Originally Posted by EnterNoEscape

• Adjusted timeout when InfiniTV network adapters are discovered.
• Added handling for unexpected standby events.
• Removed tuning monitor handling when using the media server remuxer.

FYI, this seems to mitigate the issues I had installing before (kept complaining about the InfiniTV tuner not having an IP).

[EnterNoEscape]

Originally Posted by KarylFStein

FYI, this seems to mitigate the issues I had installing before (kept complaining about the InfiniTV tuner not having an IP).

Thanks for the feedback. That was one of things I was trying to address.

[ldl72]

Originally Posted by ldl72

Sorry, I should have mentioned that I am currently running Sage V9.

I am happy with 0.5.0, but I plan to install your latest version, and will report back my tuning experiences.

Thanks.

EnterNoEscape
I tried to install version 0.5.22 but could not get my HDHR Primes detected. Went back to 0.5.0 and everything worked again. Would love to try the new version. Logs attached. Thanks.

[AlphaCrew]

I am happy to report, after installing build .5.23 and setting pm.network.resume_timeout_ms=0, OpenDCT is no longer crashing AND is no longer missing any scheduled recording, this is with 3 days of recordings.

And as a bonus, I've been able to move my machine back to the hybrid sleep state with no ill effects..

[EnterNoEscape]

Originally Posted by ldl72

EnterNoEscape
I tried to install version 0.5.22 but could not get my HDHR Primes detected. Went back to 0.5.0 and everything worked again. Would love to try the new version. Logs attached. Thanks.

You were bit by the same InfiniTV problem as another user. 0.5.23 should be much friendlier.

[Griff]

I have been putting of my upgrade to Sage v9 and OpenDCT (from a stable installation of Sage v7 and SageDCT) because I have a Ceton InfiniTV 4, and have seen that others have had problems using OpenDCT with that tuner. The instructions for installing OpenDCT also note that InfiniTV 4 users must be on the very last beta firmware from Ceton to be able to use this version in the opening post. The Ceton diagnostic tool on my Sage machine states that an InfiniTV Firmware Update 1.2.2.6 [beta] is available, but returns an error that it is unable to download the update when I try to install it. Any suggestions on how I can get this update installed? I reached out to Ceton support, noting that I needed the beta update for my Sage installation, and they responded unhelpfully that they don't support Sage. Thanks in advance for any suggestions.
Tom