| Summary: | Mythtv 0.20: Unable to change channels | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Peter Declercq <peter> |
| Component: | Current packages | Assignee: | Doug Goldstein (RETIRED) <cardoe> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | 2006.1 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Peter Declercq
2006-09-09 14:18:42 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 Please test with 0.20 and reopen if still an issue. Thanks, Peter 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 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. 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 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. 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. |