Opened 6 years ago

Closed 6 years ago

#12125 closed Bug Report - General (Feature request without patch)

Scheduler not using tuners optimally to record all possible shows

Reported by: cube_00@… Owned by: gigem
Priority: minor Milestone: unknown
Component: MythTV - Scheduling Version: 0.27-fixes
Severity: medium Keywords:
Cc: Ticket locked: no


In the first scheduled recordings list (screenshot 1) there is one conflict, however if I suggest a tuner for Elementary to be 5 all programs can be recorded (screenshot 2). Could the scheduler be improved to choose this optimal arrangement?

Background I have a duel tuner card mapped to 8 virtual tuners. Tuners 1-4 can all record different channels in the same multiplex. Tuners 5-8 can do the same for a different multiplex. In the screenshots channel 10 is on one multiplex and channels 71 and 72 are on another. So the optimal arrangement is to use one group of four tuners to record shows from 10 and the second group to record shows from 71 and 72.

Attachments (2)

Screenshot 1.png (10.7 KB) - added by cube_00@… 6 years ago.
Screenshot 1
Screenshot 2.png (9.5 KB) - added by cube_00@… 6 years ago.
Screenshot 2

Download all attachments as: .zip

Change History (4)

Changed 6 years ago by cube_00@…

Attachment: Screenshot 1.png added

Screenshot 1

Changed 6 years ago by cube_00@…

Attachment: Screenshot 2.png added

Screenshot 2

comment:1 Changed 6 years ago by Raymond Wagner

It looks like your first tuner went unused, and the recording is being placed on the first available tuner in the list, rather than dropping down to the one already active on that multiplex.

comment:2 Changed 6 years ago by gigem

Resolution: Feature request without patch
Status: newclosed

Please note the closing of this ticket is no reflection on the merit of the suggested change. It is MythTV policy to not use the ticket system to track feature requests that do not have accompanying patches.

The MythTV scheduler currently uses a "first fit wins" approach and then tries to make small adjustments when needed. This means it can sometimes paint itself into a corner as it did in your example. It intentionally works this way to keep things simple. Scheduling for multiple tuners, multiple priorities and users with varying expectations is not easy.

That being said, adding some type of "tuner affinity" to more efficiently use tuners and hopefully reduce the corner painting cases is something I'd eventually like to do. I just don't know when that will happen and I don't want to clutter up track with something that might not get done for a long time.

Note: See TracTickets for help on using tickets.