Reply to thread

Message

<blockquote data-quote="tourettes" data-source="post: 654834" data-attributes="member: 10858">the buffers in Reclock are most likely following:[pre-buffer] -&gt; sound processing -&gt; [wasapi buffer in audio HW]Probably when the 1st buffer is too small the rest of the pipeline starts to run out of samples. In any case we can just wonder what happens inside ReClock - or ask from James (after all he writes the code for ReClock <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />)We cannot create similar buffer &quot;just for fun&quot;. There is already an internal buffer / sample queue but not matter how big / small it is it wouldnt affect the MP audio renderer's lip sync at all since the buffer can be used right after there is few bytes of audio data - it doesn't have to be filled like the wasapi buffer on HW before the 1st bytes are sent to the speakers. So in that sence it wont have any affect on the lip sync (sound touch library causes small delay... approx 1 to 2 kb of audio data is buffered always inside it - but it is too minial to affect anything also it would be causing the lip sync issue on all different HWs, not jsut for one card type).Yep, it will be already noticeable - but so will be the lipsync in real world if you stand approx 200 meters away from the speaker (of course it requires binoculars to spot that <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />).</blockquote>

[QUOTE="tourettes, post: 654834, member: 10858"] the buffers in Reclock are most likely following: [pre-buffer] -> sound processing -> [wasapi buffer in audio HW] Probably when the 1st buffer is too small the rest of the pipeline starts to run out of samples. In any case we can just wonder what happens inside ReClock - or ask from James (after all he writes the code for ReClock :)) We cannot create similar buffer "just for fun". There is already an internal buffer / sample queue but not matter how big / small it is it wouldnt affect the MP audio renderer's lip sync at all since the buffer can be used right after there is few bytes of audio data - it doesn't have to be filled like the wasapi buffer on HW before the 1st bytes are sent to the speakers. So in that sence it wont have any affect on the lip sync (sound touch library causes small delay... approx 1 to 2 kb of audio data is buffered always inside it - but it is too minial to affect anything also it would be causing the lip sync issue on all different HWs, not jsut for one card type). Yep, it will be already noticeable - but so will be the lipsync in real world if you stand approx 200 meters away from the speaker (of course it requires binoculars to spot that :)). [/QUOTE]

Verification