New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MPC Video Renderer - interlaced hdtv content is jerky #631
Comments
Upload short sample, show MPC VR options and full screen screenshot with statistics. |
@Aleksoid1978 Where to find this option? |
@Aleksoid1978 Anyways, so here is a sample, have fun with it. ;) |
You can press Ctrl+J to toggle statistics overlay. |
Thank you. So I updated the link above. And what I already can see in the statistics is, that it is saying Presentation:Discard for the MPC-VR one. |
That is normal. It isn't dropping frames if you think that. |
No, thought about deinterlacing. |
For me is normal, smooth playback.
|
@Aleksoid1978 So tried this morning again and first I couldn't see the difference myself... but it is still somewhat dark outside. @clsid2 Have you tried it? I will stick to the others but I guess I always will be free to select the renderer I like most. For me it is the EVR, no fancy gimmicks I don't need, just works for me. MadVR is also smooth, although it is to complicated for my taste and knowledge. I also stick to the k-lite CP Standard defaults. |
I don't notice any difference. But my monitor is only 60Hz and yours is 144Hz. I see in your statistics screenshot that the green line is "flatter" for EVRCP than MPCVR. So smoother. Here the graphs are similar (saw tooth pattern). |
@clsid2 So I changed the refresh rate of my monitor to 60Hz and the green line for MPC-VR changes too, now one smaller spike and then one bigger spike, for EVR it stays totally the same. I then went into render settings for EVR and activated VSync. Now those lines look not so good anymore, but the video is still smoother, so I don't know, if this is really related. As a noob I would guess, that it is just another (in my opinion not so good) deinterlacer, which is used by MPC-VR. |
The deinterlacer should be the same afaik. Both use hardware deinterlacer from your GPU. |
Too bad that it is closed, it is not resolved. |
It is not a bug in MPC-HC, so there is nothing I can do. |
I just read that the MPC Video Renderer will be the default renderer on most systems.
I did an update to the K-Lite Codec Pack on my system and thankfully it isn't the default yet.
Now to my problem with it, interlaced hdtv content is jerky forever now on my system with the MPC Video Renderer. No problems with the other renderers.
MPC Video Renderer 0.4.10.1466 (git-2020.09.10-9ff2213) x64 Windows 10 DirectX 9 Graphics adapter: NVIDIA GeForce GTX 1070 (10DE:1B81) VideoProcessor : DXVA2 {6CB69578-7617-4637-91E5-1C02DB810285} DeinterlaceTech.: PixelAdaptive ReferenceSamples: Backward 0, Forward 0 Display: XB270HU 2560x1440 144.003 Hz [Primary] windowed
Filter : LAV Video Decoder - CLSID : {EE30215D-164F-4A92-A4EB-9D4C13390F9F}
CLSID: {B98D13E7-55DB-4385-A33D-09FD1BA26338}
Filter: LAV Splitter Source
Pin: Video
Video: MPEG4 Video (H264) 1920x1080 25fps
AM_MEDIA_TYPE:
majortype: MEDIATYPE_Video {73646976-0000-0010-8000-00AA00389B71}
subtype: Unknown GUID Name {31435641-0000-0010-8000-00AA00389B71}
formattype: FORMAT_MPEG2_VIDEO {E06D80E3-DB46-11CF-B4D1-00805F6CBBEA}
bFixedSizeSamples: 0
bTemporalCompression: 1
lSampleSize: 1
cbFormat: 168
VIDEOINFOHEADER:
rcSource: (0,0)-(1920,1080)
rcTarget: (0,0)-(1920,1080)
dwBitRate: 0
dwBitErrorRate: 0
AvgTimePerFrame: 400000
VIDEOINFOHEADER2:
dwInterlaceFlags: 0x00000000
dwCopyProtectFlags: 0x00000000
dwPictAspectRatioX: 16
dwPictAspectRatioY: 9
dwControlFlags: 0x00000000
dwReserved2: 0x00000000
MPEG2VIDEOINFO:
dwStartTimeCode: 0
cbSequenceHeader: 36
dwProfile: 0x00000064
dwLevel: 0x00000028
dwFlags: 0x00000004
BITMAPINFOHEADER:
biSize: 40
biWidth: 1920
biHeight: 1080
biPlanes: 1
biBitCount: 12
biCompression: AVC1
biSizeImage: 3110400
biXPelsPerMeter: 0
biYPelsPerMeter: 0
biClrUsed: 0
biClrImportant: 0
The text was updated successfully, but these errors were encountered: