GeForce4MX not good enough?

[csy]

The Mediaportal post-processing is unticked (and confirmed ffdshow is not in the graph).

My video card is Legend NV6600GT (Nvidia 6600GT, AGP)
I have also experimented with enabling Nvidia "coolbits" extensions and played with the AGP settings but no difference.

I have also experimented with enabling the PureVideo extensions and played with the DXVA settings but got nowhere.

Edit:
I have just noticed the renderer names are different:
GBPVR is using "Video Renderer" (VMR9) and has all 4 inputs enabled
Mediaportal is using "Video Mixing Renderer 9" with only input0 enabled

[pwborders]

This is all so much fun.

I just found out something interesting, might not be news to anyone else but the "Video Mixing Renderer 9" that is often used it the quartz.dll. You have probably read all the threads about funky quartz.dll issues including jerky playback.

CSY:

Have you tried the sysenum.exe that comes with graphedit to see what actual files are being used by mediaportal. It will list under Directshow Filters the video renderers installed and if you select one it shows the actual file name and location at the bottom. That might be a way to tell what Mediaportal has registered and maybe then we can get gbpvr to use that one.

I tried the alternate vmr9 listed in gbpvr's config and that worked prety badly on my FX5200. I am going to try my ATI card this weekend just to see if I can get a good picture out of this thing. Its a good thing I got used to video from overused vhs tapes or I might be more picky.

One strange thing I just noticed is that windows media player won't play my recordings anymore. The only things I have changed are upgrading the purevideo codec and installing graphedit. I have the purevideo codec set to the preferred codec with MS deccheck. Is there an issue with the new purevideo codec and wmp9 or wmp10 (I have to check and see which it is)?

[csy]

Sub,

I've found the PureVideo decoder says:
"DXVA mode A" to the Nvidia video card (jumpy motion)
"DXVA mode C" to the ATI video card (smooth motion)

Do you know what this means, and do you think this is related to the motion problem on the Nvidia video card when DXVA is enabled?
Do you know if there is a way to force the DXVA mode?

[sub]

No, I dont know how it is changed. GB-PVR isnt directly aware of DXVA.

[csy]

pwborders;

sysenum shows:
Mediaportal "Video Mixing Render 9" is using quartz.dll in the system32 directory.
GBPVR "Video Render" is using the same quartz.dll in the system32 directory.
The only difference is they appear to be using a different VMR9 mode.

Note my DXVA finding (in the above posting) when swapping between Nvidia and ATI video cards.

WRT PureVideo and WMP10, I find it works but note that WMP uses VMR7 by default. You can change the default renderer by changing the renderer filter merit. I did this to see if WMP10 produced the same result as GBPVR with "video renderer" (version 9), which it does. Then I changed the merit to make "Video Mixing Renderer 9" the default and tried again, but still jumpy motion. I confirmed the default renderer was actually changing by testing with Graphedit.

I now suspect the jumpy motion is not related to the renderer, particularily noting the fact that DXVA mode is different on ATI video cards.

I wish I knew what I was doing

[pwborders]

CSY:

" I wish I knew what I was doing " <- See what I mean about fun.

Well I at least got my media player working again. The register bat that came with my graphedit registered something that media player didn't like. Even graphedit itself wouldn't render the recordings, it just disappeared. After unregistering what it registered now thing work again.

Interesting about the different DXVA modes used. I will have to investigate further.

[pwborders]

Hey I just improved something.

A long time ago I had replaced quartz.dll ut somewhere along the line I think it got updated on me. So I just downgraded it back to one of the old ones that is supposed to work and it seems to work quite well.

During this testing I had been using quartz.dll 6.5.2600.2749 which is 1,287,680 bytes in size. The old one I thought I was using and just switched back to is 6.05.01.0902 and is 1,962,496 bytes in size but it sure seems to work better. There is a newer version that I will try tommorrow that is between these too that is supposed to fix this as well.

The biggest problem with testing this is finding something that shows the problem well. I have one recording that has one section that is pretty bad. Has anyone found a sure thing to show this issue?

[csy]

The issue with quartz.dll only relates to first release DirectX9c and BOB deinterlacing as per Microsoft:
http://support.microsoft.com/default.asp...-us;885354
Microsoft released a DirectX9c fix (quartz.dll 6.5.2600.2508) but this was difficult to obtain from Microsoft so most people rolled back to DirectX9b quartz.dll 6.05.01.0902. WinXP SP2 has quartz.dll 6.5.2600.2749 which appearantly has incorporated the .2508 fix.

The fix relates to the fact that software-based BOB deinterlacing doubles the frame-rate to the renderer, therefore the renderer (quartz.dll) can loose track of frame numbering. This particularily shows up after FF/RW resulting in very bad studdering. I dont use BOB deinterlacing (I use VMR pixel adaptive), therefore have never noticed this issue.

[csy]

I have discovered that decreasing the PureVideo quality setting to minimum, reduces the jumpy motion significantly without greatly impacting the picture quality.

You need to enable the hidden PureVideo property tabs by adding the following registry settings
[HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Filters\Video]
"EnablePropPage"=dword:00000001
"PureVideoPropPage"=dword:00000001

Then go into the PureVideo properties and select the Control tab, and reduce the Quality slider to the minimum value (far left).

[csy]

It looks like we are not the only ones experiencing these problems.
http://www.avsforum.com/avs-vb/showthrea...ost7445979
http://www.xpmediacentre.com.au/communit...utter.html

It might be PAL related and Nvidia are aware of the problem according to the above links.
I am using PAL.
pwborders - are you NTSC or PAL?