Bug #3085
Hardware CAM, adding "false" CA improves descrambling procedure
0%
Description
When using HW CAM, some of us found that adding a "false" CA (CAPMT) makes the descrambling procedure much faster and reliable. Without it, it can take 30-40 s to get the stream and sometimes nothings happends. Adding the CAPMT in the CA menu is not any big problem but it's maybe possible to solve in another way in the code. Now it generates a lot of "error" messages. See also:
https://tvheadend.org/issues/2794#change-14732
2015-09-16 21:36:15.000 capmt: Test: Cannot connect to /tmp/camd.socket (No such file or directory); Do you have OSCam running? 2015-09-16 21:36:15.000 capmt: Test: Automatic reconnection attempt in in 60 seconds 2015-09-16 21:37:14.000 capmt: Test: Cannot connect to /tmp/camd.socket (No such file or directory); Do you have OSCam running? 2015-09-16 21:37:14.000 capmt: Test: Automatic reconnection attempt in in 60 seconds 2015-09-16 21:38:13.000 capmt: Test: Cannot connect to /tmp/camd.socket (No such file or directory); Do you have OSCam running? 2015-09-16 21:38:13.000 capmt: Test: Automatic reconnection attempt in in 60 seconds 2015-09-16 21:39:12.000 capmt: Test: Cannot connect to /tmp/camd.socket (No such file or directory); Do you have OSCam running? 2015-09-16 21:39:12.000 capmt: Test: Automatic reconnection attempt in in 60 seconds
History
Updated by Gert Jansen almost 8 years ago
I have the same problem with a HW CAM as in https://tvheadend.org/issues/2794#change-14732
Adding a false CA (CAPMT) solves the problem but just like Bengt, I get a lot of errors.
The descrambling in itself works, it's just the messages that are annoying.
In my case, it's 2 messages every 3 seconds.
2016-12-13 16:32:51.190 capmt: CA client 1: Automatic reconnection attempt in in 3 seconds 2016-12-13 16:32:54.181 capmt: CA client 1: Cannot connect to /tmp/camd.socket (No such file or directory); Do you have OSCam running? 2016-12-13 16:32:54.181 capmt: CA client 1: Automatic reconnection attempt in in 3 seconds 2016-12-13 16:32:57.094 capmt: CA client 1: Cannot connect to /tmp/camd.socket (No such file or directory); Do you have OSCam running? 2016-12-13 16:32:57.094 capmt: CA client 1: Automatic reconnection attempt in in 3 seconds 2016-12-13 16:32:59.999 capmt: CA client 1: Cannot connect to /tmp/camd.socket (No such file or directory); Do you have OSCam running?
Is there a better solution available than adding the fake CA?
Or else, is there a way to get rid of the error messages? Can I disable the error output somewhere?
My syslog is not very happy this way
Updated by Gert Jansen almost 8 years ago
I forgot to add my TVH version: it is Tvheadend 4.1-2286~gb15b02c
(built from source)
Updated by Jaroslav Kysela almost 8 years ago
- Status changed from New to Rejected
This issue was really resolved in v4.1-2286-gb15b02c (so version you're running). Anyway, upgrade to latest and if you have any issues, provide logs for '--trace descrambler,en50221'. https://tvheadend.org/projects/tvheadend/wiki/Traces
Create another bug, pls.
Updated by Gert Jansen almost 8 years ago
My apologies, you are right, it does indeed work.
I never realized the fake CA client was not needed anymore, because I was aware of this particular bug report and since it was still on 'new' I never even tried to remove the fake CA.
Now I did, and indeed it works.