Reply to thread

Message

<blockquote data-quote="tourettes" data-source="post: 610162" data-attributes="member: 10858">I was planning to answer to you long &quot;rambling&quot; but haven't had any change during the workday (and I might be unavailable whole next week).I think I yet haven't understood completely the algorithm how Reclock behaves (nice to have closed source component with no good documentation <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />).Some quick notes:<ul>
<li data-xf-list-type="ul"> One thing I cannot understand is that how Reclock is able to detect the EOP. </li>
<li data-xf-list-type="ul"> If Reclock only &quot;tries&quot; to drive the SOP by adjusting the reference clock wide enough presentation window should not interfere with Reclock's algorithm.</li>
</ul>But of course that is far from perfect and still quite vulnerable for different issues (two correction algorithms cannot be good, unless they are targeted to correct the faults in each other).My vacation (if flights is possible...) comes into &quot;bad&quot; time, so could you Jong or Owlsroost ask James opinion about the possibility to have a interface in Reclock? Mainly about the idea overall and how he sees it. Interface should just allow1) toggling the v-sync on / off (to reduce registry hack and wrong setting leaved as set if crash occurs)2) Advising reference to speed / slowdown when v-sync is disabled(3) as extra reclock could provide some stats to help rendering in later stages)Just remind him that many MP / MPC-HC etc. users have bough AnyXXX (me included) and more would by if Reclock when it is working nicely together with those players.Implementing the EVR presenter &quot;steering&quot; control for reference clock speedup / slowdown is already ready (ar-jar's genlock code is perfect for this usage).</blockquote>

[QUOTE="tourettes, post: 610162, member: 10858"] I was planning to answer to you long "rambling" but haven't had any change during the workday (and I might be unavailable whole next week). I think I yet haven't understood completely the algorithm how Reclock behaves (nice to have closed source component with no good documentation :)). Some quick notes: [list] [*] One thing I cannot understand is that how Reclock is able to detect the EOP. [*] If Reclock only "tries" to drive the SOP by adjusting the reference clock wide enough presentation window should not interfere with Reclock's algorithm. [/list] But of course that is far from perfect and still quite vulnerable for different issues (two correction algorithms cannot be good, unless they are targeted to correct the faults in each other). My vacation (if flights is possible...) comes into "bad" time, so could you Jong or Owlsroost ask James opinion about the possibility to have a interface in Reclock? Mainly about the idea overall and how he sees it. Interface should just allow 1) toggling the v-sync on / off (to reduce registry hack and wrong setting leaved as set if crash occurs) 2) Advising reference to speed / slowdown when v-sync is disabled (3) as extra reclock could provide some stats to help rendering in later stages) Just remind him that many MP / MPC-HC etc. users have bough AnyXXX (me included) and more would by if Reclock when it is working nicely together with those players. Implementing the EVR presenter "steering" control for reference clock speedup / slowdown is already ready (ar-jar's genlock code is perfect for this usage). [/QUOTE]

Verification