Reply to thread

Message: <blockquote data-quote="mm1352000" data-source="post: 1115518" data-attributes="member: 82144">Yes, but in the past you only had a few of these messages for a second or two. That's very different to 25+ seconds. I would not say don't worry about it if you had/have 25+ seconds of message logging.Probably the CAM is already configured to decrypt the channel. Therefore there is minimal effort for the CAM to start decrypting the channel, and therefore no problem.I pick the CAM or CI driver. Surely it should not take so long for decryption to kick in?!?Also, I can't imagine how MP code could cause this. If the stream is encrypted then we simply have to throw away packets while we wait for the CAM to do its job.Probably only the people who created the CAM firmware would be able to explain it. Don't make the common mistake of assuming newer is better. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink    ;)" loading="lazy" data-shortname=";)" />Why?How many people have the same provider, CAM, CI, driver and firmware combination?Stay with the working firmware, and report the problem to the CAM and/or CI/tuner vendor.There is such an issue when channels use PES level encryption. TVE 3's TsWriter is not able to detect it. Usually it doesn't matter because the CAM only takes a second or so to start decrypting.Maybe it is the same or alike. Either way, it shouldn't take so long for your CAM to start decrypting.For the record, TVE 3.5's TsWriter can indeed detect PES level encryption. As usual, I don't intend to spend time implementing the same in TVE 3 where it would take longer and be more complex to implement. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink    ;)" loading="lazy" data-shortname=";)" /></blockquote>

Verification