According to EN 50221 an application should be able to query whether a given CAM can decrypt an actual broadcast by sending it a CA_PMT with a ca_pmt_cmd_id of "query" instead of "ok_descrambling".
However, if I change the line
capmt[length++] = CPCI_OK_DESCRAMBLING;
in VDR/ci.c to
capmt[length++] = CPCI_QUERY;
I never get a ca_pmt_reply as specified in EN 50221, section 8.4.3.5.
Does anybody have an idea why that is so? Is there a bug in VDR's CAM handling? Could it be that the CAMs I have just don't behave correctly?
The reason why I'd like this to work is because if somebody has more than one device with CAMs that supports a certain encryption method, but only one of them has an actual smart card in it and can thus actually decrypt, it is important that VDR selects the right device. However, it can't do so if the CAM doesn't react on a query.
Klaus
On su, 2005-08-21 at 13:47 +0200, Klaus Schmidinger wrote:
The reason why I'd like this to work is because if somebody has more than one device with CAMs that supports a certain encryption method, but only one of them has an actual smart card in it and can thus actually decrypt, it is important that VDR selects the right device. However, it can't do so if the CAM doesn't react on a query.
One Q&D way to solve this (very real problem, at least for me) would be to separate CA and DVB device information in channels.conf. Currently, nailing specific channels to a specific device causes VDR to be unaware the limitations of receiving an encypted channels which it does take into account when CA field specifies the system being used (Conax for example).
Of course, one can have more than one CAM in a particular CI of a particular DVB device..
Heikki Manninen wrote:
On su, 2005-08-21 at 13:47 +0200, Klaus Schmidinger wrote:
The reason why I'd like this to work is because if somebody has more than one device with CAMs that supports a certain encryption method, but only one of them has an actual smart card in it and can thus actually decrypt, it is important that VDR selects the right device. However, it can't do so if the CAM doesn't react on a query.
One Q&D way to solve this (very real problem, at least for me) would be to separate CA and DVB device information in channels.conf. Currently, nailing specific channels to a specific device causes VDR to be unaware the limitations of receiving an encypted channels which it does take into account when CA field specifies the system being used (Conax for example).
Of course, one can have more than one CAM in a particular CI of a particular DVB device..
Having two CAMs with the same decryption method in the same CI is no problem. The first CAM that can actually decrypt the signal will do so. The problem is only when there are several different devices with different CIs and CAMs that support the same decryption method.
Klaus
On ma, 2005-08-29 at 19:11 +0200, Klaus Schmidinger wrote:
One Q&D way to solve this (very real problem, at least for me) would be to separate CA and DVB device information in channels.conf. Currently, nailing specific channels to a specific device causes VDR to be unaware the limitations of receiving an encypted channels which it does take into account when CA field specifies the system being used (Conax for example).
Of course, one can have more than one CAM in a particular CI of a particular DVB device..
Having two CAMs with the same decryption method in the same CI is no problem. The first CAM that can actually decrypt the signal will do so. The problem is only when there are several different devices with different CIs and CAMs that support the same decryption method.
Exactly what I meant.
Having two same CAMs is a problem when you have different set of channels subscribed to them and you have them in different devices (to be able to record simultaneously).
-
Heikki Manninen -
Klaus Schmidinger