Re: [mythtv-users] if (x!=rerun) {record}
On 10/20/05, Todd Houle [EMAIL PROTECTED] wrote: I need a little help running a reruns rule.I'd like the followingrule for recording, but I can't seem to find where/how to enter it.I'd like to record a show and keep at most 4 episodes of it.Ifthere's anymore, don't record them until I watch the old (this part I'm doing).However, if it's not a rerun, then record it anyway -either delete and old one, or just record it in addition.Thanks- you guys are brilliant! ToddRight now there's no way to do that, other than manually doing it. It would be great if you could give new episodes a higher priority and then tell the scheduler to keep at most maybe 5 episodes and record new and expire old if the new episodes priority is greater than or equal to the older episode's. Lower priority should always be deleted before higher in this case, so that way a non-rerun will be recorded over a rerun instead of an older non-rerun. It would work well for the shows like the simpsons, that way you could always have different repeats to watch but they would never delete the new episodes when you don't get to them for a while.-- I probably still have a few (well, now a whole bunch) gmail invites.Drop me a line (off list) if you'd like an account. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] if (x!=rerun) {record}
On Fri, Oct 21, 2005 at 09:30:33AM -0400, Fred Squires wrote: It would be great if you could give new episodes a higher priority and then tell the scheduler to keep at most maybe 5 episodes and record new and expire old if the new episodes priority is greater than or equal to the older episode's. Lower priority should always be deleted before higher in this case, so that way a non-rerun will be recorded over a rerun instead of an older non-rerun. It would work well for the shows like the simpsons, that way you could always have different repeats to watch but they would never delete the new episodes when you don't get to them for a while. Agreed. Or maybe the simplest way to handle this would be to add support for having two separate recording schedules for the same show (one with high priority and no autoexpire for new episodes and another with lower priority and autoexpire for reruns)? That would count the number of episodes separately for new and rerun, but I personally don't see that as an issue. Something else that could help here would be additional autoexpire methods. AFAICT, oldest first is the only option present (in 0.18.1). Adding lowest priority first and reruns first (ideally with by date/by priority suboptions under the rerun setting) would definitely make it more flexible for handling Simpsons, etc. What I would *really* like to see is something comparable to Tivo's suggestions feature (it autorecords shows similar to things you've said you like when there's extra space available and those recordings are the first to go when more space is needed), but I would expect that to be a fairly major addition, while multiple schedules per show or more autoexpire options would be much simpler to add. -- The freedoms that we enjoy presently are the most important victories of the White Hats over the past several millennia, and it is vitally important that we don't give them up now, only because we are frightened. - Eolake Stobblehouse (http://stobblehouse.com/text/battle.html) ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] if (x!=rerun) {record}
Fred Squires wrote: On 10/20/05, *Todd Houle* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I need a little help running a reruns rule. I'd like the following rule for recording, but I can't seem to find where/how to enter it. I'd like to record a show and keep at most 4 episodes of it. If there's anymore, don't record them until I watch the old (this part I'm doing). However, if it's not a rerun, then record it anyway - either delete and old one, or just record it in addition. Right now there's no way to do that, other than manually doing it. It would be great if you could give new episodes a higher priority In SVN, you could create a custom record rule for new episodes only and assign a priority for that. Then, create a rule for old episodes. Or, assuming you do this after creating the custom record rule for new episodes, just create a rule for record all. If you use the same rule type (i.e. this channel or all channels) for both, the all episodes rule must be created after the new episodes rule so it can match first. If you make a more specific rule for the new episodes (i.e. use this channel for new episodes and any channel for all episodes), it doesn't matter what order they're created in. Then, assign priorities to the rules as desired. I hope I got this all right, but I'm sure Bruce Markey will chime in with corrections to any misinformation here... He's the man with the answers for recording rules--especially custom recording. ;) and then tell the scheduler to keep at most maybe 5 episodes and record new and expire old if the new episodes priority is greater than or equal to the older episode's. Lower priority should always be deleted before higher in this case, so that way a non-rerun will be recorded over a rerun instead of an older non-rerun. OK. I don't know much about how auto-expire works, but I think you can specify an auto-expire priority (or, perhaps it uses recording rule priority to determine auto-expire priority, or maybe both approaches are options...). However, I know if you have two rules--a new episodes rule and an anything else rule--you can specify that new episodes should not be auto-expired and reruns can be. You can also specify a max episodes for the all episodes rule. It would work well for the shows like the simpsons, that way you could always have different repeats to watch but they would never delete the new episodes when you don't get to them for a while. Feel free to report back your experiences. ;) Mike ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] if (x!=rerun) {record}
Dave Sherohman wrote: On Fri, Oct 21, 2005 at 09:30:33AM -0400, Fred Squires wrote: It would be great if you could give new episodes a higher priority and then tell the scheduler to keep at most maybe 5 episodes and record new and expire old if the new episodes priority is greater than or equal to the older episode's. Lower priority should always be deleted before higher in this case, so that way a non-rerun will be recorded over a rerun instead of an older non-rerun. It would work well for the shows like the simpsons, that way you could always have different repeats to watch but they would never delete the new episodes when you don't get to them for a while. Agreed. Or maybe the simplest way to handle this would be to add support for having two separate recording schedules for the same show (one with high priority and no autoexpire for new episodes and another with lower priority and autoexpire for reruns)? That would count the number of episodes separately for new and rerun, but I personally don't see that as an issue. Pretty sure that has always been possible. See my other post in this thread. Something else that could help here would be additional autoexpire methods. AFAICT, oldest first is the only option present (in 0.18.1). Adding lowest priority first and reruns first (ideally with by date/by priority suboptions under the rerun setting) would definitely make it more flexible for handling Simpsons, etc. I think SVN has lowest priority first. The reruns first--actually keying off original airdate--would be a nice addition. What I would *really* like to see is something comparable to Tivo's suggestions feature (it autorecords shows similar to things you've said you like when there's extra space available and those recordings are the first to go when more space is needed), but I would expect that to be a fairly major addition, while multiple schedules per show or more autoexpire options would be much simpler to add. TVWish and other plugins give you this. Mike ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] if (x!=rerun) {record}
Michael T. Dean wrote: Fred Squires wrote: On 10/20/05, *Todd Houle* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I need a little help running a reruns rule. I'd like the following rule for recording, but I can't seem to find where/how to enter it. I'd like to record a show and keep at most 4 episodes of it. If there's anymore, don't record them until I watch the old (this part I'm doing). However, if it's not a rerun, then record it anyway - either delete and old one, or just record it in addition. Right now there's no way to do that, other than manually doing it. It would be great if you could give new episodes a higher priority In SVN, you could create a custom record rule for new episodes only and assign a priority for that. OK. Now I'm thinking that it will work in 0.18, too. The docs describe custom record rules, so it seems to be in the main version: http://mythtv.org/docs/mythtv-HOWTO-11.html#ss11.8 Mike ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] if (x!=rerun) {record}
On Fri, Oct 21, 2005 at 11:05:31AM -0400, Michael T. Dean wrote: Dave Sherohman wrote: What I would *really* like to see is something comparable to Tivo's suggestions feature (it autorecords shows similar to things you've said you like when there's extra space available and those recordings are the first to go when more space is needed), but I would expect that to be a fairly major addition, while multiple schedules per show or more autoexpire options would be much simpler to add. TVWish and other plugins give you this. Really? Thanks! I've been told by two other mythtv users that nothing like that existed, so I didn't bother checking for myself. Guess that gets put on my list for after I finish getting MythWeb/ Video/Gallery/Weather up and running... -- The freedoms that we enjoy presently are the most important victories of the White Hats over the past several millennia, and it is vitally important that we don't give them up now, only because we are frightened. - Eolake Stobblehouse (http://stobblehouse.com/text/battle.html) ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] if (x!=rerun) {record}
Michael T. Dean wrote: Fred Squires wrote: On 10/20/05, *Todd Houle* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I need a little help running a reruns rule. I'd like the following rule for recording, but I can't seem to find where/how to enter it. I'd like to record a show and keep at most 4 episodes of it. If there's anymore, don't record them until I watch the old (this part I'm doing). However, if it's not a rerun, then record it anyway - either delete and old one, or just record it in addition. Right now there's no way to do that, other than manually doing it. It would be great if you could give new episodes a higher priority In SVN, you could create a custom record rule for new episodes only and assign a priority for that. Then, create a rule for old episodes. Or, assuming you do this after creating the custom record rule for new episodes, just create a rule for record all. If you use the same rule type (i.e. this channel or all channels) for both, the all episodes rule must be created after the new episodes rule so it can match first. If you make a more specific rule for the new episodes (i.e. use this channel for new episodes and any channel for all episodes), it doesn't matter what order they're created in. Outstanding. Your ability to absorb information then present in an easy to digest manner is always impressive. I really hope you spend some time at some point going over the HOWTO to clarify things you commonly respond to so that you can reply with links to the docs. But that's another matter. Then, assign priorities to the rules as desired. I hope I got this all right, but I'm sure Bruce Markey will chime in with corrections to any misinformation here... He's the man with the answers for recording rules--especially custom recording. ;) You rang? I started a reply to this last night but got mired in the details of making sure the power search for new rules had precedence and the issue of total episodes for two rules. Todd, What Mike said. Here are the gory details. I'll guess we're talking about The Simpsons. If not, it's a typical example for the situation described. There are new episodes Sunday evening on FOX and years of reruns on the same or different channels throughout the week. You want a limited number of reruns but still record new episodes. You may even want a different priority or profile for the new ones. This can be done with two different rule. One that applies to new episodes only and one that will match any other showing. As Mike mentioned, the rule for new episodes has to match only the new episodes and take precedence over the other rule. I'll use the output of mythbackend -v schedule to illustrate. Because of the World Series, there isn't a new Simpsons this week so I faked one in my test DB program table. First, if I set a simple All rule. It matches three episodes: --- print list start --- Title - SubtitleChan ChID Day Start End S C I T N Pri The Simpsons - Diatribe of a Mad H 14 1014 21 18:30-19:00 1 1 1 A 1 0 The Simpsons - Margical History To 14 1014 21 19:30-20:00 1 1 1 A 1 0 The Simpsons - Brand New Bart5 1005 23 20:00-20:30 1 1 1 A 1 0 The Type is A and they are all scheduled to record on card 1. If I set Record new episodes only, it will mark the reruns as repeat. The Simpsons - Diatribe of a Mad H 14 1014 21 18:30-19:00 1 0 0 A r 0 The Simpsons - Margical History To 14 1014 21 19:30-20:00 1 0 0 A r 0 The Simpsons - Brand New Bart5 1005 23 20:00-20:30 1 1 1 A 1 0 This rule still controls all three episodes but we want a different rule for the reruns so we need a rule that will only match the new episodes. To do this, I remove this rule, go to Custom Record and create this rule: program.title = 'The Simpsons' AND program.previouslyshown = 0 from Match an exact title and New episodes only. See: http://www.mythtv.org/docs/mythtv-HOWTO-11.html#ss11.8 . I click Record to set a new rule with no episode limit but I bump up the priority a bit to make sure I get these new episodes. The Simpsons - Brand New Bart5 1005 23 20:00-20:30 1 1 1 A 1 2 This rule only matched the new episode and set the priority to 2. Next I find one of the old episodes. There is no existing rule so I can create a new one. I choose All but this time I lower the priority by 1, set Keep at most 4 episodes and Don't record if this would exceed the max episodes then Save. The Simpsons - Diatribe of a Mad H 14 1014 21 18:30-19:00 1 1 1 A 1 -1 The Simpsons - Margical History To 14 1014 21 19:30-20:00 1 1 1 A 1 -1 The Simpsons - Brand New Bart5 1005 23 20:00-20:30 1 1 1 A 1 2 The reruns have -1 priority and only a max of 4 recorded by this rule will be kept. New episodes will get +2 and an unlimited number recordings. You could have 4 reruns and 2 new for a total of 6 but presumably you'll watch the new ones as
Re: [mythtv-users] if (x!=rerun) {record}
Quoting Bruce Markey [EMAIL PROTECTED]: Note: the rule for new episodes has to take precedence. The more specific type wins (Single beats Channel beats All) but in this case they are both All. Therefore the rule for new episodes needs to be created first to win the tie breaker for older rule. See: http://www.mythtv.org/docs/mythtv-HOWTO-11.html#ss11.7 the last item under Scheduling decisions. More for my own knowledge and understanding, but doesn't the assigned priority (-1 for syndication and +2 for new episodes) ensure that these rules will never tie? Therefore, it doesn't really matter which order you add them, even though doing it this way certainly won't hurt. - Derek ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] if (x!=rerun) {record}
Derek Battams wrote: Quoting Bruce Markey [EMAIL PROTECTED]: Note: the rule for new episodes has to take precedence. The more specific type wins (Single beats Channel beats All) but in this case they are both All. Therefore the rule for new episodes needs to be created first to win the tie breaker for older rule. See: http://www.mythtv.org/docs/mythtv-HOWTO-11.html#ss11.7 the last item under Scheduling decisions. More for my own knowledge and understanding, but doesn't the assigned priority (-1 for syndication and +2 for new episodes) ensure that these rules will never tie? Therefore, it doesn't really matter which order you add them, even though doing it this way certainly won't hurt. There are two different issues. There is the normal question of which of two different titles has higher priority and thus which title gets recorded. However, in this case we have two rules that match the same showing of the same title. Here the question is which rule controls that showing. For instance, say you have an All rule for a favorite show with +6. Due to circumstance you want it to record on card 2 tonight and can do so by lowering the priority to -2 so you add an override. If the controlling rule was chosen by priority, the override would lose. An override applies to a single showing of a program that is also controlled by a recurring rule. The override must always win precedence in order to work. The same would be true if you set a kWeekslotRecord rule for one showing where you knew the time was always off by a few minutes and a kChannelRecord for all other showings. The weekslot rule needs to control that specific day and time over the more general rule regardless of any of the recording parameters. In the code, this decision is made by RecTypePriority(). -- bjm ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] if (x!=rerun) {record}
On Fri, Oct 21, 2005 at 12:30:13PM -0700, Bruce Markey wrote: Derek Battams wrote: Quoting Bruce Markey [EMAIL PROTECTED]: Note: the rule for new episodes has to take precedence. The more specific type wins (Single beats Channel beats All) but in this case they are both All. Therefore the rule for new episodes needs to be created first to win the tie breaker for older rule. See: http://www.mythtv.org/docs/mythtv-HOWTO-11.html#ss11.7 the last item under Scheduling decisions. More for my own knowledge and understanding, but doesn't the assigned priority (-1 for syndication and +2 for new episodes) ensure that these rules will never tie? Therefore, it doesn't really matter which order you add them, even though doing it this way certainly won't hurt. There are two different issues. There is the normal question of which of two different titles has higher priority and thus which title gets recorded. However, in this case we have two rules that match the same showing of the same title. Here the question is which rule controls that showing. For instance, say you have an All rule for a favorite show with +6. Due to circumstance you want it to record on card 2 tonight and can do so by lowering the priority to -2 so you add an override. If the controlling rule was chosen by priority, the override would lose. An override applies to a single showing of a program that is also controlled by a recurring rule. The override must always win precedence in order to work. The same would be true if you set a kWeekslotRecord rule for one showing where you knew the time was always off by a few minutes and a kChannelRecord for all other showings. The weekslot rule needs to control that specific day and time over the more general rule regardless of any of the recording parameters. In the code, this decision is made by RecTypePriority(). Great examples for why a more specific rule should always win over a less specific rule, but, when both are equally-specific, it would seem reasonable to go to priority as the next determinant rather than when the rule was created, if for no other reason than because, if you want to be sure which one takes precedence, priority is visible in the interface and 'date rule created' is not. (Not to mention that, if the wrong one has precedence, it's easier to change its priority than it is to delete and recreate rules so that they're in the right order. And it would be more consistent to boot. (Priority controls precedence of rules between different shows but not the same show? Huh?) Priority is better from a standpoint of clarity as well, since anyone can see that higher-priority beats lower-priority, but if you just say it's decided on date, then it's unclear whether newer or older should win - and some of us would expect newer to win, for much the same reason as we would expect overrides to win over the general rule.) *phew* OK, I think I'm out of reasons why I think it should go to priority after specificity instead of to rule age. So why was it set up to go by age instead? -- The freedoms that we enjoy presently are the most important victories of the White Hats over the past several millennia, and it is vitally important that we don't give them up now, only because we are frightened. - Eolake Stobblehouse (http://stobblehouse.com/text/battle.html) ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] if (x!=rerun) {record}
Dave Sherohman wrote: On Fri, Oct 21, 2005 at 11:05:31AM -0400, Michael T. Dean wrote: Dave Sherohman wrote: What I would *really* like to see is something comparable to Tivo's suggestions feature (it autorecords shows similar to things you've said you like when there's extra space available and those recordings are the first to go when more space is needed), but I would expect that to be a fairly major addition, while multiple schedules per show or more autoexpire options would be much simpler to add. TVWish and other plugins give you this. Really? Thanks! I've been told by two other mythtv users that nothing like that existed, so I didn't bother checking for myself. Guess that gets put on my list for after I finish getting MythWeb/ Video/Gallery/Weather up and running... http://mythtv.info/moin.cgi/MythTvModules See TVWish, MythSuggest, and MythRecommend. I can't recommend any of them because I don't use them (I have more than I can watch just recording the things I know I want to record). However, I know some are being used as I just saw someone (Wendy?) mention using TVWish. Mike ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
