Recording Directory

[mvallevand]

Is it possible they are in C:\Program Files\NextPVR\

Running a sample here from am UNC I get a MUP with handle64

BF0: File \Device\Mup\172.16.3.105\recordings\Dynasty\Season 04\Dynasty.S04E03.The.Note.ts

Martin

[scaesare]

Interesting... I just started a recording a while ago, and sure enough, free space is dropping on the NextPVR system drive. 

The files aren't in the app directory though, nor in any of the named sub-directories. But there's one unnamed sub-dir:

11/11/2023  11:28 PM    <DIR>          .
11/11/2023  11:28 PM    <DIR>          ..
03/06/2024  11:50 AM    <DIR>
05/31/2023  06:52 PM    <DIR>          runtimes
06/01/2023  10:51 AM    <DIR>          Other
05/31/2023  06:53 PM    <DIR>          wwwroot
07/13/2023  12:39 PM    <DIR>          data
05/31/2023  06:52 PM    <DIR>          client

Actually, I suspect it's named with a space, although attempting to quote to change to that directory fails. And it has today's date...

Any thoughts on why this would be, as I had defined a network share initially, and I have several recordings that made it there? Then it stopped at some point on my old file server, and won't put ones there when defining the new share...

Or why the log files indicate the share path as the location when it's clearly not putting them there?

[mvallevand]

Yeah thought the folder was a space.

Code:

C:\Program Files\NextPVR\ \192.168.100.2\pvr\Emergency!\Season 03\Emergency!.S03E19.The.Hard.Hours.ts

Look back at post#1 is that a space in config.xml too?

Martin

[scaesare]

Oooh, it appears to be, and sure enough it's in the settings page.

In the middle of rebooting the server right now as I disabled the service to close any open files in that dir so I can try and rename it...

Thanks for catching that... will report back shortly...

[scaesare]

BOOM!

That was it... recordings going to the NAS. At some point I must have fat fingered that, although I honestly don't recall having futzed with it after it had successfully used the share, but I must have.

Thank you for helping to identify the issue, which was clearly user error.


At the risk of becoming even more an annoyance... as part of the migration I'm looking to move this server to a new box. An initial look at the docs page didn't show a method to do that... any suggestion or pointers on if that's documented?

[scaesare]

For any other folks that happen to experience this...  you can get in to and manipulate the directory using the object manager namespace:

C:\Program Files\NextPVR>dir "\\?\c:\Program Files\NextPVR\ "
Volume in drive \\?\c: has no label.
Volume Serial Number is 140A-4C91

Directory of \\?\c:\Program Files\NextPVR\

03/06/2024  11:50 AM    <DIR>          .
03/06/2024  11:50 AM    <DIR>          ..
03/06/2024  11:50 AM    <DIR>          192.168.100.2
11/11/2023  11:28 PM    <DIR>          file01
03/05/2024  01:19 PM    <DIR>          nas01
              0 File(s)              0 bytes
              5 Dir(s)  65,238,388,736 bytes free

Sure enough, it interpreted the UNC path share names with the prepended space as subdirectories....

I'll watch the stuff I have in there and then delete it all from within the NextPVR client and then croak the directories....

[mvallevand]

What is interesting to me is the 11/11/2023 folder that corresponds with this thread https://forums.nextpvr.com/showthread.php?tid=65192 where you also had share troubles with \\file01

Martin

[scaesare]

Which was the tuner issues associated with needing to use the HDHR tuner devices. But that is interesting because at that time it was writing to the share on my old file server successfully...

Troubleshooting that may have been the time I fat-fingered the errant space in the path.

When migrating to the new NAS in the last couple of days, I just edited the server name, leaving the rest of the path alone, and as a result that space remained...