Unique_id no longer populated!

[jcjefferies]

I belatedly updated to the latest version of NextPVR yesterday and today it is recording programmes I have recently watched. I checked the database and the "unique_id" field is blank.

For several years I have been using EPG Collector to extract the "episode-num" broadcast with the EPG data. As the data includes both the "Series_id" and the "Unique_id" of each programme I process the XML file to replace the "series_id" with a "0" so the "unique_id" field in the database is in the form 0:xxxxxxx:0 and this is also the format in the Recently_Deleted table.

Today I added the latest patches and the "unique_id" for some channels appears but in a different format which includes the programme name. The trouble is I have over 1200 recently deleted recordings and almost as many existing recordings so don't want to start again!

Is my best solution to do a clean install of v3.3.9 and import the backup xml files and possibly config.xml? A patch I know I needed is still available!!

Chris

[sub]

It didn't used to populate the unique_id for xmltv (unless your xmltv data was from schedules direct), but that changed in 3.3 build to improve things for more users.

I'm sorry this broke your previous manual work-around. Not really sure what to suggest on this one. You could maybe change your xml pre-processing to force the id you want to use with the system="dd_progid". This takes the value verbatim.

[jcjefferies]

Sub
From what I remember in the version of NextPVR released July/August 2012 you added support for XML files from EPG Collector. I was already using EPG Collector as it was a work around for partially populated EPG I sometimes got using native NextPVR to load the EPG. I seem to remember you saying that if an XML file from EPG Collector was detected "unique_id was populated. Before importing I process the XML file to remove the unwanted "series_id" which is also broadcast.

http://forums.nextpvr.com/showthread.php...-Collector

I have reverted to v3.2.9 and have imported recordings and settings from 3.3.8 and I seem to be back to where I was with "unique_id" populated again and only 30 pending recordings instead of over 100 yesterday.

What I will do is install the latest version of NexrPVR on a test server. Can you clarify where the setting you suggested system="dd_progid" should go.

Chris

[sub]

Can you clarify where the setting you suggested system="dd_progid" should go.

Here is an example that uses system="dd_progid"

Code:

    <programme start="20141005123000 -0700" stop="20141005130000 -0700" channel="I5.28460688.microsoft.com">
        <title lang="en">Larry King Reports</title>
        <desc lang="en">Larry King investigates Omega XL, the ultimate all natural solution for pain and inflammation.</desc>
        <category lang="en">Educational</category>
        <category lang="en">Other</category>
        <category lang="en">Paid Programming</category>
        <episode-num system="dd_progid">SH01795054.0000</episode-num>
        <subtitles type="teletext" />
    </programme>

[jcjefferies]

Thanks for the suggestion Sub.

I thought I was back working but I had several problems! I understood from what has been said previously somewhere that the database format was changed in v3.3 so could not use it when I went back to v3.2 so imported the data from the backup xml files. I later realised that this does not import the "unique_id" of each recording imported and the "Recently Deleted" data is not imported either. So I exported the "Recently Deleted" and "Scheduled Recordings" tables from the V3.3 database from the previous day and imported them into the v3.2 installation database.

I am now back working using V3.2, as I am seeing episodes not being recorded because they were recently deleted, or there is an existing recording or the episode is already scheduled. I will now investigate what I can do to persuade V3.3 to recognise my XML files using the different "System" tag in the file using a test server.

Chris

[jcjefferies]

Sub

I built a test NextPVR server running version 3.3 and confirmed that the processed TVguide.xml file from EPG Collector which worked in version 3.2 now does not populate "unique_id" in the EPG table.

I then did a Find & Replace on TVguide.xml changing (system="xmltv_ns") to (system="dd_progid") as you suggested and "unique_id" is now populated again. There is a minor problem because the previous versions of NextPVR removed the spaces in the id so "0 . xxxxxx . 0" became "0.xxxxxx.0" in the database but v3.3 does not. This is something that can easily be cured by changes to the script I use to process the TVguide.xml before it is loaded into NextPVR.

If I cannot find a way to make EPG Collector use the system="dd_progid" setting then I will add a find and replace to my pre processing script.

Thanks for your help Sub

Chris

[sub]

I then did a Find & Replace on TVguide.xml changing (system="xmltv_ns") to (system="dd_progid") as you suggested and "unique_id" is now populated again. There is a minor problem because the previous versions of NextPVR removed the spaces in the id so "0 . xxxxxx . 0" became "0.xxxxxx.0" in the database but v3.3 does not. This is something that can easily be cured by changes to the script I use to process the TVguide.xml before it is loaded into NextPVR.

The system="dd_progid" logic doesn't remove any spaces, because that field has never had spaces in it in the past. You'd probably have to remove the spaces from your data to make it look more like real data you'd get there.

[jcjefferies]

Looking at my pre processing script which replaces the unwanted "series_id" with "0" I can see it reinserts the spaces in the field to maintain the original format. My son wrote it in PHP for me so will get him to modify it to remove the spaces. However there is no rush to sort it out as the previous version of NextPVR still does everything I want!

Chris