Opened 14 years ago
Closed 13 years ago
#2350 closed defect (fixed)
Incorrect transport values
| Reported by: | Owned by: | Isaac Richards | |
|---|---|---|---|
| Priority: | minor | Milestone: | unknown |
| Component: | mythtv | Version: | 0.20 |
| Severity: | medium | Keywords: | |
| Cc: | Ticket locked: | no |
Description
11067 svn here. I have two sats.
Scanning channel is a success but there is no lock in mythfrontend. I suspected transport values in mythtv-setup and checked that they are different from my previous channel scan entries. For example: frequency=11642000, polarity=horizontal and symbol rate=27500000 was frequency=11642000, polarity=vertical and symbol rate=27500000 in transport editor. Correcting polarity to horizontal fixes the mythfrontend lock issue.
This occurs often.
Attachments (3)
Change History (8)
comment:2 Changed 14 years ago by
| Version: | → 0.20 |
|---|
Replying to Janne <janne-mythtv@grunau.be>:
please attach a dump of the NIT (dvbsnoop -n 1 0x10)
I suspect that it is an error in the transmitted NIT and not an error in MythTV.
ps: please don't change the priority from the default (see TicketHowTo)
Did goktug.yildirim@… ever attach his dvbscoop output? I'm having the same problem and I compiled a few days ago. Most of my channels will lock and sometimes a few wont that are even closer than the others. I'm attaching the dvbsnoop output from 2 pids just in case.
comment:3 Changed 14 years ago by
I'm also attaching the output from the "mythbackend -v channel" command trying to watch livetv on a channel that wont lock because it might provide some usefull information.
Changed 14 years ago by
| Attachment: | backendvchannel added |
|---|
Output from the "mythbackend -v channel" command getting No Lock.
comment:4 Changed 13 years ago by
Seems to be the same bug as the polinv patch fixes in ticket 2473. Apply this patch and then play with the LNB Reversed setting in the DiSEqC configuration.
This should fix your problem (at least it did for me!)
please attach a dump of the NIT (dvbsnoop -n 1 0x10)
I suspect that it is an error in the transmitted NIT and not an error in MythTV.
ps: please don't change the priority from the default (see TicketHowTo)