Project

General

Profile

Bug #2989

DVR priority regression - "high" is preferred over "important"

Added by Ivan Kalvachev almost 7 years ago. Updated almost 7 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
Category:
PVR / DVR
Target version:
-
Start date:
2015-07-02
Due date:
% Done:

100%

Estimated time:
Found in version:
4.1-334~g5c3b74d
Affected Versions:

Description

Even now the priority list in the webUI reads:

Not set
Important
High
Normal
Low
Unimportant

I have 2 programs on different transponders that collide in time. I have them set as "high" and "important" respectively. (I don't want the other "normal" stuff to fight with these two, e.g. reruns at night.)

After upgrading from version "3.9.2679~g995aaf8" to "4.1-295~g8ad9f08" the program set as "high" started to interrupt the one set as "important". Since "important" is higher in the list, it is supposed to have higher priority.

I upgraded to current "4.1-334~g5c3b74d" and I was able to reproduce the bad behavior by adding 2 new program entries in "DVR AutoRec".

Associated revisions

Revision b6d4dda4 (diff)
Added by Jaroslav Kysela almost 7 years ago

DVR: Fix Important priority handling, fixes #2989

Revision ab7c0b79 (diff)
Added by Jaroslav Kysela about 5 years ago

DVR: Fix Important priority handling, fixes #2989

History

#1

Updated by Jaroslav Kysela almost 7 years ago

  • Status changed from New to Fixed
  • % Done changed from 0 to 100

Also available in: Atom PDF