One second recordings

[sub]

=1 creates a netpush.txt
=2 creates a netpush-x.txt

[jcole998]

Thanks for all your help, gentlemen, but I believe I know what's wrong. This was revealed last night when I examined the tuner status on the DCR-3250 web page and found that two tuners were tuned to the same channel with the data going to two different machines. Yuck.

I have two desktops where "A" is the NPVR server and "B" is the client. I occasionally use B to test new software by making it a server at times it won't interfere with A. When I'm switching modes(on either machine), I carefully stop NRecord.exe, start NPVR and change the checkbox under Devices, stop NPVR then restart NRecord.exe. This seems to do the trick. I may have not stopped NRecord.exe during my last mode switch. I changed B's NPVR client checkbox as usual and thought I was done. It seems that NRecord still thought is was in server mode and was connecting to the tuner for all scheduled recordings and, apparently, because B's clock was ahead of A's clock B got there first and blocked A from connecting only after A got one second's worth of data. A's NRecord log showed a normal connection even though B was receiving the data. Apparently NRecord B was not honoring my its client option.

Does this make sense. Did I follow the correct procedure for switching server/client modes? This conflict would certainly interfere with padding overlap I submitted on another thread.

For now, I deleted npvr.db3 on B. NRecord.exe created a new DB automatically but it's empty for now. I tested that B is using only A's DB, not it's own.

I am a little puzzled that A was told that a tuner was available when it really wasn't. I attached logs from both machines for your examination. The actions in question begin at 8pm, 02-06-2016, with "The Flash"(WPIX) and continues into the 9pm hour with "Black Lightening"(WPIX) and "Bull."(WCBS) All programs have one minute pre-/post-padding.

I'll be watching tonight very closely.

I greatly appreciate all your help.

[sub]

If you're doing that, you need to stop the recording service when you're not using.

[jcole998]

I did stop the service last night hoping my morning schedule would be OK. The schedule did not go well and the service was running. Should I rename NRecord.exe?

Will the service be started when I sign in?

[sub]

Windows will auto start the service when you reboot. Just set the service to disabled if you don't want to use it.

[jcole998]

Thanks, sub, but just to be clear:

- The service is not needed for the client to run correctly?
- The service should NEVER access the server DB when in client mode?

[Graham]

Thanks, sub, but just to be clear:

- The service is not needed for the client to run correctly?
- The service should NEVER access the server DB when in client mode?

A NextPVR client does not need the NextPVR Recording Service to be running for any reason ... You need one and only one NextPVR Recording Service to be running.

I use PCIe tuners for everything. All of the tuners are inside one computer. The computer that contains all of the tuners is the only device that needs to run the Recording Service. It's the same for network tuners ... they only need to connect to one Recording Service running in one computer.

[sub]

- The service is not needed for the client to run correctly?

Correct.

- The service should NEVER access the server DB when in client mode?

Correct.

The recording service always accesses it's own database. If you'd been switching the frontend NextPVR.exe between client mode and normal mode, you need to be careful that you haven't scheduled both recording service to be using the same device at the same time. If you're unsure, disabling the recording service on the client machine is a good idea. Even better idea is using a separate tuner for those tests.

[jcole998]

I will change the client service to start manually and change its startup mode as needed.

Thank you all for the good advice.