Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 146995 - Mythtv 0.20: Unable to change channels
Summary: Mythtv 0.20: Unable to change channels
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal
Assignee: Doug Goldstein (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-09 14:18 UTC by Peter Declercq
Modified: 2006-11-06 23:58 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Declercq 2006-09-09 14:18:42 UTC
I've been trying to work out mythtv 0.19 and ivtv based cards.
Changing channels from live-tv doesn't work. It stays on the initial channel configured in input connections.
-----------------------------------------------------------------
Debugging mythbackend showed errors when trying to change channels:
2006-09-09 22:30:42.656  SELECT channel.chanid FROM channel, capturecard, cardinput WHERE channel.channum      = NULL           AND       channel.sourceid     = cardinput.sourceid AND       cardinput.inputname = 'Tuner 1'             AND       cardinput.cardid     = capturecard.cardid   AND       capturecard.cardid  = 1            AND       capturecard.hostname = 'tvserver'
2006-09-09 22:30:42.657 TVRec(1): Failed to find channel() on current input (Tuner 1) of card (1).
----------------------------------------------------------------

When you execute this query manually, the result is empty.
This seems logical as channel.channum isn't NULL, it is a number identifying the channel.
My test channels are:

chanid channum freqid sourceid callsign name
1000 1 E9 1 EEN EEN
1001 2 E5 1 Canvas canvas
1002 3 E12 1 VTM VTM

They were manually created from mythtv-setup.

When I schedule a manual recording and record the 3 different channels at the same time I get 3 different and correct recordings.
Comment 1 Doug Goldstein (RETIRED) gentoo-dev 2006-09-12 19:35:19 UTC
I would say this would have to go upstream. But I can tell you right away they won't help since 0.20 has been released. I would retest this with 0.20
Comment 2 Steve Dibb (RETIRED) gentoo-dev 2006-09-21 09:20:17 UTC
Please test with 0.20 and reopen if still an issue.  Thanks, Peter
Comment 3 Peter Declercq 2006-10-01 04:13:11 UTC
I emerged mythtv 0.20 and I have the same problem, Unable to change channels.
I now have a second setup using a only DVB-S card (technisat SkyStar2) and strangely I have the same problem.
Please tell me what I can provide you for troubleshooting analyse.
Regards,

Peter
Comment 4 Doug Goldstein (RETIRED) gentoo-dev 2006-10-05 19:28:07 UTC
There's another issue with 0.20 and DVB-S, mythtv-0.20_p11444 is targeting DVB-S fixes. Upstream has a pretty poor track record for this 0.20 release. Please test and report what version you have. You might have to dump your database and set it up again because it sounds like you've got it screwed up.
Comment 5 Peter Declercq 2006-10-16 03:44:48 UTC
Doug,

Can you please have a look at it. I'm not the only one having the channel change problem! http://forums.gentoo.org/viewtopic-t-489942.html

Peter
Comment 6 Peter Declercq 2006-10-16 03:51:11 UTC
F Y I,

I totally reinstalled the database when I installed v.20.
the other systems with a DVB card is working. I sometimes loose the signal lock after switching but I can live with that.

My DVB and analogue recording systems are totally separated, they don't use a common database.
Comment 7 Doug Goldstein (RETIRED) gentoo-dev 2006-11-06 23:58:51 UTC
Unfortunately your providing very minimal amount of information. You're not including any logs. Crank up the verbosity and provide some info. The most likely reason is that your channels are not properly configured. As far as the lock goes, your input is loosing signal. Signals can vary.

Your describing a situation which I won't be able to reproduce or will Steve (beandog) so you must provide us with the details. Also this issue does not appear to be anything reported to MythTV upstream so the issue is possibly fixed or a setup issue. Your best bet is going to be to try to find a user in a similar situation in #mythtv-users on Freenode. But right now my bet goes to mythtv-setup not being configured properly.