DVR priority regression - "high" is preferred over "important"
Even now the priority list in the webUI reads:
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".
Updated by Jaroslav Kysela almost 7 years ago
- Status changed from New to Fixed
- % Done changed from 0 to 100
Applied in changeset tvheadend|b6d4dda4af5874654d9c0d7035b8046ce9897d06.