HHmm... glad i'm not the only. Could it be due to somehow due to the "program id", or whatever id that MCE / EPG database generates??
I found this quote written by "impact" on the xpmediacenter forum: Could this be the problem. I hope I'm not breaching any copyright issues here....
Quote:
gslender - In answer to your question.... MCE operates at two levels...
It uses the name of the program to identify all series recordings... And it only checks on the names supplied, so if in week one, lets say you load up something like 'Survivor" and set a series recording for it, the following week the data load supplies the name 'Survivor Exile' - then MCE does not see this as the same program and does not record it.
All Series recordings are matched on program name.
Manual recordings are set up and tracked by a unique program identifier, this number which is meaningless should be a number that is only unique for that one program. So if you do a manual recording or cancel a one off recording - MCE does its business by using that internal number.
The problem is that in XMLTV DTD there is no real unique number similar to what MCE expects, and no mechanism to remember the numbers from the previous week. So these unique identifiers are calculated. Typically they are hashed from other available data - like channel its being shown on, start time, end time etc... this in turn creates a useable number that is hopefully unique. And why Monster says 99% accuracy - because the algorithm is flawed to give anything better.
BRP does not use a db to remember what occured in the previous week, so uses this algorithm method to generate a number each week, most of the time it allocates the same number to a repeating show week in week out, however if a program was to change timeslot / day etc, it would be generating a new number that was different to the previous one.
So over a period of time, you may find drifting of the numbers being generated and thus see some strange results - manual recordings disappearing, an extra recording appear, something recorded that you had canceled... but the most annoying one of all - recordings being grouped incorrectly.
Even though a series may be set up to record, MCE uses the internal id and not the name in the 'Recorded TV' section... Show by date works fine - as nobody fiddles with dates, but Show by Name which sorts shows by their name can often mix the shows up because of the inaccurate internal id's.
So over in Microsoft's real EPG solution - in the US and the UK and.... They do not use XML, they have a database, a proper database that knows what is shown this week, what was on last week, last month, last year. This guarantees a unique identifier for each unique show and thus all functionality works fine in MCE.
ICETV uses a database, so the integrity is there, BRP does not and can give you these annoyances. If BRP used a db then all these red dot issues and groupings would be gone too.
On a newly formatted machine, with BRP 3.5 and some automated test scripts I used previously, the grouping of program names inaccurately occured in the 4th week of data I supplied, and it appears once it occurs, it becomes more and more predominant - ie. it may take you 600 recordings before you notice the first issue, but then it starts occuring on every 100th...
Perfectionist I may be..... But I like my guide to be accurate, and if not to understand why - and thats the issue, others always ask questions and get no satisfactory replies...