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
Development
General Development (no feature request here!)
MediaPortal Audio renderer - better video playback quality
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: 730994" data-attributes="member: 83973"><p>In the 75Hz case, I think it's behaving correctly - the 'Rptd FPS' (which comes from the decode filter/EVR mixer) is 47.952Hz, and the display is 75Hz. </p><p></p><p>75Hz : 47.952Hz isn't close to an integer ratio so the audio correction is disabled.</p><p></p><p>Decode filters/EVR mixer tend to assume the video might be interlaced, so they report 2 x frame rate to allow for de-interlacing. They don't know if the video is actually interlaced until it starts playing, but this is too late for the audio renderer bias calculation. The dshowhelper works around this (for internal use) by calculating the actual frame rate from the stream timestamps, but again this isn't accurate until at least 128 frames have been played (this is the 'Detd FPS' value in the render stats).</p><p></p><p>Tony</p></blockquote><p></p>
[QUOTE="Owlsroost, post: 730994, member: 83973"] In the 75Hz case, I think it's behaving correctly - the 'Rptd FPS' (which comes from the decode filter/EVR mixer) is 47.952Hz, and the display is 75Hz. 75Hz : 47.952Hz isn't close to an integer ratio so the audio correction is disabled. Decode filters/EVR mixer tend to assume the video might be interlaced, so they report 2 x frame rate to allow for de-interlacing. They don't know if the video is actually interlaced until it starts playing, but this is too late for the audio renderer bias calculation. The dshowhelper works around this (for internal use) by calculating the actual frame rate from the stream timestamps, but again this isn't accurate until at least 128 frames have been played (this is the 'Detd FPS' value in the render stats). Tony [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
MediaPortal Audio renderer - better video playback quality
Contact us
RSS
Top
Bottom