Ticket #5869 (closed Patch - Feature: Fixed)
Opened 5 years ago
Last modified 2 years ago
[PATCH] Don't record free schedules on channels with lowest priority
| Reported by: | Wolfgang <mythtv@…> | Owned by: | gigem |
|---|---|---|---|
| Priority: | minor | Milestone: | 0.25 |
| Component: | MythTV - Scheduling | Version: | head |
| Severity: | medium | Keywords: | |
| Cc: | Ticket locked: | no |
Description
With this patch you can instruct the scheduler that free schedules are not allowed on channels that have the lowest recordpriority -512. This is useful for example if you don't want that the free schedules match on radio channels or other special channels.
Attachments
Change History
Changed 5 years ago by Wolfgang <mythtv@…>
- Attachment free_scheduling_channel_blacklist_mythweb.diff added
patch for mythweb
comment:1 Changed 5 years ago by gigem
- Owner changed from ijr to gigem
- Status changed from new to accepted
This patch won't be applied as is. For starters, it causes gratuitous changes because a new field was inserted into the middle of a query. I am going to accept the report, however, because I have considered adding something similar myself. I need to think some more about excacly how best to do it though.
Changed 5 years ago by Wolfgang <mythtv@…>
- Attachment free_scheduling_channel_blacklist.2.diff added
fix wrong value
Changed 5 years ago by Wolfgang <mythtv@…>
- Attachment free_scheduling_channel_blacklist.3.diff added
- added recordtypes (All,FindWeekly?,FindDaily?,FindOne?) for blacklisting - put field at the end of the query
comment:4 Changed 2 years ago by beirdo
- Type changed from enhancement to Patch - Feature
- Summary changed from Enhancement - don't record free schedules on channels with lowest priority to [PATCH] Don't record free schedules on channels with lowest priority
comment:5 Changed 2 years ago by gigem
- Status changed from assigned to closed
- Resolution set to Fixed
- Milestone changed from unknown to 0.25
This is now fixed by the new recording rule filter support. To perform the original task, create a filter with SQL "channel.priority > -512" and set it to be automatically enabled for new rules. If/when you do want to record from a lower priority channel, disable the filter for the new rule.
