Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#268 closed defect (worksforme)

EPG "Forgets" Current Channel For Some Channels

Reported by: anonymous Owned by: danielk
Priority: trivial Milestone: 0.20
Component: mythtv Version: head
Severity: low Keywords:
Cc: Ticket locked: no

Description

When watching live TV, normal behavior is that when I enter the program guide, it will open with the channel I am watching selected. But, when I'm on some channels, the current channel isn't selected and the guide starts on channel 1. It's always the same channels that have this problem, but I can't figure out what they have in common. I went into mythtv-setup and deleted channel info and reconfigured it, but no change.

Browse mode always shows the correct channel, just program guide has this problem. I only have one tuner connected to the s-video input of a PVR-250.

What further info can I provide to help track this down?

Attachments (3)

mythtv_trac_268.sql.bz2 (9.5 KB) - added by anonymous 14 years ago.
database dump of requested tables
mythbackend.log.bz2 (1.8 KB) - added by anonymous 14 years ago.
backend log as requested with -v record,channel
mythfronttend_playback_log.txt.bz2 (2.9 KB) - added by anonymous 14 years ago.
frontend log as requested with -v playback

Download all attachments as: .zip

Change History (14)

comment:1 Changed 14 years ago by anonymous

I also see this problem. One thing I will add is that the OSD report the channel as a decimal like .234 instead of 33. Entering browse mode and then leaving seems to initialize things correctly and the program guide works fine afterward.

comment:2 Changed 14 years ago by anonymous

I believe this to be similar... If I leave LiveTV on for extended period of time (over night) or just watching same channel has done it too, The tuner seems to forget where it is and cannot turn the channel. The "Info" box about the channel and show you are on is blank and the guide shows that you are on a different channel than you are. Selecting a channel just returns to the same channel and exiting to the main menu and going back in will restore services to normal.

comment:3 Changed 14 years ago by danielk

Owner: changed from Isaac Richards to danielk

I'll look at this.

comment:4 Changed 14 years ago by danielk

Resolution: fixed
Status: newclosed

(In [7643]) Fixes #268.

The EPG wasn't really forgetting the current channel. The problem was that it was looking up channum which is not always unique.

This change makes quidegrid look for the chanid if it is passed one and fallback on channum if it is not.

Then in LiveTV mode this change adds code to look up the chanid of the current channel. But in progfind.cpp and programs/mythfrontend/main.cpp we still use the channum. This is fine because in these cases we aren't trying to start on a particular channel on a particular tuner, but rather just start in the same place whenever the grid is brought up.

This also does a little bit of refactoring in that it passes chanid around as an unsigned integer rather than a string.

comment:5 Changed 14 years ago by anonymous

I'm still experiencing this problem in SVN 7671.

comment:6 Changed 14 years ago by anonymous

Resolution: fixed
Status: closedreopened

comment:7 Changed 14 years ago by danielk

Milestone: 0.20
Resolution: worksforme
Status: reopenedclosed

anon, can you give an exacting description of what you did to before experiencing the problem and the exact nature of the problem. (i.e. every key pressed, what capture card is being used, etc.)

I'll also need the output of mythfrontend "-v playback" and mythbackend "-v record, channel", for the run described.

Plus provide a DB dump of the channel, videosource, cardinput and capturecard tables. I'll need to match that up to the description and logs.

I'm marking this as worksforme, but you can reopen it when you have the needed info

comment:8 Changed 14 years ago by anonymous

Resolution: worksforme
Status: closedreopened

Here's the description. I'm attaching the logs and db dump requested and reopening the ticket.

I have a combined frontend / backend with a single PVR-250 capture card connected to my external cable box. It receives signal via the s-video input.

  1. Start live tv and change channel to 211. (This channel is one of many that always have the problem). In the logs supplied it started on 211, so I didn't change channels.
  2. Press m to bring up menu
  3. Press right arrow to bring up guide.
  4. Some channels go to correct channel on guide others do not.

The following workaround addresses the problem (not shown in logs). After 1-4 above have failed

  1. Start live tv or change channel.
  2. Press i to bring up info/browse OSD
  3. Press esc to exit OSD
  4. Press m to bring up menu
  5. Press right arrow to bring up guide
  6. Guide always opens to correct channel.

Changed 14 years ago by anonymous

Attachment: mythtv_trac_268.sql.bz2 added

database dump of requested tables

Changed 14 years ago by anonymous

Attachment: mythbackend.log.bz2 added

backend log as requested with -v record,channel

Changed 14 years ago by anonymous

frontend log as requested with -v playback

comment:9 Changed 14 years ago by danielk

(In [7784]) References #268. Simplify chanid query for EPG.

comment:10 Changed 14 years ago by danielk

Priority: minortrivial
Resolution: worksforme
Severity: mediumlow
Status: reopenedclosed
  1. Some channels go to correct channel on guide others do not.

So did it bring up the wrong guide data this time?

Anyway, I looked at the sql tables and the logs.

I can't see any reason why this should fail, but I did change the EPG to use the same query as the INFO command. So if the info command works this should too.

I'm marking this as 'worksforme' again. If you get this problem again with the new chanid query, reopen the ticket. If the problem persist I'm going to have to create a debugging patch which gives us some more info on what is going on here, that will have to wait until after the 0.19 release though.

comment:11 Changed 14 years ago by anonymous

This seems to have cleared it up or, at worst, made it much less probable.

Note: See TracTickets for help on using tickets.