Opened 9 years ago

Closed 3 years ago

#12185 closed Bug Report - General (Unverified)

CI/CAM: CAM thread started too late causing "TL__"

Reported by: ast@… Owned by:
Priority: minor Milestone: unknown
Component: MythTV - General Version: Unspecified
Severity: medium Keywords:
Cc: Ticket locked: no


This is for mythtv 0.27.1.

I do have a CAM that, after power up, doesn't pass the transport stream, either encrypted or unencrypted, until communication with the CAM commences. I didn't check further, which part of the communication (e.g. connection, session, time/date) is actually required. A quick look through the spec doesn't seem to disallow this CAM behaviour.

The problem is now, that MythTV starts the CAM thread which commences communication only in SetPMT(). This, however, is called only after TuningSignalCheck?() returns "good signal" which in turn requires the transport stream, thus causing a chicken and egg problem resulting in "TL".

Thus the CAM thread needs to be started before TuningSignalCheck?() starts to wait for the transport stream.

The attached patch is more or less a demo workaround that calls SetPMT with a NULL PMT before TuningSignalCheck?() is called. What is probably really required is just to start the CAM thread at a suitable point in the processing flow.

Attachments (1)

cam-thread-workaround.patch (424 bytes) - added by ast@… 9 years ago.
cam thread start workaround

Download all attachments as: .zip

Change History (4)

Changed 9 years ago by ast@…

Attachment: cam-thread-workaround.patch added

cam thread start workaround

comment:1 Changed 9 years ago by mythtv@…

I have the same behaviour, after reboot I get TL_ and I must remove and reinsert the CAM to get a decrypted picture - is there a simple way to verify if I have the same problem?

comment:2 Changed 9 years ago by ast@…

You can only try the attached patch. Be aware, however, that there are more problems (e.g. card validity updates don't work) which I don't have a solution for.

comment:3 Changed 3 years ago by Stuart Auchterlonie

Resolution: Unverified
Status: newclosed

Closing all old tickets in trac.

If your issue still persists, please open an issue in Github

and reference the existing trac ticket.

Note: See TracTickets for help on using tickets.