Web app import recording feature will now accept side by side style xml files

[ceejayemm]

Sub

I was glad to see that the ability to import side by side style XML file has been incorporated in to v5.1.3.210711, but it doesn't seem to work as I would expect yet.

I have had a problem with my normal HDHomeRun Quatro and am awaiting a replacement from SiliconDust, so in the meantime I installed NextPVR (v5.1.2.210603) to a spare Windows 10 Pro (64bit) PC which has a TBS 6280 PCie Dual Tuner and used this to record some films. This was fine, but I now need to move these recording to my normal recording library so I copied the .ts and .xml files from the Windows PC to my normal NAS film library.

I updated my RPi server to v5.1.3.210711 and I edited the xml files to change the filename path from Windows format to Linux format. I then tried to import copied the xml files from the NAS but unfortunately this failed ('No recordings imported'). I reviewed the .XML file and eventually ended up having to add <recordings></recordings> and <name></name> (with the relevant film name incorporated) tags to the .XML file before I could get the recordings to be imported.

Ok, so the recordings were made with an earlier version of NextPVR (v5.1.2.210603) so I upgraded the PC version to v5.1.3.210711 and tried another recording with this version. The resulting .ts and .XML files were copied to the NAS as previously but the .XML file was in exactly the same format as the earlier version and, again, I needed to change the filename path (to be expected) and add the <recordings> and <name> tags before I could get the recording to import.

There are no apparent entries in the log file for the failed imports, there used to be in previous versions. I have uploaded the log files and the original/edited XML files for you to see.

Chris

[ceejayemm]

Bump

[sub]

I’m out of town until Monday. Bump it again then and I’ll take a look.

[ceejayemm]

Bump - as requested

[ceejayemm]

Bump

[sub]

Hmm, I just tried importing the your recording xml, and it imported fine (when I ignored the fact the file didn't exist on my drive).

Are you positive it didn't import on your first attempt? Your log messages only seem to match the scenario where it didn't bother to import the recording because there was already one in the database with the same file name.

I've attached an updated nshared.dll, which adds a couple of log messages to make it clearer why a recording might not have imported.

[mvallevand]

Did you try and import the _original xml ? When I tested it from the browser <recording> needed to be wrapped in

<recordings>
</recordings>

Also without <name> the filename is used as the name not the title.

Martin

[sub]

Doh - right you are. (should have gone back and reread the details I'd forgotten since originally reading it)

I'll fix.

[sub]

This version fixes the issue.

[ceejayemm]

Sub / Martin

Thanks for your work on this. I installed the new .DLL file and restarted my server. I imported a recording I have never had on the PI server previously and yes it was imported BUT with the full filename as the recording title, including the file path as well, in my case '/home/pi/nas_recordings/TVShows/Star Trek Voyager/Season 02/Star.Trek.Voyager.S02E10.ts' - which is a bit of a mouthful and difficult to explain to my wife. This is because, as Martin points out, without the <name></name> tag in the xml file that is what you currently get.

I realise you can only work with what you have BUT there is, at least in the xml file I used for this test, a useful <title></title>tag - could the contents of this tag be used as the recording title IF the <name></name> tag doesn't exist ? I have attached the xml file I used for this test which was only edited to change the original windows file path to a linux path for the PI server I imported the recording to.

Thanks for your help so far.

Chris