Unique Id

[mvallevand]

Sub, I'm not sure how you use the unique_id field to block future recordings of deleted events, but I noticed in this database http://forums.nextpvr.com/showthread.php...m&p=430524 several unqiue_id's that weren't going to be unique over time.

Martin

[sub]

I havn't looked at that database, but what were the IDs that were not unique?

I know those that end in 0000 are not necessarily unique.

[mvallevand]

The were 4744 records with S#E#

Code:

S002E005
S002E006
S002E003
S009E009
S002E004
S002E013
S001E010
S002E014
...

Martin

[sub]

Ah, sorry - I assumed you were talking about schedules direct.

Thats not really what I'd intended to happen, but let me think about it for a bit to decide if it's a problem or not.

[sub]

With the way the NextPVR scheduler does it's thing, it wouldnt have caused it to stop episodes from being scheduled (except possible with the deleted history), but it is worth changing the unique ids genereated by xmltv_ns to be more consistent with schedules direct. ie, making them unique across shows. The attached patch implements this by prefixing the show title.

[jcjefferies]

Who usually generates these unique IDs or Series IDs used by PVRs to detect programmes in a "series", the broadcaster or EPG generator? I know different countries do it differently but when available are they transmitted as part of the EPG or along with the programme data stream. I looked at a couple of UK XMLTV EPG sources and neither contained any IDs.

[sub]

In the UK PVRs use some proprietary data hidden away in the stream. NextPVR's DVB EPG reader doesnt know anything about this data. I dont know whether any of the xmltv sources in the UK also carry this information.

[b00sfuk]

The database in question that generated these IDs used both a UK DVB EPG source (for radio) and a xmltv source for TV imported from Digiguide (using XMLTVGUI)