Project

General

Profile

Bug #5293

Multiple one mux instances (Common Interface Service limit)

Added by john beton about 6 years ago. Updated about 6 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Descrambling
Target version:
-
Start date:
2018-10-26
Due date:
% Done:

0%

Estimated time:
Found in version:
4.3-1497~g860fb78
Affected Versions:

Description

Hi all,

I have 2 tuners with a CI module. The CI module can only descramble 3 channels at the same time (of the same mux). I have set the service limit in "Configuration - CAs - Parameters - Common Interface Settings - Service Limit" to the value of 3.

When I start 3 recordings on the same mux, everything works fine but when I start the 4th recording, tvheadend doesn't start recording on the secondary tuner.

2018-10-26 11:53:52.210 [WARNING] subscription: 0065: service instance is bad, reason: No descrambler
2018-10-26 11:53:52.210 [ INFO] subscription: 0065: "DVR: Homes Under the Hammer" subscribing on channel "BBC 1", weight: 500, adapter: "Silicon Labs Si2168 #0 : DVB-C #0", network: "TELENET", mux: "314MHz", provider: "Telenet", service: "BBC 1", profile="pass", username=""
2018-10-26 11:53:54.210 [WARNING] subscription: 0065: service instance is bad, reason: No descrambler
2018-10-26 11:53:56.210 [ NOTICE] subscription: 0065: No input source available for subscription "DVR: Homes Under the Hammer" to channel "BBC 1"
2018-10-26 11:53:56.210 [ ERROR] dvr: Recording unable to start: "Homes Under the Hammer": No descrambler

History

#1

Updated by saen acro about 6 years ago

If set value to "2" is it work correct?

#2

Updated by john beton about 6 years ago

saen acro wrote:

If set value to "2" is it work correct?

Hi,

Strange thing: If I set it to 2, I can only record 2 services at the same time (on same mux).

So, why doesnt it work if I set it to 3? :(

#3

Updated by john beton about 6 years ago

I'm sorry, I should clarify more.

If I set the limit to 2, I can ofcourse record 2 channels at the same time. The 3rd fails.

But tvheadend doesn't switch to the secondary tuner because it thinks all channels of 1 mux should be recorded on a single tuner.

I think the problem is similar to my other remarks in #4933

https://tvheadend.org/issues/4933#change-27363

#4

Updated by saen acro about 6 years ago

Hardware CAM can decode only from one tuner in same time
Only PRO devices can and have software for more.

#5

Updated by john beton about 6 years ago

Yes, I know. But I have 2 TT-4650 tuners with 2 CI modules. One placed in each.

Currently there doesn't seem to be a solution for this problem. The "service limit" for a cam works. If you tune for a 4th recording from another much, it will work.

#6

Updated by Jaroslav Kysela about 6 years ago

It's a bit dup of #4933 . The only way to handle this is to create two networks and assign tuners separately to those networks and map services from both networks to one channel.

EDIT: Until #4933 is resolved (absolutely no ETA).

#7

Updated by john beton about 6 years ago

Dear Jaroslav, I understand it.

But am I missing the point here? Why is there such a setting to limit the services on a CAM if there is no fallback plan to what is supposed to happen when this limit is exceeded?
From a DVR view or from a HTSP or RTSP view, the problem remains the same.

Or is this setting here for another reason?

#8

Updated by Jaroslav Kysela about 6 years ago

john beton wrote:

Dear Jaroslav, I understand it.

But am I missing the point here? Why is there such a setting to limit the services on a CAM if there is no fallback plan to what is supposed to happen when this limit is exceeded?

You can let tvh to select quickly another service - see my previous comment for the workaround for DVBAPI sources (two networks). Also there might be different scenarios (like DVB-S primary, DVB-T or IPTV fallback etc.).

#9

Updated by Jaroslav Kysela about 6 years ago

  • Subject changed from Common Interface Service limit doesn't work to Multiple mux instances (Common Interface Service limit)
#10

Updated by Jaroslav Kysela about 6 years ago

  • Subject changed from Multiple mux instances (Common Interface Service limit) to Multiple one mux instances (Common Interface Service limit)

Also available in: Atom PDF