Opened 15 years ago
Closed 15 years ago
#507 closed defect (fixed)
"Full scan of existing transports"
Reported by: | anonymous | Owned by: | danielk |
---|---|---|---|
Priority: | minor | Milestone: | 0.19 |
Component: | dvb | Version: | head |
Severity: | medium | Keywords: | |
Cc: | Ticket locked: | no |
Description
I can scan fine when doing doing an existing transport scan and moving though each transport manually, but the Full Scan of Existing Transports times out on each transport.
The signal timeout value seems to make no difference and it doesn't seem relevant if it can scan a single transport fine but not sequentially.
The card is a Leadtek LR6650 and I'm in the UK.
I will do what I can to help debug the problem.
Attachments (3)
Change History (9)
comment:1 Changed 15 years ago by
Status: | new → assigned |
---|
Changed 15 years ago by
Attachment: | ex_transport.log added |
---|
Changed 15 years ago by
Attachment: | full_scan_ex_transports.log added |
---|
comment:3 Changed 15 years ago by
Milestone: | → 0.19 |
---|
Can you try the attached patch?
It looks like the "Leadtek LR6650" drops the FE_LOCK once you begin reading data from it. I won't use this patch on SVN, but if it works, I'll add a checkbox to ignore the FE_LOCK status during the scan.
comment:6 Changed 15 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
(In [7654]) Closes #507, by giving option of a SLOW scan.
Basically the problem is that that the DVB drivers used by the "Leadtek LR6650" don't report an FE_LOCK in a reasonable time, even after they are delivering data to MythTV they are telling MythTV that they don't see any data out there... This is a serious driver bug. But my experience with DVB suggests that serious driver bugs are commonplace so I've added the option of allowing the channel scan to ignore the FE_LOCK status timeout altogether. This, of course, makes the scan take much longer, but it's probably preferable to not getting any channels from the scan.
Users that require this option may experience problems in MythTV as well, but MythTV tuning is a little more forgiving of broken drivers than the MythTV channel scan so YMMV.
Can you attach the log from "mythtv-setup -v channel,siparser" for one Existing Transport, and another log from a Full Scan of Existing Transports?