2007-01-31, 02:57 AM
KingArgyle Wrote:Here are my list of basics that aren't there. Not a long list:
2. Eliminate duplicates and ignore shows that have already been recorded. You can do this without the use of ZAP2It, but it really relies on the quality of the XMLTV source. I don't use the ZAP2IT format, but the XMLTV format through the North American grabber (which gets it's info from Zap2It). I use a combination of RecTracker and CDK Scheduler to eliminate and not record duplicates. It gets about 98% of the shows, but not 100%. The key is the Title, Sub Title and Description checks. If these are different it's considered a new episode. Also, shows that have been already recorded are tracked in a seperate database or table. This is checked to when scheduling to determine if it should be scheduled or recorded. Again, this relies on the quality of the data provided by the guide, not reliant on special features of ZAP2IT. This should also be enabled as it is now on a recording by recording basis.
4. Diskspace management, not just show management.
#2 really strikes home at my house. The kids record everything on a channel and then delete the shows when they are done. With all the repeats I spend quite a bit of time just re-deleting recordings they have already watched. It is a pain and fairly slow. It might be nice to select a few recordings and delete all at once.
Since I am a pvr150 user in the States, I don't think closed captions are a possibility but they are sorely missed in our house.
Thought I would throw my 2 cents on the committee idea.
If the program were open source and there were multiple programmers, one could see the benefit of an committee to set goals. For a program that is written by one person, I can't see any motivation for the programmer to have a group of people telling someone what they want coded in his volunteer time.
I think we get really cool features in almost every release, and the system today seems to work pretty well.