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="tourettes" data-source="post: 849357" data-attributes="member: 10858"><p>23.976 as 24 is quite big difference, so I'm not sure if the v-sync correction calculations would be able to correct such big difference (in reference clock side the difference is big <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" />). V-sync correction is targeted for example for HW errors like 23.976 as 23.972 (or for case where audio clock is a bit faster / slowed). Which basicly means that the bias control should be accurate as possible, so I would assume that those are way too big differences.</p><p> </p><p>Isn't the video decoder providing proper sample durations that could be used to detect the real incoming rate?</p></blockquote><p></p>
[QUOTE="tourettes, post: 849357, member: 10858"] 23.976 as 24 is quite big difference, so I'm not sure if the v-sync correction calculations would be able to correct such big difference (in reference clock side the difference is big :)). V-sync correction is targeted for example for HW errors like 23.976 as 23.972 (or for case where audio clock is a bit faster / slowed). Which basicly means that the bias control should be accurate as possible, so I would assume that those are way too big differences. Isn't the video decoder providing proper sample durations that could be used to detect the real incoming rate? [/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