-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatic ECM pid fails after some time #16
Comments
I think I found when the problem happens: it is when original stream is lost for a while (dvblast restart or sat signal loss). Initially when running tsdecrypt we get: 2018-08-04 13:41:43 | NEW | Input PID 0x0010 appeared (NIT) But after stopping dvblast for few seconds then restarting it: So it seems after data is back, it doesn't read all ECM pids but only one, which in my case is one that can't be decrypted. |
OK, I think I found the issue. The code that detects the ecm pids (int __ts_get_ecm_info) calls find_CA_descriptor. But in order to work correctly, passed values ts->ecm_caid, ts->ecm_pid and ts->ecm_pids[X] should all be set to zero. On first run they are zero but after signal loss, on second run, they have the previously detected values and ecm pid detection fails (detects 0 pids). Following patch fixes that:
|
Using tsdecrypt on some VIACCESS channels that have different ECM pids for different viaccess providers, for example 0500:050F00, 0500:043800 and 0500:051E00. Newcamd line supports both 43800 and 50F00 but not 51E00. Everything works as expected, tsdecrypted switches between providers if there is an issue (timeout, cw not found etc) but after some time (can be days or hours) it seems it gets in a situation that only keeps retrying 051E00 which is not supported. I tried to debug it but the issue happens after some time so it is difficult. Any thoughts?
The text was updated successfully, but these errors were encountered: