I want a show to not record if it has already been recorded within the last 56 days.

[Jrr6415sun]

I know i can make it so an episode won't record if it has been recorded within the last 28 days, but is there a way to increase this number? Like if I wanted to make it 56 days instead?

[OLdDog]

No, not without some serious hacking.

I do not believe this has ever been asked before, at least this is the first request for 56 days I ever remember seeing.

Other than keeping the first as save until I delete for the first 28 days then deleting it manually ther is no other way currently.

The ability to set "no repeat recorded" length for each SP or ARWL might be an easy enhancement at the programming level and I could see uses for both longer and shorter no repeat times.

But, from another point of view, the programming change could be fairly major as it would involve moving from a global constant to a local variable (attached to the program data) in every instance where the system uses the 28 day rule and changing the program database to hold the new variable and changing the SP/ARWL options screen to allow this to be set.

[supasta]

Just curious - Why 56 days?

[OLdDog]

My guess: 2 X 28 = 56

[JohnBrowning]

This is one of my most desired TiVo mods! I'd like the ability to set the "previously viewed" tracking timer to as long as I want.

[CraigHB]

Heck, I'd like to make it 6 months or even a year!

[rainwater]

Well, it also doesn't record if its still in the Now Playing list. So get a bigger drive! :)

[jsmeeker]

I do not believe this has ever been asked before, at least this is the first request for 56 days I ever remember seeing.



I don't follow the TiVo specifics as much as I used to, but I'm pretty sure I remember people asking for the 28 day rule be a user setable parameter. Just like some people want to change the length of the buffer.

Why longer? My guess is that the OP is recording some TV show that winds up with lots of repeats of the same episode within that period of time. It's probably not super common, but I'm sure there are cases where it happens.

[ZeoTiVo]

But, from another point of view, the programming change could be fairly major as it would involve moving from a global constant to a local variable (attached to the program data) in every instance where the system uses the 28 day rule and changing the program database to hold the new variable and changing the SP/ARWL options screen to allow this to be set.

it would fall into the fairly major category, no question. main problem is all the extra data that would be kept for longer as TiVo keeps track of what is previously recorded. all that data has to be indexed and it is my guess that some bug in the indexing is what caused the slowdown problems in 7.3 version. So a change to make that time longer would just be inviting performance problems to show back up.

[Stormspace]

it would fall into the fairly major category, no question. main problem is all the extra data that would be kept for longer as TiVo keeps track of what is previously recorded. all that data has to be indexed and it is my guess that some bug in the indexing is what caused the slowdown problems in 7.3 version. So a change to make that time longer would just be inviting performance problems to show back up.

Well, if you just replaced the global constant with another number the existing logic would likely work the same, just using the new period. Making it SP specific would be a nightmare and require a lot more processing and logic to resolve the schedule. Doable, but not as easy as changing 28 to 56 one place in the system. I would think too that if it allowed you to make this change you'd have to do a clear and delete before the new setting took place, otherwise you'd need a whole set of code to handle exceptions.

Now for why I don't think it should change...

My Wife loves M.A.S.H. It comes on Hallmark 2 or four times a day. Basically a lot. With the 28 day rule we almost never see a repeat during that month, or even the next and M.A.S.H. ran for twelve seasons. The show would have to be repeating a ridiculous number of times every two months for this to be a problem. My advice, once all you are seeing is repeats, turn them off. Do a first run only WL or SP.

[dswallow]

As I recall there is a hack out there that can track everything you watch and cancel recordings that get scheduled for shows you've already watched, no matter how long ago you watched it; you'd just need to do something to prune the list based on the desire for it not to exclude such shows forever but for a different period of time than the normal 28 days.

[ZeoTiVo]

Well, if you just replaced the global constant with another number the existing logic would likely work the same, just using the new period. Making it SP specific would be a nightmare and require a lot more processing and logic to resolve the schedule. Doable, but not as easy as changing 28 to 56 one place in the system. I would think too that if it allowed you to make this change you'd have to do a clear and delete before the new setting took place, otherwise you'd need a whole set of code to handle exceptions.
you misunderstand - currently the TiVo will hold what shows recorded for 28 days - that is data that needs to be stored in a database, indexed and then read through whne scheduling recordings. aIf you increase that number ot 56, even globally, you have increased the data to be kept two fold over time. That means bigger indexes and longer times to figure out scheduling shows, ect..

[bobbyt]

you misunderstand - currently the TiVo will hold what shows recorded for 28 days - that is data that needs to be stored in a database, indexed and then read through whne scheduling recordings. aIf you increase that number ot 56, even globally, you have increased the data to be kept two fold over time. That means bigger indexes and longer times to figure out scheduling shows, ect..

But it's not all data, it's just select data in a database...

It seems odd that it would create that much of a bottleneck just by increasing the length of time a record is kept, espcially since it should only take precidence when the tivo figures out the "to do" portion...

[ZeoTiVo]

But it's not all data, it's just select data in a database....
Uuummmmmm, that would still be all data.
But yes I do not know exactly how much of a drag on the system it would truly be. I do assume TiVo has done some analysis around it though in arriving at the 28 days.

[lordargent]

Heh, I want a wishlist to not record shows that have three thumbs down.

/has a category only wishlist for science fiction. This grabs good shows, but it also grabs some IMO bad shows (charmed, star trek 2.0).

[ZeoTiVo]

Heh, I want a wishlist to not record shows that have three thumbs down.

/has a category only wishlist for science fiction. This grabs good shows, but it also grabs some IMO bad shows (charmed, star trek 2.0).

you know a do not record this show via wishlist or via seasonpass or either one would be real handy. Thumbs are not really for that but I think a simple "do not record" menu with options like find by title would help a ton :up:

[JYoung]

Boolean Wishlists would also solve that problem and I think that logic is already in the codebase.

[OLdDog]

Boolean Wishlists would also solve that problem and I think that logic is already in the codebase.Even when the advanced WLs were accessible there was no "NOT" operator so I doubt the logic for "NOT" is in the code base.

Basically all the advanced WLS gave were "ORs" That is you could have one WL with "CSI" on one line and "Start Trek" on another and that WL would record all Star Treks and CSIs..

There is NOT a NOT and there is NOT going to be, at least NOT in the foreseeable future.

[Stormspace]

you misunderstand - currently the TiVo will hold what shows recorded for 28 days - that is data that needs to be stored in a database, indexed and then read through whne scheduling recordings. aIf you increase that number ot 56, even globally, you have increased the data to be kept two fold over time. That means bigger indexes and longer times to figure out scheduling shows, ect..

You know, I knew that. I just didn't think it all the way through. :o You're exactly right.

[JYoung]

There is NOT a NOT and there is NOT going to be, at least NOT in the foreseeable future.

I think you enjoyed that. ;)

[ADent]

The only use for a AWL (which I still have on my S1 DTiVo) is for missing episodes.

For example the Show Name is required then throw in the list of missing episode titles that are OR'd.

A NOT option would make the AWL truly useful.