2.59 (build 1625) - Impact on SQ

[Suedkiez (Just a fellow user like you)]

@simon_pepper

Not shared, but who cares when it has a material effect on the SQ.

One cares out of sheer interest.

@simon_pepper

Completely different - this actually in the audio processing chain, and therefore possible to have an effect.

Well it’s not IN the processing chain, it’s an alleged external influence ON the chain. In a 25k streamer LOL.

@simon_pepper

Not Naim’s fault - it was undocumented by SU, so unknown to Naim, plus it only kicked in after the board had been powered for some time, so not present when they ‘voiced’ the firmware and checked how it operated and sounded.

So that’s 100% Naim’s fault if it’s true, not for causing it but for letting it happen in their supposed super strict testing that users pay top money for.

@simon_pepper

Sure, but then why is Roon releasing a Build that allows these tasks on the Roon Server to be scheduled, as to not interfere, if there was no impact on the operation?

Because it interfered with interactive responsiveness of the UI (and in rare cases - I suppose with underpowered servers - interruptions). There were LOTS of forum complaints about not being able to browse or edit without the UI getting stuck at inconvenient times. Nothing to do with degraded SQ:

@vova

which can lead to slow loads, responsiveness hiccups, connectivity oddities, and in rare cases even playback interruptions.