Vidimport

[keith_leitch]

I don't see the behavior you describe but I do see it missing some descriptions. Try this version and you may want to delete your showfile.

Also theTVDB seems to still be going strong.

Ah...I was typing TVDB.COM, not THETVDB.COM.

The update seems to work just fine...thank you very much. As you've said, I sometimes get odd behaviour (like messages about shows already having been added when they have not) unless I delete the showdetails.txt file; is there any disadvantage to deleting this after each use?

[carpeVideo]

The only disadvantage is time and bandwidth - with the showfile if the show has been added and the episode info is in there it should use the showfile description rather than hitting the internet again. It is also used in guidePlus but I don't think there are any live users of that but me

[carpeVideo]

Two small new features
* it will read the NPVR directory and look for the recordings XML there if it exists. It will not automatically import into NPVR so you must specify autoimport=off for NPVR and import the generated file manually from NPVR.
* if a file has a gbpvr or npvr metadata alternate filestream the contents of that file will be written to <filename>.xml allowing the data to be saved if being moved to a non-ntfs filesystem (for example unRaid which uses the reiser filesystem). Use the "writeMetaDataXml" switch for this.

[keith_leitch]

Two small new features
* it will read the NPVR directory and look for the recordings XML there if it exists. It will not automatically import into NPVR so you must specify autoimport=off for NPVR and import the generated file manually from NPVR.
* if a file has a gbpvr or npvr metadata alternate filestream the contents of that file will be written to <filename>.xml allowing the data to be saved if being moved to a non-ntfs filesystem (for example unRaid which uses the reiser filesystem). Use the "writeMetaDataXml" switch for this.

Thanks, Carpe. Does this also incorporate the changes you made three posts ago, and the changes immediately prior (to correct the error caused when searching for an NPVR database)?

[carpeVideo]

Thanks, Carpe. Does this also incorporate the changes you made three posts ago, and the changes immediately prior (to correct the error caused when searching for an NPVR database)?

Yes - it should incorporate all changes

[BrettB]

Two small new features
* it will read the NPVR directory and look for the recordings XML there if it exists. It will not automatically import into NPVR so you must specify autoimport=off for NPVR and import the generated file manually from NPVR.
* if a file has a gbpvr or npvr metadata alternate filestream the contents of that file will be written to <filename>.xml allowing the data to be saved if being moved to a non-ntfs filesystem (for example unRaid which uses the reiser filesystem). Use the "writeMetaDataXml" switch for this.

With recent NPVR versions, there are 2 alternate data stream files with the .ts recordings. One is the "old" metadata.xml, and the other is a new Timing.Info. It appears that (for me, at least) vidimport is reading the Timing.Info alternate stream instead of the metadata.xml stream because if I use the writeMetadataXml switch, the file that gets created next to the .ts recording file contains the timing info not the metadata. Also, the import file has the generic

Code:

<channel>IMPORT</channel>
<subtitle />
<description>Not Found</description>

lines for all of the recordings to be imported rather than the correct info from the metadata.xml stream.

[carpeVideo]

With recent NPVR versions, there are 2 alternate data stream files with the .ts recordings. One is the "old" metadata.xml, and the other is a new Timing.Info. It appears that (for me, at least) vidimport is reading the Timing.Info alternate stream instead of the metadata.xml stream because if I use the writeMetadataXml switch, the file that gets created next to the .ts recording file contains the timing info not the metadata. Also, the import file has the generic

You are correct it is just grabbing the first alternate stream - I noticed that and fixed in in guidePlus but I forgot to do so in vidImport - I will release a new one soon.

[carpeVideo]

v1.43 on the wiki should read the correct stream from NPVR if there are multiple ADS streams attached to the file.

[BrettB]

v1.43 on the wiki should read the correct stream from NPVR if there are multiple ADS streams attached to the file.

This new version did fix the problem with getting the wrong metadata from the ADS stream.

However, when I try to import the generated xml file into NPVR via the settings/import function, I get a message box saying the recordings were imported, but the don't acutally show up in the recordings list. The npvr.log file show:

Code:

2010-10-24 11:56:14.581    [ERROR][1]    Unexpected error saving scheduled recording: System.Data.SQLite.SQLiteException: Abort due to constraint violation
SCHEDULED_RECORDING.event_details may not be NULL
   at System.Data.SQLite.SQLite3.Reset(SQLiteStatement stmt)
   at System.Data.SQLite.SQLite3.Step(SQLiteStatement stmt)
   at System.Data.SQLite.SQLiteDataReader.NextResult()
   at System.Data.SQLite.SQLiteDataReader..ctor(SQLiteCommand cmd, CommandBehavior behave)
   at System.Data.SQLite.SQLiteCommand.ExecuteReader(CommandBehavior behavior)
   at System.Data.SQLite.SQLiteCommand.ExecuteNonQuery()
   at NUtility.ScheduledRecording.Save()

Anyone (carpe?, sub?) know what new required field is missing from the xml file?

[carpeVideo]

It may be that the xml file is a different structure than the one for GBVPR - can you post the XML file that you are trying to import?