Opened 10 years ago

Closed 8 years ago

#8324 closed Bug Report - General (Unverified)

Channel Scan turns EIT usage back on while guide data comes from somewhere else already, resets visibility and other values.

Reported by: dekarl@… Owned by: Stuart Auchterlonie
Priority: minor Milestone: 0.25
Component: MythTV - Channel Scanner Version: 0.23rc1
Severity: medium Keywords:
Cc: Ticket locked: no

Description

I have a setup with mixed guide data from Xmltv and EIT.

After the initial channel scan all channels with EIT present get EIT usage enabled. I turned EIT usage off for the channels I get via Xmltv.

On the next channel scan EIT usage got automagically turned back on although there is guide data in the database. (which doesn't work and is unsupported, see #1770)

This happens still after configuring Grabber+EIT via mythtv-setup (should not matter, the channel scan should only care about data being there or not, might be inserted via mythfilldatabase from cron because its from nxtvepg or whatever)

Change History (8)

comment:1 Changed 10 years ago by robertm

Summary: Channel Scan turns EIT usage back on while guide data comes from somewhere else alreadyChannel Scan turns EIT usage back on while guide data comes from somewhere else already, resets visibility and other values.

comment:2 Changed 10 years ago by Janne Grunau

Milestone: unknown0.24
Owner: changed from danielk to Janne Grunau
Status: newaccepted

I'll commit a fix which preserves use_on_air_guide if xmltvid is set for 0.23. Further fixes require DB updates and are scheduled for 0.24.

comment:3 Changed 10 years ago by Janne Grunau

(In [24113]) channel scan: preserve use_on_air_guide value if xmltvid is empty

Refs #8324

comment:4 Changed 10 years ago by Janne Grunau

(In [24118]) backports [24113] from trunk

channel scan: preserve use_on_air_guide value if xmltvid is empty Refs #8324

comment:5 Changed 9 years ago by robertm

Milestone: 0.240.25

Bumping to .25 as I believe the remainder of the changes mentioned in IRC require substantial rework.

comment:6 Changed 8 years ago by beirdo

Milestone: 0.25unknown
Owner: Janne Grunau deleted
Status: acceptednew

comment:7 Changed 8 years ago by beirdo

Owner: set to Stuart Auchterlonie
Status: newassigned

comment:8 Changed 8 years ago by stuartm

Milestone: unknown0.25
Resolution: Unverified
Status: assignedclosed
Type: defectBug Report - General

I'm not sure how much of this is still the case in 0.25, I've lost track of when the channel scanner was last re-written and which fixes have already been made (I committed some of my own since the last re-factor). I'm closing this as 'unverified' and if there are still issues with the channel scanner resetting/overwriting existing settings then please open a new ticket.

Note: See TracTickets for help on using tickets.