Latest Build 1353 with extensive debug logging overhead?

There is an interesting comment of Taiko Audio „and reduction in what appears to be extensive debug logging to an otherwise quite nice release!“ about why the latest build is more prone to problems / sensible.
Statement on Post in thread:
Post in thread ‘Taiko Audio SGM Extreme : the Crème de la Crème’

This might be an interesting explanation why the latest build seems to be causing problems for some users / network setups.

FYI - link is broken, please fix

Thanks for the hint, got it corrected.

Seems that with every Roon update Taiko imagines sound issues without corroboration and another update „restores“ it. The infamous build 537 thread didn’t raise my trust.

That said, they may or may not have found an issue with the logging. It’s not unheard of that some new error checking code might generate an unexpectedly high number of log entries that can impact performance. It happened to me :slight_smile:

1 Like

Well they don’t tell that with every build - but this time it was more obvious. Seems with this build also when more endpoints of Roon are active the network is more sensible / prone to problems what they found.

So really investigate things thoroughly and spend a of time - and that should also help the Roon team.