[mythtv] Check start byte of next table in packet commit impact on tuning reliability?

Klaas de Waal klaas.de.waal at gmail.com
Thu Oct 22 16:04:59 UTC 2020

Hi Piotr,

On Thu, 22 Oct 2020 at 12:03, Piotr Oniszczuk <piotr.oniszczuk at gmail.com>

> Klaas,
> Is it possible that
> https://github.com/MythTV/mythtv/commit/58dfe835843a39065bce73af9dc1f586b48d9de3
> may cause decreased sat tuning reliability on encrypted sat channels?
> With this commit i see correlation of issue of approx few % of tunings
> failing at waiting on TLAMc.
> Reverting this patch removes TLAMc failure case from running issues.
The result of the commit should only be that a few more tables are actually
processed instead of being discarded because of checksum failures. I do not
have a clear view on how this can influence decryption, also given that
basic tuning has already been done otherwise there are no transport stream
packets at all.
Can you be specific on which satellite and which channels do give problems?
Is it for specific channels or is it random?
I can receive Astra-1/2/3 plus Hotbird 13.0E; if your problem is not random
but specific for channels on one of these satellites then I could do some
testing on it.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-dev/attachments/20201022/117c0d61/attachment.htm>

More information about the mythtv-dev mailing list