home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Area 51 - Testing Area
MP1-4100 Rework Refresh Rate when using multi monitor
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Owlsroost" data-source="post: 1017285" data-attributes="member: 83973"><p>I think that scythe42 mentioned something about that (for Win8) a while ago, so it may be a 'feature' of Win8 <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p> </p><p></p><p> </p><p>Do you mean a float (as you had decimal before with the Win32 API) ?</p><p> </p><p>MPAR really needs a very accurate measurement of refresh rate (i.e. the one that EVR presenter estimates), otherwise it can create worse dropped/repeated frames (instead of making it better). So it's better to force MPAR bias to 1.0 (no correction) unless we know for sure that the video is running on the primary monitor (and MP was started there etc.). We need to disable EVR presenter vsync correction for the same reason in the 'no primary' situation as well. Of course this hopefully doesn't apply to Win8 <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p> </p><p>I'm happy to make the changes to dshowhelper (for MPAR and vsync correction control), but I think it might be better for MP C# to handle the 'logic' of this - what do you think ?</p></blockquote><p></p>
[QUOTE="Owlsroost, post: 1017285, member: 83973"] I think that scythe42 mentioned something about that (for Win8) a while ago, so it may be a 'feature' of Win8 :) Do you mean a float (as you had decimal before with the Win32 API) ? MPAR really needs a very accurate measurement of refresh rate (i.e. the one that EVR presenter estimates), otherwise it can create worse dropped/repeated frames (instead of making it better). So it's better to force MPAR bias to 1.0 (no correction) unless we know for sure that the video is running on the primary monitor (and MP was started there etc.). We need to disable EVR presenter vsync correction for the same reason in the 'no primary' situation as well. Of course this hopefully doesn't apply to Win8 :) I'm happy to make the changes to dshowhelper (for MPAR and vsync correction control), but I think it might be better for MP C# to handle the 'logic' of this - what do you think ? [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Area 51 - Testing Area
MP1-4100 Rework Refresh Rate when using multi monitor
Contact us
RSS
Top
Bottom