44 minutes ago
Current setup as per signature all using NextPVR v7.0.3.250920
On this occasion the recording was made, correctly (kind of), on the RPi4 server.
The issue that is causing me problems is not with the recording itself but why the recording was made ?
As you can see the recording started at 15:59 on Nov 28 and completed at 17:05. However this recording was not scheduled by me and the path/filename is completely incorrect for any of my NextPVR recordings:
/home/pi/recordings/local/TVShows/Trucking Hell/Trucking Hell_20251128_16001700.ts
instead of normally, for example:
/home/pi/recordings/local/TVShows/Trucking Hell/Season 08/Trucking.Hell.S08E09.ts
From the recorded filename used however I can tell that this is a previously imported recording (from my old Humax box) which I transferred to NextPVR some 3 years ago.
So what caused this programme to get recorded again with an old file name ?
Bemused :-)
Chris
On this occasion the recording was made, correctly (kind of), on the RPi4 server.
The issue that is causing me problems is not with the recording itself but why the recording was made ?
As you can see the recording started at 15:59 on Nov 28 and completed at 17:05. However this recording was not scheduled by me and the path/filename is completely incorrect for any of my NextPVR recordings:
/home/pi/recordings/local/TVShows/Trucking Hell/Trucking Hell_20251128_16001700.ts
instead of normally, for example:
/home/pi/recordings/local/TVShows/Trucking Hell/Season 08/Trucking.Hell.S08E09.ts
From the recorded filename used however I can tell that this is a previously imported recording (from my old Humax box) which I transferred to NextPVR some 3 years ago.
So what caused this programme to get recorded again with an old file name ?
Bemused :-)
Chris
Servers: NextPVR Linux Docker and RPi4 8GB both official rel. Recordings: OMV 7.x NAS, NFS share mounted to Docker container and RPi. Client: Amazon Firestick via Jellyfin Addon, Docker JellyFin, NextPVR addon