Reply to thread

Message

<blockquote data-quote="tourettes" data-source="post: 661532" data-attributes="member: 10858">Just wondering about how to detect the A/V sync drifting (we must assume that the EVR presenter itself is not causing any drifting... otherwise it will get too complex - but the dropped frames should make the piling up of the error impossible).Would following give use the required debug info?[code]if (m_dStartQpcHW == 0)&nbsp; &nbsp; &nbsp; m_dStartQpcHW = hwQpc;&nbsp; &nbsp; if (m_dStartTimeHW == 0)&nbsp; &nbsp; &nbsp; m_dStartTimeHW = hwClock;&nbsp; &nbsp; if (m_dStartTimeSystem == 0)&nbsp; &nbsp; &nbsp; m_dStartTimeSystem = dwTime;&nbsp; &nbsp; if (m_dStartTimeCorrected == 0)&nbsp; &nbsp; &nbsp; m_dStartTimeCorrected = m_rtPrivateTime;&nbsp; &nbsp; m_dDurationHW = (hwClock - m_dStartTimeHW) / 10000;&nbsp; &nbsp; m_dDurationSystem = (dwTime - m_dStartTimeSystem); &nbsp; &nbsp; m_dDurationCorrected = (m_rtPrivateTime - m_dStartTimeCorrected) / 10000;&nbsp; &nbsp; //Log(&quot;hw: %I64d sys: %I64d cor: %I64d hwsy: %I64d hwcor: %I64d&quot;, m_dDurationHW, m_dDurationSystem, m_dDurationCorrected, m_dDurationHW - m_dDurationSystem, m_dDurationHW - m_dDurationCorrected);&nbsp; &nbsp; if (m_dPrevTimeHW &gt; hwClock)&nbsp; &nbsp; {&nbsp; &nbsp; &nbsp; m_dStartTimeHW = m_dPrevTimeHW = hwClock;&nbsp; &nbsp; &nbsp; m_dStartQpcHW = m_dPrevQpcHW = hwQpc;&nbsp; &nbsp; &nbsp; m_dStartTimeSystem = dwTime;&nbsp; &nbsp; &nbsp; m_dStartTimeCorrected = m_rtPrivateTime;&nbsp; &nbsp; }[/code][code]void CSyncClock::GetClockData(CLOCKDATA *pClockData){&nbsp; // pointer is validated already in CMPAudioRenderer&nbsp; pClockData-&gt;driftMultiplier = m_dSystemClockMultiplier;&nbsp; pClockData-&gt;driftHWvsSystem = m_dDurationHW - m_dDurationSystem;&nbsp; pClockData-&gt;driftHWvsCorrected = m_dDurationHW - m_dDurationCorrected / m_dBias;}[/code]driftHWvsSystem&nbsp; &lt;-- drift in this should be constantly going into up or down, with the speed of the driftMultiplier. If that happens the correction should be working ok.driftHWvsCorrected&nbsp; &lt;-- this should be quite static? If this increases or decreases it should tell us that the A/V sync is failing apart? Of course it wont take the bias into account. Also the adjustment might falsely cause drifting (or it could even cause real drifting).Are those assumptions valid? Or should we use something else to compute the real A/V sync drifting? I really cannot sit in the front of TV / monitor for months to watch the A/V sync slowly getting out of the drift and then make a single code line change after 2 hours have passed (to be able to detect the sync drifting) <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite7" alt=":p" title="Stick Out Tongue&nbsp; &nbsp; :p" loading="lazy" data-shortname=":p" /></blockquote>

[QUOTE="tourettes, post: 661532, member: 10858"] Just wondering about how to detect the A/V sync drifting (we must assume that the EVR presenter itself is not causing any drifting... otherwise it will get too complex - but the dropped frames should make the piling up of the error impossible). Would following give use the required debug info? [code] if (m_dStartQpcHW == 0) m_dStartQpcHW = hwQpc; if (m_dStartTimeHW == 0) m_dStartTimeHW = hwClock; if (m_dStartTimeSystem == 0) m_dStartTimeSystem = dwTime; if (m_dStartTimeCorrected == 0) m_dStartTimeCorrected = m_rtPrivateTime; m_dDurationHW = (hwClock - m_dStartTimeHW) / 10000; m_dDurationSystem = (dwTime - m_dStartTimeSystem); m_dDurationCorrected = (m_rtPrivateTime - m_dStartTimeCorrected) / 10000; //Log("hw: %I64d sys: %I64d cor: %I64d hwsy: %I64d hwcor: %I64d", m_dDurationHW, m_dDurationSystem, m_dDurationCorrected, m_dDurationHW - m_dDurationSystem, m_dDurationHW - m_dDurationCorrected); if (m_dPrevTimeHW > hwClock) { m_dStartTimeHW = m_dPrevTimeHW = hwClock; m_dStartQpcHW = m_dPrevQpcHW = hwQpc; m_dStartTimeSystem = dwTime; m_dStartTimeCorrected = m_rtPrivateTime; } [/code] [code] void CSyncClock::GetClockData(CLOCKDATA *pClockData) { // pointer is validated already in CMPAudioRenderer pClockData->driftMultiplier = m_dSystemClockMultiplier; pClockData->driftHWvsSystem = m_dDurationHW - m_dDurationSystem; pClockData->driftHWvsCorrected = m_dDurationHW - m_dDurationCorrected / m_dBias; } [/code] [b]driftHWvsSystem[/b] <-- drift in this should be constantly going into up or down, with the speed of the driftMultiplier. If that happens the correction should be working ok. [b]driftHWvsCorrected[/b] <-- this should be quite static? If this increases or decreases it should tell us that the A/V sync is failing apart? Of course it wont take the bias into account. Also the adjustment might falsely cause drifting (or it could even cause real drifting). Are those assumptions valid? Or should we use something else to compute the real A/V sync drifting? I really cannot sit in the front of TV / monitor for months to watch the A/V sync slowly getting out of the drift and then make a single code line change after 2 hours have passed (to be able to detect the sync drifting) :P [/QUOTE]

Verification