Reply to thread

Message

<blockquote data-quote="tourettes" data-source="post: 637539" data-attributes="member: 10858">Both logs are showing that there isn't audio buffer available to be rendered. Basicly meaning that the WASAPI device provides a buffer than won't exists (dont ask from me how it could happen).Update: in addition to that there is different results with the refresh rate detection on reclock and the EVR presenter. EVR presenter detects the refresh rate as 75 Hz, where as reclock as 75.09 Hz. That would cause 1.002 x difference in the durations (but that is not as much as you are seeing).Update #2: &quot;Because of an error in the implementation, the WASAPI may return an invalid pointer.&quot; <a href="http://kbalertz.com/957569/application-WASAPI-crash-GetBuffer-function.aspx" target="_blank">http://kbalertz.com/957569/application-WASAPI-crash-GetBuffer-function.aspx</a> - could you check if that OS update has been installed? Most likely it is installed since you seem to have SP2.</blockquote>

[QUOTE="tourettes, post: 637539, member: 10858"] Both logs are showing that there isn't audio buffer available to be rendered. Basicly meaning that the WASAPI device provides a buffer than won't exists (dont ask from me how it could happen). Update: in addition to that there is different results with the refresh rate detection on reclock and the EVR presenter. EVR presenter detects the refresh rate as 75 Hz, where as reclock as 75.09 Hz. That would cause 1.002 x difference in the durations (but that is not as much as you are seeing). Update #2: "Because of an error in the implementation, the WASAPI may return an invalid pointer." [url]http://kbalertz.com/957569/application-WASAPI-crash-GetBuffer-function.aspx[/url] - could you check if that OS update has been installed? Most likely it is installed since you seem to have SP2. [/QUOTE]

Verification