Any success in using NPVR simultaneously with a capture program on the same computer?

[sub]

Hey sub, since you are here, is there any way I could select which CPU core the NPVR recording service will run on? I try that from the Windows XP Task Manager and get a "This operation can not be completed. Access denied."

I don't know. I never mess around with priorities or affinity etc. I prefer my processes to all run at standard priority and on all available processor cores.

[christheman]

That's okay, it probably explains why Windows just throws up an error. It's probably a bit esoteric for a lot of programmers, as many of the other programs I use don't look like they support that either. I will look around as I have time, there might be a few other tricks. A fast-response process management tool might be in order here. Something to slow down a new recording process in the initial moments as it starts up, or any other process for that matter.

[christheman]

Okay, for whomever may still be following this, I believe that I have come up with a fix. The program I was thinking of before, Outertech Cacheman, seems to be able to fix it. This is a paid program with a free 30 day trial, which costs about $29 US. There may be other programs which might be able to accomplish the same thing, maybe even for free, but this is one I already knew of.

I used all the default settings, including the Simple Profile/Basic Optimization (This program takes over and improves upon some of the Windows management operations). In addition, all the running Windows XP Taskbar processes are represented under the Sticky Priority tab. Any changes made here will immediately happen, and will remain after the program is reset or the machine rebooted.

With it I was able to downgrade all non-essential process priorities which were higher than "Normal", even a couple Windows processes which didn't need to be "High" priority. I also changed to "High" priority both "Nrecord.exe" and "TMShowbiz.exe" (Arcsoft capture module used with Hauppauge HD-PVR).

So that leaves all other programs I could find under Task Manager running either at "Normal" or "BelowNormal". That of course results in everything else on the system opening more slowly, which I believe to be a fair tradeoff.

So this approach does seem to fix the pixelation problem that occurs when I start or stop one capture program while running the other. I tested this a few times, and both ways, and it seems to work flawlessly.