Project

General

Profile

Bug #4743

Change in commit a05f1b2 (tsdemux: always pass scrambled data through descrambler) causes issues when no external descrambler is present

Added by Robert Cameron almost 7 years ago. Updated almost 7 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
Category:
Descrambling
Target version:
-
Start date:
2017-11-26
Due date:
% Done:

0%

Estimated time:
Found in version:
4.3 (commit a05f1b2)
Affected Versions:

Description

I am using a HDHomeRun Prime with Tvheadend, and all CableCARD channels are marked as encrypted. However, because the CableCARD handles the decryption, the stream is passed to Tvheadend without the need for a separate descrambler. Previously, this caused no problems. However, after this commit, Tvheadend will no longer play channels that have encrypted services (which are all of my services) because it cannot find a descrambler.

History

#1

Updated by Joe User almost 7 years ago

Do you have "Remove scrambled bits:" selected for the device?

#2

Updated by Jaroslav Kysela almost 7 years ago

Yes, if TS packets in the source stream are not marked as scrambled, the commit should work. Please, show '--trace descrambler' . https://tvheadend.org/projects/tvheadend/wiki/Traces

#3

Updated by Robert Cameron almost 7 years ago

Joe User wrote:

Do you have "Remove scrambled bits:" selected for the device?

No, that option is not set on my tuners; should it be?

I've presently downgraded to a previous build until I had time to troubleshoot and run a bunch of test builds on another machine.

The services are marked as "Encrypted" in the service info dialog. I'm in the process of setting up a clean install/test build using one of my tuners not presently associated with my current install to get some logs and traces. I'll post more once I have some more information.

(I am aware that my situation is quite different from most others. I am using a CableCARD tuner as if it were a real DVB/ATSC tuner, and the muxes are the cable/vchannel numbers rather than the frequencies actually used. Tuning this way through the modified tvhdhomerun_frontend using vchannels instead of frequencies allows the device to handle the decryption which would not happen otherwise. This situation might be unique because of the way in which I am manipulating the system.)

#4

Updated by Robert Cameron almost 7 years ago

Joe User wrote:

Do you have "Remove scrambled bits:" selected for the device?

Well, now I feel a bit of a boob. I just ran a test on a clean install using the latest master (295288821). Playing a mux directly was fine, but attempting to play a service gave me a "Couldn't start streaming ..., No descrambler". However, once I ticked the "Remove scrambled bits" in the adapter tab, it seemed to stream fine.

I've since made the change to my main TVH server and it is running fine now. Thanks for the head's up, and the easy fix. (Although why this was never a problem until this change ... who knows.)

#5

Updated by Robert Cameron almost 7 years ago

Argh .. I guess I can't close an issue I started. So, please feel free to mark this issue closed.

#6

Updated by Mark Clarkstone almost 7 years ago

  • Status changed from New to Invalid

Robert Cameron wrote:

Argh .. I guess I can't close an issue I started. So, please feel free to mark this issue closed.

As requested.

Also available in: Atom PDF