Does v5 support multiple recording directories?

[mvallevand]

None of the above, each separation needs the ~ (tilde) ie.

<ExtraRecordingDirectories>Beast~V:\NextPvr\Beast~Hive~V:\NextPvr\Hive</ExtraRecordingDirectories>

One day hopefully we can some volunteers for the wiki.

Martin

[markn62]

Thanks Martin. I saw one taker. Perhaps I could help out too. I'll keep an eye open for an announcement to the start of that project.

[mvallevand]

Your in luck https://forums.nextpvr.com/showthread.ph...n=lastpost

Martin

[markn62]

Thats the thread I saw. Seems the document framework should be layed out first, to ensure consistent format, then content added within.

[markn62]

Is the plan to copy the v4 manual to v5 GitHub space. Then track and edit the changes in the document needed to represent v5 specifically? Or is the plan to start from scratch.

[sub]

Is the plan to copy the v4 manual to v5 GitHub space.

No - the v4 manual will just stay where it is in pmwiki, as a read only copy, and will receive no further updates.

Then track and edit the changes in the document needed to represent v5 specifically?  Or is the plan to start from scratch.

v5 will be a new wiki based on GitHub and markup, allowing people to fork a copy, make edits, and request their edits be merged back into the master repository etc. Mostly NextPVR v5 is entirely new, and better suited to starting a new wiki. There is a few pages from the old wiki that have useful information that we'll probably copy into the v5 wiki.

[markn62]

I should have also asked, can it be a network drive?

It can, but it'd need to be somewhere accessible from the account the service runs as. By default it runs as 'localsystem', so wont see any drive mappings you've made under your desktop account, so don't use drive letters. Use UNC paths instead NAS~\\server\share~ and make sure that share has permissions that'll allow that account to create and writes files

I tried running as a service instead of as a process. The firewall entries were created ok and the service is running.  Can access the service via browser just as I could as a process.  I changed my default and extra storage directories from a drive letter to a network path, via config.xml, but get error "failed: access to path...is denied" when a schedule tries to record. I ran command prompt as admin from the host box and I can, for example, get a dir \\192.168.2.112\abc\def\  response just fine.  My NAS has read/write permissions for both the user and admin account of the host box.  Is there another trick to making this work?

[mvallevand]

The Admin account is not Local System.

Martin

[markn62]

Can I run the service as other than "Local System" then?  Or how do I determine what the password is for "Local System"?  Thought it was the same as the admin account.
I'll presume it can't run as other than "Local System" and figure out how to set Nas to allow Local System" access.  Seems to be what I'm getting from Google search.

[mvallevand]

Yes if you search this forum before posting you would see that is one solution to the NAS problem. Google, Bing, DDG etc let you search fo general Windows questions. Sorry if that is hard, but I found many people don't bother doing research anymore.

One hint you can use sysinternal tool psecec to log into Local System if you have too. psexec -i -s cmd

Martin