Reply to thread

Message

<blockquote data-quote="tourettes" data-source="post: 638057" data-attributes="member: 10858">red5goahead, a new version. Contains one fix for buffers and sleep handling. There was some code (not my own <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />) that was commented to be sleeping half of the buffer size, but it didn't sleep, just calculate the sleep. In theory it could cause buffer to be NULL (if driver would return that if it is required too close to the point when previous one is just released a bit ago (we have no clue what drivers are doing behind the curtain).Also it does contain a new registry setting DevicePeriod that allows user (for edbugging purposes only) change the latency / buffer size that is used. Default value is same as before, 500000 which is 50 ms (this value was recommended by James from Slysoft to albain. But for example my audio card's drivers are setting it as low as 3 ms). Please experiment with that setting. If the setting is set as zero audio renderer will query the setting from drivers.Also there is new and removed logging related to the NULL buffer (mainly workaround removed and just logging the asked buffery size.)</blockquote>

[QUOTE="tourettes, post: 638057, member: 10858"] red5goahead, a new version. Contains one fix for buffers and sleep handling. There was some code (not my own :)) that was commented to be sleeping half of the buffer size, but it didn't sleep, just calculate the sleep. In theory it could cause buffer to be NULL (if driver would return that if it is required too close to the point when previous one is just released a bit ago (we have no clue what drivers are doing behind the curtain). Also it does contain a new registry setting [b]DevicePeriod[/b] that allows user (for edbugging purposes only) change the latency / buffer size that is used. Default value is same as before, 500000 which is 50 ms (this value was recommended by James from Slysoft to albain. But for example my audio card's drivers are setting it as low as 3 ms). Please experiment with that setting. If the setting is set as [b]zero[/b] audio renderer will query the setting from drivers. Also there is new and removed logging related to the NULL buffer (mainly workaround removed and just logging the asked buffery size.) [/QUOTE]

Verification