POPPUR爱换

标题: MPC-HC Sync Renderer(同步渲染器)设置指南 [打印本页]

作者: Edison    时间: 2010-2-7 13:17
标题: MPC-HC Sync Renderer(同步渲染器)设置指南
http://www.ostrogothia.com/?page_id=1216

Published by Arto Jarvinen on 24 Jul 2009 at 08:54 am

                        Get started                                                       
These instructions apply to MPC-HC build 1465 and later.Alternative 1: Synchronize video frame rate to display refresh rate
This is the alternative to try first if you have matching video – display rates and don’t watch a lot of TV (or camera feeds or other more esoteric live sources). It should work with all displays and graphics cards. If using SPDIF (digital) audio output from the computer, this method may cause video and audio to get slightly out of sync during a full lenght movie. For accurate sync between audio and video, analog output should thus be used from the audio renderer. (See this blog post.)
Sync options dialog.

This sync mode uses the display refresh rate as the master and adjusts video and sound speed to the display refresh rate. It is important that the rate difference between the media and the display is small. If it gets larger than about 0.5%, then the audio will 【请注意文明用词】 of sync, even if the video may stay in sync with large control parameters (see below).Alternative 2: Synchronize display refresh rate to video frame rate
This is the more theoretically correct synchronization alternative and mimics the way a regular TV display is synchronized to the incoming video (or at least was in the good old analog age). It also works for live sources such as TV. The drawback with this method is that it may not work for your graphics card – display – display resolution combination. Some experimentation is required. This alternative requires the PowerStrip application.
When this alternative is selected, the Sync Renderer uses PowerStrip to fine-tune the graphics adapter output refresh rate so as to keep it in sync with the frame rate of the incoming video. To accomplish this it adds or removes (invisible) columns or lines to the front porch of the video frame (image) as needed. Adding columns or lines reduces the effective frame rate if the time to display each pixel (determined by the pixelclock) is kept constant. Removing columns or lines similarly increases the frame rate.
Displays such as projectors or LCD TVs tolerate a certain amount of change in the frame rate. Some displays are more tolerant to changes to the number of columns whereas others are more tolerant to changes in the number of lines. The best way to adjust the frame rate must be experimentally determined in the following way:
PowerStrip preferences.

This synchronization alternative has been tested with my own player, the GothPlayer, with various NVidia 5000, 6000 and 7000 series graphics cards (PowerStrip is currently not compatible with the 8000 and up series cards) and the ATI 3450. There are also reports stating that PowerStrip works with the 4000 series of ATI / AMD cards. (See this post at the PowerStrip forum.) PowerStrip needs to be able to adjust the timing parameters of the graphics card to enable Sync Renderer to alter the refresh rate. Go to EntecTaiwan Forums and click your way to PowerStrip for Windows -> Announcements: Latest PowerStrip release notes to find a list of formally supported graphics cards. A “Yes” in column “Timing” is required for the synchronization feature to work.
The display synchronization function has been tested (again with GothPlayer) with four different HDTV displays, all with a 720 lines native resolution. Some issues have been reported with 1080 lines displays.Alternative 3: Present at nearest vsync
This alternative is for those who wish to use SPDIF out instead of analog signals (sync alternative 1 won’t work) and don’t have a display and a graphics board compatible with PowerStrip (sync alternative 2 won’t work) or simply can’t match the display rate to the video rate because if display limitations. It also works well in combination with ReClock.
This sync alternative attempts to minimize the ill effects of poor sync by (1) always presenting a new frame to the graphics board a certain distance from the vsync to avoid tearing and (2) by “snapping” to the closest vsync for as long as possible. A common cause of visible judder is that a frame’s nominal presentation time is exactly at the start of the vsync. Because of inherent imprecision in the video presentation code, sometimes such frames will be presented right before a vsync and sometimes right after a vsync which means that the frames will not be presented with even intervals. This in turn results in judder as shown in the image below.
Inevitable judder when presentation time is close to vsync and no sync correction is active. This judder was induced by playing a 25 fps movie with a 50.01 Hz display refresh rate.

When turning on the Present at nearest vsync synchronization option, the judder is reduced to one “clean” glitch as shown in the image below.
When the Present at nearest vsync is active, there is only one “clean” glitch at vsync. The sync correction keeps the presentation time away from the vsync at all times and lets it only move a full vsync period back or forth when needed, not continuously as in teh graph above. In this case we need to show one video frame one extra display cycle now and then to stay in sync why the vsync period gets longer in that “glitch”.

To activate this sync option do the following:
作者: iamspy    时间: 2010-2-7 13:35
本帖最后由 iamspy 于 2010-2-7 13:39 编辑

试了。没啥感觉。
作者: godlike    时间: 2010-2-7 15:34
madvr用惯了,今天试了下haali看dvdrip,差了好多
作者: Edison    时间: 2010-2-7 15:37
Sync Renderer 是基于 EVR CP 的,和 Haali renderer 两码事。
作者: crossky    时间: 2010-2-25 15:53
汗,全E文,又得费时间慢慢看了
作者: Asuka    时间: 2010-2-25 16:08
收藏了,此帖翻译下应该进精华区
作者: godlike    时间: 2010-4-16 13:39
我100HZ桌面的怎么用呢
作者: 380    时间: 2010-4-16 13:51
提示: 作者被禁止或删除 内容自动屏蔽
作者: ruready    时间: 2010-4-16 19:45
技术帖要mark
作者: eternal0    时间: 2010-4-18 08:44
模式2:同步显示到视频效果最完美,但是碰到VFR的片子大家都萎掉了
作者: naage    时间: 2010-4-18 08:45
全英文的怎么看啊




欢迎光临 POPPUR爱换 (https://we.poppur.com/) Powered by Discuz! X3.4