Reply to thread

Message

<blockquote data-quote="Rick164" data-source="post: 1163597" data-attributes="member: 17766">Some errors do get suppressed at it would otherwise flood the logs, on every frame error would result in max 60 log lines per second for instance.Attached test build with a minor tweak which might help reduce lag and also logs every frame error so this can create large log files so recommend only running this for debugging.Old frames right now can happen as we have to wait for the AmbiBox header from the memory stream method, with the last fixes from the official release I added a wait timer (2.5s) where after we discard the frame (while accepting new ones at the same time) because sometimes AmbiBox failed and we would wait forever.Most of it are workarounds which we don't usually need but are because AmbiBox acts up now and again without any way of knowing why.Do have something on my todo-list and that is queuing for all targets where we always use the newest frame and discard old/expired ones so that we never get an old frame (FIFO queue)Just needs a bit more work and testing before that is ready <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="Rick164, post: 1163597, member: 17766"] Some errors do get suppressed at it would otherwise flood the logs, on every frame error would result in max 60 log lines per second for instance. Attached test build with a minor tweak which might help reduce lag and also logs every frame error so this can create large log files so recommend only running this for debugging. Old frames right now can happen as we have to wait for the AmbiBox header from the memory stream method, with the last fixes from the official release I added a wait timer (2.5s) where after we discard the frame (while accepting new ones at the same time) because sometimes AmbiBox failed and we would wait forever. Most of it are workarounds which we don't usually need but are because AmbiBox acts up now and again without any way of knowing why. Do have something on my todo-list and that is queuing for all targets where we always use the newest frame and discard old/expired ones so that we never get an old frame (FIFO queue) Just needs a bit more work and testing before that is ready :) [/QUOTE]

Verification