NVidia Decoder performance issue in GB-PVR

[wtg]

I forgot to add... I'm wondering if it's the combo of GB-PVR Parser and the NVidia decoder that accounts for the fact that sometimes it stutters, and sometimes it doesn't.

While it's CPU use has always been higher than I thought it should when used with GB-PVR, I've tried to use it since it makes a nice picture. However, occasionally it would stutter and I wasn't able to figure out why. Perhaps it was when I was trying to watch an in-progress recording, or the bug that I'm claiming to have seen last night... choosing the GB-PVR parser for a recording even when it shouldn't have.

In any event, I'm hoping with some more testing we can narrow it down.

[sub]

Notice too that I get no sizable peak at all in the graph graphedit comes up with on it's own with the NVidia decoder, and the difference there is the GB-PVR Flow Status filter.

I'm confident your spiking is not related to the GBPVR Flow Status filter. This is filter does virtually nothing, simply getting a chance to look at the data as it goes by. Its actually a renamed version of the Microsoft 'null in place' transform filter. I got no spiking at all with GBPVR Flow Status being used.

You cant do this in the current release, but I've made a small change for the next release that will let you run without this filter to give you peace of mind that it is not the cause.

I tried a large number of combinations this morning attempting to reproduce the CPU usage you're seeing, including manually crafted graphs, graphs generated by GB-PVR, existing recordings vs in-progress recordings, and my results were pretty much the same at all times.

[wtg]

As usual you're putting more time into this than most would reasonably assume. I certainly appreciate your efforts, and I'll post back with my results later this evening.