2015-10-01, 07:34 AM
I found some orphaned recording files, so I thought that I'd use VidImport to check for any more. I downloaded the latest version (v1.71) from the Wiki. But it seems that, by default, it is not finding NextPVR's Recording-Backup.xml to skip recordings already in the NPVR database. Full logs are attached. Here's the section showing that it's not finding Recording-Backup.xml:
If I explicitly point it to the Recordings-Backup.xml file on the command line, then it does find it and use it. See:
I'm guessing that the problem is that it isn't getting/setting the NPVR Data Directory properly since it is being listed as null in both logs.
Hopefully, carpeVideo is still monitoring this forum and can get us a fix. :-)
There also seems to be a problem with the auto-import (again the default for drag & drop operation). When it runs NextPVR to do the import, NextPVR.exe is hanging and I have to kill it with the Task Manager. The full NPVR.log file is in the attachment, but the last few lines are:
I am using Remote Desktop Connection to get to the server to run VidImport, so I suppose that could be a problem for NextPVR.exe. But just doing an import doesn't have any user interface, so I wouldn't think so. This part is probably a bug for sub.
Code:
vidImport.exe version 1.71
Settings used:
----> Npvr Install Dir = C:\Program Files (x86)\NPVR\
----> Npvr Data Dir =
----> Npvr Recording File = recording-backup.xml
----> Show File = showDetail.txt
----> Autoimport = True
----> XmlOut = videos.xml
----> Series Only = False
----> ImdbLookup = True
----> Autoimport = True
----> Season Prefix = s
----> Episode Prefix = e
----> Episode Suffix = .
----> Write NFO = False
----> Video extensions = avi~mpg~ts~mp4~mkv~mpeg~dvr-ms~wmv~divx~ifo~mov~dvrms~mov~flv
----> Include Season in Episode = False
----> Starting dir/file = F:\NPVR Recordings3
Reading showfile showDetail.txt
Checking for gbpvr export file:recording-backup.xml
Error: recording-backup.xmldoes not exist. Skipping file
Recursing: F:\NPVR Recordings3
If I explicitly point it to the Recordings-Backup.xml file on the command line, then it does find it and use it. See:
Code:
vidImport.exe version 1.71
Settings used:
----> Npvr Install Dir = C:\Program Files (x86)\NPVR\
----> Npvr Data Dir =
----> Npvr Recording File = C:\users\public\npvr\recording-backup.xml
----> Show File = showDetail.txt
----> Autoimport = False
----> XmlOut = import-recordings3.xml
----> Series Only = False
----> ImdbLookup = True
----> Autoimport = False
----> Season Prefix = s
----> Episode Prefix = e
----> Episode Suffix = .
----> Write NFO = False
----> Video extensions = avi~mpg~ts~mp4~mkv~mpeg~dvr-ms~wmv~divx~ifo~mov~dvrms~mov~flv
----> Include Season in Episode = False
----> Starting dir/file = F:\NPVR Recordings3
Reading showfile showDetail.txt
Checking for gbpvr export file:C:\users\public\npvr\recording-backup.xml
Reading gbpvr export: C:\users\public\npvr\recording-backup.xml
Recursing: F:\NPVR Recordings3
I'm guessing that the problem is that it isn't getting/setting the NPVR Data Directory properly since it is being listed as null in both logs.
Hopefully, carpeVideo is still monitoring this forum and can get us a fix. :-)
There also seems to be a problem with the auto-import (again the default for drag & drop operation). When it runs NextPVR to do the import, NextPVR.exe is hanging and I have to kill it with the Task Manager. The full NPVR.log file is in the attachment, but the last few lines are:
Code:
2015-10-01 02:07:37.087 [INFO][3] Online check reports version info:
<version><component name="NextPVR" version="3.5.7" display="NextPVR 3.5.7"><url>http://forums.nextpvr.com/showthread.php?57088-3-5-7-available-(30th-August)</url></component></version>
2015-10-01 02:07:37.088 [INFO][3] current online version: 3.5.7
2015-10-01 02:07:37.088 [INFO][3] last notified version: 3.5.7
2015-10-01 02:07:37.682 [DEBUG][1] Frame Render Rate=96.5237655639648
I am using Remote Desktop Connection to get to the server to run VidImport, so I suppose that could be a problem for NextPVR.exe. But just doing an import doesn't have any user interface, so I wouldn't think so. This part is probably a bug for sub.