paradise lost... 1.5.31 problems came back

[johnsonx42]

I want to test NRecord without the web server running at all. Disabling the web server in Settings does nothing. What can I do to actually stop it from loading?

[sub]

another edit: is it possible then that NEWA is causing the high cpu utilization? NEWA is the primary difference between the recording service launched by NRecord vs. the one from NextPVR, right? can I tell NRecord to run without NEWA?

Due to a bug, you cant current stop it running the web server, but you could try temporarily removing all the files from c:\users\public\nextpvr\web\* then start nrecord to see if it helps with your CPU.

[johnsonx42]

Thanks sub. I did that, CPU still at 20+%. 'twas worth a try....

[johnsonx42]

The clock remains perfect running without NRecord. So it does seem that whatever NRecord is doing when it runs at high CPU utilization also causes clock drift; I can't explain it, but there it is.

[johnsonx42]

bump, now that you're back sub (yes, I know, you were so looking forward to dealing with my problems again right away)

My clock continues to keep near perfect time as long as I don't run NRecord. As soon as I run NRecord the CPU goes to 20%, the clock runs fast, and playback often freezes after skipping.

I also discovered one other problem I was having is related to this: I'd had a lot of trouble with the comskip auto-skip points being early in a lot of recordings. Running with NextPVR alone I've found that all recordings auto-skip pretty much perfectly. I think what was happening is that the clock was drifting during recording, thus making the Timing.Info drift as it was being generated; so later when skipping based on the Timing.Info, it would skip to the wrong place. Now that I have no clock drift, Timing.Info is spot on as are the comskip auto-skips.

On the down side, running NextPVR.exe for everything all the time I'm running into an apparent memory leak and out of memory error every few days as reported in another thread. And of course I have no NEWA and thus no SearchLite which I seriously miss.

[sub]

If you kill your nrecord.exe service, and instead start it from a command prompt with "nrecord.exe RUN", do you still see this high CPU usage?

It might also be worth temporarily rename npvr.db3, and start the app and setup a capture device from scratch to see if you get the high CPU. If you do, zip and attach your npvr.db3 and I'll try it here.

[johnsonx42]

Thanks sub, I'll give that a try when I get a chance.

[johnsonx42]

Ah, this is weird, it's the NPVR Tray icon that causes NRecord to run at high CPU and do all the other bad things. If I kill the tray icon, NRecord goes back to normal operation. I'll test it for a couple of days without the tray icon to be sure.

[BrettB]

I discovered last weekend that the NPVR Tray application was constantly receiving a "large" amount network data CONSTANTLY from nrecord on my system, too. After I killed all of the NPVR tray applications, my nrecord process went down to no CPU usage while idle, too.

[sub]

I dont see this high CPU here. They do exchange a lot of info, but not enough to account for that high CPU. I wonder if you have firewall/antivirus software that is monitoring the TCP/IP communication between these two processes and generating a lot of CPU doing it?