Reply to thread

Message

<blockquote data-quote="Owlsroost" data-source="post: 705606" data-attributes="member: 83973">Re: AW: MP1 EVR Presenter/dshowhelper community developmentHi Tourettes,The refresh rate estimator was changed to a version of arion_p's 'linear regression' code back at SVN 26897 (1st Dec 2010). Because this is much more accurate and reliable than my old method I removed the 'find best match to allowed refresh rates' code. That code couldn't differentiate between, for example, 23.976Hz and 24.000Hz, so it reported a compromise refresh rate of 23.988Hz for both.If reporting 'accurate' measured rates to the audio renderer code is causing a problem, I could add back the 'find best match to allowed refresh rates' code - any thoughts ?(Actually, the new refresh rate estimator is probably accurate enough to differentiate between 23.976Hz and 24.000Hz - a 0.1% difference, so the 'best match' code might work better than it used to).Tony</blockquote>

[QUOTE="Owlsroost, post: 705606, member: 83973"] [b]Re: AW: MP1 EVR Presenter/dshowhelper community development[/b] Hi Tourettes, The refresh rate estimator was changed to a version of arion_p's 'linear regression' code back at SVN 26897 (1st Dec 2010). Because this is much more accurate and reliable than my old method I removed the 'find best match to allowed refresh rates' code. That code couldn't differentiate between, for example, 23.976Hz and 24.000Hz, so it reported a compromise refresh rate of 23.988Hz for both. If reporting 'accurate' measured rates to the audio renderer code is causing a problem, I could add back the 'find best match to allowed refresh rates' code - any thoughts ? (Actually, the new refresh rate estimator is probably accurate enough to differentiate between 23.976Hz and 24.000Hz - a 0.1% difference, so the 'best match' code might work better than it used to). Tony [/QUOTE]

Verification