@ tetsuo
Just an idea : I think it will be better that you to start a new MPC-HC thread and put the "Troubleshooting_guidelines" ( and Bugs Reporting ?) on the first page cause this one it's already too big and the most part of it contains old / irrelevant info for the current version

Ok, what about the renderer settings, which settings make the eye sore problem go away

Well, I realized that both the earlier and current versions of MPC have somewhat rough playback that is hard on my eyes.

However, when I enable "lock back buffer" in 908, it all becomes perfectly smooth. But no combination of the gpu settings for the newer builds can fix the video as well as back buffer setting. So, I believe reintroducing this function could solve my problem.

@ tetsuo
Just an idea : I think it will be better that you to start a new MPC-HC thread and put the "Troubleshooting_guidelines" ( and Bugs Reporting ?) on the first page cause this one it's already to big and the most part of it contains old / irrelevant info for the current version

thats a good idea, i will contact xxl

Quote:

Originally Posted by snyders6dogrecipe

Well, I realized that both the earlier and current versions of MPC have somewhat rough playback that is hard on my eyes.

However, when I enable "lock back buffer" in 908, it all becomes perfectly smooth. But no combination of the gpu settings for the newer builds can fix the video as well as back buffer setting. So, I believe reintroducing this function could solve my problem.

I don't know if it is already posted but I've a problem with g45 in my ACER laptop(Timeline Travelmate 8471) and DXVA on Windows 7 x64: sometimes (every 5 min) in various video, a series of frame are corrupted with negative colors artifacts in the entire video scenes...the driver that I've installed are the 8.15.10.1892.

I think that it would be a driver problem or MPC-HC issue...I tried both x86 than x64 version and the problem is the same...

I don't know if it is already posted but I've a problem with g45 in my ACER laptop(Timeline Travelmate 8471) and DXVA on Windows 7 x64: sometimes (every 5 min) in various video, a series of frame are corrupted with negative colors artifacts in the entire video scenes...the driver that I've installed are the 8.15.10.1892.

I think that it would be a driver problem or MPC-HC issue...I tried both x86 than x64 version and the problem is the same...

The MPC-HC versions tested are 1249 and 1345 svn x86 and x64.

Thanks in advance

Try to disable the internal H.264 filters (both DXVA and software) to let Windows 7's built-in DXVA decoder do the decoding... Then you'll be able to check if it's a problem w/ the internal filter OR a driver problem...

Try to disable the internal H.264 filters (both DXVA and software) to let Windows 7's built-in DXVA decoder do the decoding... Then you'll be able to check if it's a problem w/ the internal filter OR a driver problem...

With Windows 7 built-in DXVA there is no prob: so I think that this is a MPC-HC internal filter issue...

When I ticked "sync video to display," there was still some tearing, and the initial problem didn't go away. I couldn't try the other options because I can't use powerstrip with my video card, and also because if I enable evr renderer I can't use dxva.

Edit: OK, DXVA DOES work with EVR Custom Renderer and it makes the tearing go away. But the dynamic range is wrong and I can't fix it using Nvidia's Control Panel or the player's controls- and the initial problem is still there, unfortunately.

Have you turned on the stats graph? While a video is running, right-click on the screen, at the bottom is "Renderer Settings", then enable "Display Stats".

This will show you what the rendered frame rate is, and show a graph. If the lines are flat, everything is fine and the framerate matches the video.

However, when the video has to resync you will see a spike.

I've noticed that for a while, 3:2 pulldown wasn't working right, and by enabling "Display Stats" I saw a large spike at a regular interval, every 3 or 4 seconds or so. I was then able to understand my problem a little bit better.

i just tried to encode interlaced material (a mpeg-2 and a h264 sample) with x264 (rev1342). output is also interlaced, Mediainfo shows Scan type: MBAFF , but MPC-HC with DXVA fails to deinterlace the video completely. did i do a mistake while setting up the Avisynth-script(the script contains only DirectShowSource(clip) .... )/encoding or MPC-HC doesnt support interlaced material created with x264?
with ffdshow hardware-deinterlacing will work perfectly if i set up in the "Output" settings of ffdshow the "field order" as "top field first". on "Auto" i get erratic frame-display.

i just tried to encode interlaced material (a mpeg-2 and a h264 sample) with x264 (rev1342). output is also interlaced, Mediainfo shows Scan type: MBAFF , but MPC-HC with DXVA fails to deinterlace the video completely. did i do a mistake while setting up the Avisynth-script(the script contains only DirectShowSource(clip) .... )/encoding or MPC-HC doesnt support interlaced material created with x264?
with ffdshow hardware-deinterlacing will work perfectly if i set up in the "Output" settings of ffdshow the "field order" as "top field first". on "Auto" i get erratic frame-display.

I don't know if it is already posted but I've a problem with g45 in my ACER laptop(Timeline Travelmate 8471) and DXVA on Windows 7 x64: sometimes (every 5 min) in various video, a series of frame are corrupted with negative colors artifacts in the entire video scenes...the driver that I've installed are the 8.15.10.1892.

I think that it would be a driver problem or MPC-HC issue...I tried both x86 than x64 version and the problem is the same...

When I ticked "sync video to display," there was still some tearing, and the initial problem didn't go away. I couldn't try the other options because I can't use powerstrip with my video card, and also because if I enable evr renderer I can't use dxva.

Edit: OK, DXVA DOES work with EVR Custom Renderer and it makes the tearing go away. But the dynamic range is wrong and I can't fix it using Nvidia's Control Panel or the player's controls- and the initial problem is still there, unfortunately.

Dynamic range settings are also in the renderer settings section of the options, set it to 16-235 or 0-255 to match your display