Test/Development environment for npvr.db3

[scJohn]

In production the  npvr database is located at:
"D:\Users\Public\NPVR\npvr.db3"

I have a test/development npvr database located at:
"D:\Users\johni\Projects\graphql-knex-npvr\NPVR\npvr.db3"

Is it possible to point "C:\Program Files (x86)\NPVR\NextPVR.exe" to use the test npvr.db3.  I came across some docs for the command line parameters for NetPVR.exe  but did not need see anything for overriding the production npvr.db3 file.


What is the best practice to set up a development environment so that I don't screw up the production version?

Version 4.

Thanks

[sub]

In v4, you can set an HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\NPVR\DataDirectory registry setting pointing to a another data directory, which could include a different npvr.db3 file etc.

In reality, it kind of makes no sense having the front end software pointing at a different npvr.db3 than the server though. ie, wont be able to schedule recordings etc.

[mvallevand]

In v4, you can set an HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\NPVR\DataDirectory registry setting pointing to a another data directory, which could include a different npvr.db3 file etc.

In reality, it kind of makes no sense having the front end software pointing at a different npvr.db3 than the server though. ie, wont be able to schedule recordings etc.

The registry setting would also impact the production and dev version, it would be just as easy and maybe safer to rename folder.

If you move to v5, really not sure what's holding you back, you can use an environment variable specific to your setup.

Martin

[BrettB]

In v4, you can set an HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\NPVR\DataDirectory registry setting pointing to a another data directory, which could include a different npvr.db3 file etc.

In reality, it kind of makes no sense having the front end software pointing at a different npvr.db3 than the server though. ie, wont be able to schedule recordings etc.

The registry setting would also impact the production and dev version, it would be just as easy and maybe safer to rename folder.

If you move to v5, really not sure what's holding you back, you can use an environment variable specific to your setup.

Martin

I think that maybe what the OP is asking about is really just having both v4 (his production) and v5 (his test) installed on the system at the same time.

If that is the case, then both versions (by default) use different folders for both their program files and their data files, so they can co-exist easily. The only catch is that (again by default) they both use the same port. But you can easily shutdown v4, install v5, shutdown v5, change v5's config.xml to use a different port, then restart both v4 and v5.

[scJohn]

........

In reality, it kind of makes no sense having the front end software pointing at a different npvr.db3 than the server though. ie, wont be able to schedule recordings etc.

This is exactly the testing I am trying to do: record once and recurring .  

Renaming folder option is interesting.  I could just add 2 scripts to my package.josn file.   One to copy the files in NPVR  to a safe place before testing and the other to  restore those same file after testing.  

There is also that can of worms for the wake timers in powercfg to wake the up and record the event

[mvallevand]

As soon as you stop a server I am pretty sure the wake timers for that database will stop.

I script like this run as admin should work but you have to create Production first and change your release folder so the script works

Code:

net stop "npvr recording service"
if not exists  "D:\Users\johni\Projects\graphql-knex-npvr\NPVR\"  goto production
ren "D:\Users\Public\NPVR\" "D:\Users\Public\NPVR\Production\"
ren "D:\Users\johni\Projects\graphql-knex-npvr\NPVR\" "D:\Users\Public\NPVR\"
goto restart
:production
ren "D:\Users\Public\NPVR\" "D:\Users\johni\Projects\graphql-knex-npvr\NPVR\"
ren "D:\Users\Public\NPVR\Production\" "D:\Users\Public\NPVR\"
:restart
net start "npvr recording service"

Martin

[scJohn]

Running the command: NextPVR.exe --recurring is suppose to re-schedule recurring programs using current EPG data. Looking at the log, the only hint that this done is:

2020-09-03 17:17:00.597 [DEBUG][1] Version: 4.2.4.190307
2020-09-03 17:17:00.597 [DEBUG][1] SingleInstance()
2020-09-03 17:17:00.837 [INFO][1] About to connect to remote recording service
2020-09-03 17:17:00.845 [DEBUG][1] RecordingServiceProxy@exit
2020-09-03 17:17:00.846 [DEBUG][1] Rendering for screen size: 1920x1080

There is nothing obvious like when looking at the nrecord log when the EPG is updated. Or is it I don't see anything in the NPVR log because there was no changes to process.

How are 'record once' determined because they are not in the RECURRING_RECORDING table but in the SCHEDULED_RECORDING table.

Unfortunately when using -- recurring, NextPVR does not exit like when running with -updateepgonly.

[mvallevand]

Did you try with the documented syntax -recurring (single dash)?

Martin

[BrettB]

How are 'record once' determined because they are not in the RECURRING_RECORDING table but in the SCHEDULED_RECORDING table.

One-off (i.e. 'record once') recordings are only stored in the SCHEDULED_RECORDING table. They get put in there when you select to record them. And they stay there until they get deleted. What are you expecting???

[mvallevand]

Missed that it is (also including in progress) one offs

With the JSON API the absence of these fields are one-offs.

"recurring": true,
"recurringParent": 495

If your are using the .NET API check ScheduledRecording.RecurrenceOID

If you use the database it would be

Code:

select * from scheduled_recording
where status = 1 or status = 3
and recurrence_oid=0

Martin