Yep. This is one of the things I would still like to see.
I used to like the log from my old Topfield software, TEDS Suite, which gave me a breakdown of why a program was, or was not, selected. For example, below is an extract of an old log that I still have. Not a great example, but it shows the program is selected for recording based on the name, and then rejected because it is a repeat. If I had multiple conditions set up for the Recording Rule, it evaluated each and showed the result.
--------------------------------------------------------------------------------
ABC2 Fr 20:30 - Sep 10 - 60 mins Life on Mars
[Crime] A Manchester United fan is murdered as a local derby approaches and Sam, Gene and Annie go undercover to find the killer. Cast: John Simm; Philip Glenister (2004, UK) (M) [Rpt] M
- Search String: Life on Mars Rating: D Filters: Channel Non-HD Repeat
Matched on: Life on Mars
Rejected by: Repeat filter
--------------------------------------------------------------------------------
The log was actually better than the above example, as it included graphics to show the result and colour coding. I have attached an example of the log in the web archive format, so the simple graphics can be seen.
I'm sure a much better log could be developed based on the MC data available. Knowing why a recording was missed, or why some unexpected recording was made, makes any DVR/PVR software far easier to use, helps keep the WAF high or at least reduces the plunge when a favourite program isn't recorded, and generally help users learn what the program is doing, keeping them happier.
Of course this is related to my comments about visibility of the Recording Rule ID in both the Guide data, the To Be Recorded list, the Recording Rules list, and any recorded shows views. It is all about understanding what MC is doing with regard to recordings, and therefore understand how to use the functionality better and avoid problems.
(Sorry. I'll get off my soapbox now.
)