Opened 15 years ago

Closed 15 years ago

#1108 closed enhancement (invalid)

Frontend crashes when switching to a channel with 5C protection on Firewire

Reported by: tim_trampedach@… Owned by: Isaac Richards
Priority: minor Milestone: 0.20
Component: mythtv Version: head
Severity: medium Keywords: firewire frontend crash
Cc: Ticket locked: no


When I watch live TV and switch from a 5C=0 channel (copy protection off such as regular OTA and basic cable channels) to one that has copy protection such as premium cable or Comcast's INHD channels, the picture freezes on the last frame of the previous non-copy protected channel. The CPU usage of mythfrontend goes to the max it can and never recovers. Assumably, the firewire stream at that point is suddenly null and the frontend isn't handling this.

My setup: SVN 8657 (1/19/06) Firewire with DCT-6200 and Comcast cable

I apologize in advance if I may have interpreted the priority and severity wrong, though at this stage of the release I thought my choices are correct

Change History (6)

comment:1 Changed 15 years ago by anonymous

Priority: majorminor
Severity: highmedium

comment:2 Changed 15 years ago by danielk

Resolution: invalid
Status: newclosed

Feature request...

The firewire recorder needs a signal monitor to fix this.

The workaround is to not put 5C channels in your lineup.

comment:3 Changed 15 years ago by tim_trampedach@…

Resolution: invalid
Status: closedreopened

Daniel: I'm surprised that you completely closed this issue. While I can understand that major code fixes aren't of the order at this stage of the release, I feel that anything that causes the frontend to either crash or lock up is indeed an issue. I would even argue that it's not a feature request, because this isn't "user error". Channels can come in 5C encrypted some of the time and some of the time they're not encrypted. MythTV needs to gracefully handle not locking up when the datastream hits zero. Behavior like this in MythTV makes it tough for the system to pass the "girlfriend or wife test".

Please understand that I'm not trying to start an argument here. I work as a Program Manager for a staff of over 30 people building telco software and anything that locks up the application, irrespective of user error or not, is an issue. I do have systems programming background, so if someone could point me to the direction of where to look into fixing this, I'd be happy to do.

I'm reopening this as a defect for 0.19 therefore.

comment:4 Changed 15 years ago by bjm

Resolution: invalid
Status: reopenedclosed

Feature request with no patch attached. This is a database of information about code changes and not a chat room about our feelings. I'll talk about my feelings elsewhere.

comment:5 Changed 15 years ago by tim_trampedach@…

Milestone: 0.190.20
Resolution: invalid
Status: closedreopened
Type: defectenhancement

Wow, tough crowd. Sorry, I'm just trying to help. Transitioning to .20 as an enhancement...

Please also try to take the high road. Again, I'm just trying to help. Thanks.

comment:6 Changed 15 years ago by Isaac Richards

Resolution: invalid
Status: reopenedclosed
Note: See TracTickets for help on using tickets.