GB-PVR => NPVR migration; video library missing episode ID information

[mvallevand]

I wrote a utility to help browse these fields that I guess only I use http://forums.nextpvr.com/showthread.php...post443946

Code:

select name,XmlLookup(event_details,"/Event/UniqueId") from scheduled_recording

Martin

[Braklet]

What are you using to look in the npvr.db3? It sounds like it's not showing you all the data in that column. I'm guessing it's all there. The unique id is later in that data.

Quite possible, although I've had good luck with SQLite Maestro.

The column does show some non-printable characters for each imported recording as well, that could be throwing off Maestro.

[Braklet]

Thanks for the utility, Martin!

I copied XMLLookup.exe to my NPVR data directory (C:\Documents and Settings\All Users\Application Data\NPVR, this is 32 bit XP Pro) along with System.Data.SQLite.dll. Fired up the tool, copied your query quoted above into the window, hit Button1, and got a "Unable to open the database file" popup. npvr.db3 is in there, not sure what's up?

[Braklet]

I pulled down the SQLite shell from sqlite.org and used my faulty memory to output the contents of my scheduled_recordings table. It appears OK, although the whitespace and non printable characters seem to throw SQLite Maestro for a loop. Here's an example of one row:

Code:

||1|2|0||||
2408|Off the Air|E:\Video\GB-PVR\Off the Air\Nightmares.mpg|2|2012-12-22 09:00:0
0|2012-12-22 09:15:00|0|0|0|176 TOON|    <Event>
      <OID>0</OID>
      <Title>Off the Air</Title>
      <SubTitle>Nightmares</SubTitle>
      <Description></Description>
      <ChannelOID>0</ChannelOID>
      <StartTime>2012-12-22T09:00:00.0000000Z</StartTime>
      <EndTime>2012-12-22T09:15:00.0000000Z</EndTime>
  <UniqueID>EP014135410007</UniqueID>
    </Event>

So I think sub's updated DLL did what I wanted, at least I hope so. Won't know for sure unless I run a new test from scratch or continue with daily EPG updates to see if repeats keep getting scheduled.

Thanks, all.

[mvallevand]

Thanks for the utility, Martin!

I copied XMLLookup.exe to my NPVR data directory (C:\Documents and Settings\All Users\Application Data\NPVR, this is 32 bit XP Pro) along with System.Data.SQLite.dll. Fired up the tool, copied your query quoted above into the window, hit Button1, and got a "Unable to open the database file" popup. npvr.db3 is in there, not sure what's up?

Sorry, it needs to be placed in the Program Files NPVR folder with but it looks like you got it.

Martin

[Braklet]

Tried the Program Files/NPVR directory too, but still got the "Unable to open the database file" popup. But yeah, I think the event data were migrated over with the new DLL.

[ElihuRozen]

Tried the Program Files/NPVR directory too, but still got the "Unable to open the database file" popup. But yeah, I think the event data were migrated over with the new DLL.

From Martin's other thread:

lets you test your SQL (hard coded to the Win7 default)

In this thread you indicated the WinXP default for your data directory.

[Braklet]

It appears that UID is present in my imported SCHEDULED_RECORDINGS.Event columns, but NPVR is still scheduling duplicate recordings after EPG update.

How does NPVR determine if a recording is a duplicate?

I hope there are some simple database tweaks I can perform to ensure that NPVR properly detects duplicates in my imported GB-PVR recordings.

TIA!

[Graham]

How does NPVR determine if a recording is a duplicate?

There is a Unique_id in the epg_event table. It's value comes from Schedules Direct (if used) or is generated by NextPVR ...

http://forums.nextpvr.com/showthread.php...post450565

http://forums.nextpvr.com/showthread.php...post451625

[Braklet]

I just took a closer look at npvr.db3 using SQLite Maestro. The output attenuation that kept me from seeing any imported Unique ID data has to do with the fact that the SCHEDULED_RECORDINGS.event_details column shows up typed as varchar(50), even though it ends up longer than that. I tried changing the definition to varchar(500) and was able to see all the data.

This reveals another issue: the recordings import preserves all the event strings, so that recording title, subtitle etc. show up as expected. But no corresponding rows are created in the EPG_EVENT table and the embedded event OID is left 0. So as it stands, NPVR can't detect imported duplicates.

I'm not too handy with SQL queries but I guess I'll have to learn.