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="davidf" data-source="post: 662871" data-attributes="member: 19484"><p>You shouldn't need to take anything else into account - the errors will cancel each other out (or will once you figure out why EVR is trying to compensate for your clock correction). I had done the tossing a coin explanation - but deleted it. Just think about tossing a coin 10 million times with head a positive error and tails a negative error. It certainly would do no harm to correct it if you can though. You'd need to add log info about it as there's nothing I could use to estimate in the current logs. The only thing I can tell you is that in the * one there were 2 (long) uses of the adjustment and in the / one there were 24 (short) uses.</p><p></p><p>The thing to worry about is why the small correction is causing EVR to try and correct it's sync in the opposite direction, as I said you could adjust the audio speed by mult (same arguments for * and / <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" />) which wouldn't be detectable by EVR and would produce the same results.</p><p></p><p></p><p>I'll have to go and see if any of my machines has IIS installed as the excel sheet is rather large.</p><p></p><p>Actually thinking about it then the mult makes sense as it made the adjustments at the beginning and then stopped (I've had to page through the thing to find that out). Div doesn't as it had to constantly readjust as it was drifting out (or thought it was). Guess that tells you which one is correct. Would be interesting to know what the numbers would be if you ignore the AV drift in the clock.</p><p></p><p></p><p></p><p>I wasn't thinking of blaming him - I was interested in the effect, and I'm betting that he has played with the code and seen the same effects.</p></blockquote><p></p>
[QUOTE="davidf, post: 662871, member: 19484"] You shouldn't need to take anything else into account - the errors will cancel each other out (or will once you figure out why EVR is trying to compensate for your clock correction). I had done the tossing a coin explanation - but deleted it. Just think about tossing a coin 10 million times with head a positive error and tails a negative error. It certainly would do no harm to correct it if you can though. You'd need to add log info about it as there's nothing I could use to estimate in the current logs. The only thing I can tell you is that in the * one there were 2 (long) uses of the adjustment and in the / one there were 24 (short) uses. The thing to worry about is why the small correction is causing EVR to try and correct it's sync in the opposite direction, as I said you could adjust the audio speed by mult (same arguments for * and / :-)) which wouldn't be detectable by EVR and would produce the same results. I'll have to go and see if any of my machines has IIS installed as the excel sheet is rather large. Actually thinking about it then the mult makes sense as it made the adjustments at the beginning and then stopped (I've had to page through the thing to find that out). Div doesn't as it had to constantly readjust as it was drifting out (or thought it was). Guess that tells you which one is correct. Would be interesting to know what the numbers would be if you ignore the AV drift in the clock. I wasn't thinking of blaming him - I was interested in the effect, and I'm betting that he has played with the code and seen the same effects. [/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