Opened 13 years ago

Closed 12 years ago

#10967 closed Developer Task (Fixed)

Live TV Input Order Ignored During Channel Changes

Reported by: skd5aner <skd5aner@…> Owned by: Jim Stichnoth
Priority: minor Milestone: 0.27.1
Component: MythTV - General Version: 0.25-fixes
Severity: medium Keywords:
Cc: Ticket locked: no

Description

Prior to 0.25, a Live TV input order was added. This feature allows one to specify the order that a particular input will be used when launching Live TV. It works well, but unfortunately is only respected at the initial launch of Live TV. After Live TV has been launched, the tuners will leverage the standard order based on the order that the inputs were added and will ignore the live tv order setting after any channel changes. This is especially noticeable when leveraging different video sources across channels.

Simple Example:

3 tuners - A, B, C

Recording Order/Added Order: A-1 B-2 C-3

Live TV Order: A-3 B-2 C-1

After launching Live TV, tuner C will be chosen, however, if you are changing the channel, and it would need to select a different tuner perhaps because a channel uses a different video source, the tuner selected would no longer be selected based on the Live TV order.

Change History (7)

comment:1 by gigem, 13 years ago

Milestone: unknown0.27
Owner: set to gigem
Status: newassigned

comment:2 by sphery, 13 years ago

Type: Bug Report - GeneralDeveloper Task

Since this isn't a bug, but an unfinished feature...

comment:3 by paulh, 12 years ago

Milestone: 0.270.28

comment:4 by Jim Stichnoth, 12 years ago

Milestone: 0.280.27.1
Owner: changed from gigem to Jim Stichnoth
Status: assignedaccepted

comment:5 by Jim Stichnoth <jstichnoth@…>, 12 years ago

In cb602368945cf42f9072d8187991cff0b025684a/mythtv:

Error: Processor CommitTicketReference failed
GIT backend not available

comment:6 by Jim Stichnoth <jstichnoth@…>, 12 years ago

In d31e729827a1a50aae87eb816881547f58c1e68f/mythtv:

Error: Processor CommitTicketReference failed
GIT backend not available

comment:7 by Jim Stichnoth, 12 years ago

Resolution: Fixed
Status: acceptedclosed

I believe all situations should be fixed now in 0.27 and Master. Please reopen the ticket if you find any more.

Note: See TracTickets for help on using tickets.