Opened 15 years ago

Closed 11 years ago

#2053 closed defect (fixed)

mythtv should inform user of lineup changes

Reported by: Isaac Richards Owned by: danielk
Priority: minor Milestone: unknown
Component: MythTV - Channel Scanner Version: head
Severity: medium Keywords:
Cc: Ticket locked: yes


At least, not without asking. New channels should not be silently disabled. It certainly shouldn't be doing a 'Select All' on the channels for an existing lineup.

Change History (11)

comment:1 Changed 15 years ago by Isaac Richards

(In [10531]) - Treat new videosources as analog, unless they have existing digital channels (as from a scan).

  • Don't do a 'select all' on channels from zap2it.

Initial setup for analog TV now actually works again.

Fixes #2052, Refs #2053.

comment:2 Changed 15 years ago by danielk

(In [10612]) Fixes #1848. Refs #2053. Allows DTV cards to be hooked up to DataDirect? without manual editing again.

There is still some work to do to prevent mythfilldatabase from mucking with the datadirect lineups when it doesn't need to so I'm keeping #2053 open.

The only time you really need to touch the datadirect lineups are:

  • right after a digital channel scan to get the xmltvid matches
  • when datadirect tries to add channels to a digital source (so you don't download listings data for an untunable channel).
  • when the user explicitly asks you do so to with --remove-new-channels and there are actually new channels to remove.
  • when you start up the frontend channel editor, and sometime after you leave it if xmltvid changes are made.

The code is still touching the lineups twice every time mythfilldatabase is run for digital sources, even when every channel has an xmltvid, and after any time you run the frontend channel editor (whether changes were made or not).

comment:3 Changed 15 years ago by danielk

(In [10710]) Refs #2053. Avoid unneeded change of zap2it lineups when --only-update-channels is used with analog inputs, and treat firewire as an unscanable input when --only-update-channels is used.

comment:4 Changed 15 years ago by danielk

Milestone: 0.200.21
Summary: mythfilldatabase shouldn't change the selected lineups at zap2it.mythtv should inform user of lineup changes

Moving the remainder of this to 0.21. The main part left is tracking of new and deleted channels so that the user is informed of lineup changes.

Note: after some testing I've determined that mythfilldatabase is not touching the lineups twice every time mythfilldatabase is run nightly on digital sources. It only does this when channels have been added, or when run with --only-update-channels.

comment:5 Changed 14 years ago by danielk

(In [13401]) Refs #2695. Refs #2053. Adds facility for saving newly scanned channels to the DB before processing them for DB insertion. This allows for debugging scans that don't resemble the developer's setup and also should allow for interactive processing in the frontend of automated channel scans in the future.

comment:6 Changed 14 years ago by danielk

Component: mythtvchannelscan
Milestone: 0.21unknown

The new channel table has been added in mythtv-multirec, this just needs a UI in that branch so I'm reclassifying this under the channelscan 'Component'.

comment:7 Changed 12 years ago by Dibblah

Status: newassigned

comment:8 Changed 12 years ago by barberio@…

I think attention should be drawn to

It seems that channel re-scanning on a line-up change for DVB-T simply doesn't work, and line-up changes simply don't get added to the database. I think this needs to be bumped from enhancement to bug, since it's a design flaw.

comment:9 Changed 12 years ago by Dibblah

Ticket locked: set

Trac is not a discussion forum.

comment:10 Changed 12 years ago by stuartm

Component: channelscanMythTV - Channel Scanner

comment:11 Changed 11 years ago by robertm

Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.