I set up comskip to run in parallel. I'll start playback 45-60 mins into a recording, and NextPVR will read from the EDL, and skip commercials, just like it's supposed to. Over time, NextPVR will gradually start the commercial skips earlier and earlier in time -- by the time I'm at the 2 hour (ish) mark, commercials are being skipped 5-10 seconds early, cutting off that much of the program (and playing that much of the commercial at the end of the skip period). If I stop playback and re-start from my saved position, commercials start getting skipped at the right time again. If I let the program finish and then start playback, the skip locations are correct from start to finish.
Any idea what's going on, and how I can fix?
I'm using Kodi with the NextPVR PVR Client addon. I've tested most on a Vero V OSMC device. My client is set to "Timeshift" Live TV Method, with a Pre-buffer time of 3 seconds, Live TV chunk size of 64, and Recording chunk size of 32 (I don't know what these options mean, btw, so if they're suboptimal, lmk). My device is on a local hardwired LAN with plenty of bandwidth between server & client.
The NextPVR server is running in the custom container published by @Ranbato , but I've been experiencing this behavior for years while I was running NextPVR on bare metal -- never brought it up before b/c it was just me using the frontend. Now family is getting involved ...
Posted by: artmetz - 2026-01-04, 06:47 PM - Forum: Windows
- No Replies
I have a TerraMaster NAS where I keep archived recordings. Archiving recordings to the NAS was failing (copying the files via windows explorer fails as well). (My old QNAP NAS did not have this issue. Here are the relevant lines from the NPVR log:
2026-01-03 09:55:27.930 [DEBUG][66] ArchiveRecording@2(469933:Today, TV)
...
2026-01-03 09:55:28.037 [DEBUG][38] Source File: D:\nextpvr\Today\Season 74\Today.S74E89.ts
2026-01-03 09:55:28.041 [DEBUG][38] Target File: \\NAS0324\Public\videos\tv\Today\Season 74\Today.S74E89.ts
2026-01-03 09:55:28.041 [DEBUG][38] Archiving...
2026-01-03 09:55:28.042 [DEBUG][38] Starting: C:\Users\Public\NPVR-data\Scripts\PreArchive.bat "D:\nextpvr\Today\Season 74\Today.S74E89.ts" "\\NAS0324\Public\videos\tv\Today\Season 74\Today.S74E89.ts" 469933
....
2026-01-03 09:57:05.298 [ERROR][38] Unexpected error archiving file: System.IO.IOException: The requested operation could not be completed due to a file system limitation
at System.IO.FileSystem.MoveFile(String sourceFullPath, String destFullPath, Boolean overwrite)
at NShared.ArchivingService.WorkerThread()
As a work around, I was able to use 7zip to zip and unzip the recordings, then I was able to archive them.
This issue was caused by the source NTFS files having alternate "streams" that are not supported by the destination filesystem (BTRFS or EXT4).
You can use this tool from Microsoft to remove them: https://learn.microsoft.com/en-us/sysint...ds/streams
Now I run this command on a nightly basis against the recording directory (via the updateepg script).
streams -s -d "D:\nextpvr"
If you simply want to check the files, remove the -d option:
D:\nextpvr>streams -s
I thought I'd try the SD 7 day trial. I've only tried once and it messed up a lot of stuff. Despite specifying UK, it download and imported a lot of channel/show data with German show titles and incorrect timings. I reverted to OTA EPG updates, emptied the EPG and manually updated - everything looked OK but several shows failed to record that night and the next day or two (this was earlier in the week and I haven't tried since).
Is it possible to see what npvr downloads BEFORE it imports so I can check it's valid? I had an email from SD this morning my trial finishes on Monday and I haven't really had a chance to see what it can do.
I've been running NextPVR on bare metal for some time, and now I'm switching to a Docker container. In doing so I'm learning more about NextPVR.
I think I understand that the /buffer dir is used to store a temporary (partial) copy of the mpeg stream being sent to the client. I think I understand it is also used to store the mpeg data stream being written as it is being recorded. Once the client is done playing back the buffered copy is destroyed; or when the recording finishes, the file in the buffer directory is written to the /recordings directory.
... do I have that right?
I'm asking b/c I'm trying to optimize the mappings of these directories to docker volumes / bind mounts. I currently have /recordings on a spinning-disk array, and I was thinking of putting /buffer onto an SSD, if that would make the experience snappier for clients. I have much more spinning disk space than I have SSD space, not surprisingly. For a machine that might at-most record 2 3-hour-long football games at a time
in 1080i at 15Mbps, and play back to 2 clients at a time, how much space would you think the /buffer dir need?
How do I remove the many failed recordings, without doing one at a time, because of a downed tuner. I've been to Programs folder and Public folder looking for some sort of file without any luck or I don't know what I am looking for.
In Kodi, if I select a show via the TV Guide and then select Add Timer, the dialog has the timer type as Recording: Repeating (guide) by default.
I can't see any way to change this behaviour in the NextPVR add-on settings, so is it possible to add an option to set an alternative default? For my use case, I'd prefer Recording: one time (guide) to be the default.
A Record isn't played on web UI and only shuttering on desktop UI.
Moreover none of the UI's allow fast forward/backwards scrolling or any handling of the recorded file at all.
Any clue?
Logfiles should be attached
