ENVAR style recordings dir in exported XML file

[bgowland]

Just a suggestion rather than a wish...

It would be nice if the Export Recordings used an env variable for the recordings directory / filename path rather than absolute file path. It's not something people use regularly and a lot of users probably never export/import recordings. It would save editing the xml file if the recordings dir is different.

Cheers,
Brian

[sub]

Sounds reasonable. I've added something like this for the next build.

[bgowland]

Cool, it would make a nice touch.

I think I only ever did it once with my old Win XP system but  I've done it 3 times in the past couple of weeks. I setup my capture card in my debian 11 desktop a few months ago for testing. I finally got my new machine running a few weeks ago - debian 12. A couple of days later I decided I didn't like the hardware configuration and fitted a new SSD for OS and dedicated an M.2 NVMe to recordings. I then realised I'd created the NVMe recordings directory with incorrect permissions - nextpvr would record and play but the recordings I copied in didn't have the right permissions. I ended up creating another recordings directory on the NVMe with correct permissions and moved everything into that. All good fun.

Cheers,
Brian

[mvallevand]

If you create a standalone XML file with the recording(which I recommend) NextTool will use that for importing with full metadata, otherwise it just uses the filename.

Martin

[bgowland]

To be honest I've been back at rookie level since I restarted and haven't looked at any utilities. I was just using the export / import buttons on the web ui. It was the fact I changed my mind about recordings directory meant I had to tweak the exported xml files a few times. The basic metadata provided by the OTA EPG has copied in fine.

Cheers,
Brian