12-23-2019, 02:33 AM
@bobfa
@Tim Curtis
Found this entry https://community.roonlabs.com/t/use-fla...etup/54926 which describes what's happening.
Reading between the lines, it means Roon is transcoding everything which isn't FLAC into FLAC when this setting is enabled. This dovetails with my previous conjecture that FLAC encoding on-the-fly on your server could be leading to problems.
I note that Roon makes explicit statements about the need for adequate computing power.
In Roon's knowledge base (https://kb.roonlabs.com/Sound_Quality#Ro...her_Player), for example, we find
Regards,
Kent
@Tim Curtis
Found this entry https://community.roonlabs.com/t/use-fla...etup/54926 which describes what's happening.
Reading between the lines, it means Roon is transcoding everything which isn't FLAC into FLAC when this setting is enabled. This dovetails with my previous conjecture that FLAC encoding on-the-fly on your server could be leading to problems.
I note that Roon makes explicit statements about the need for adequate computing power.
In Roon's knowledge base (https://kb.roonlabs.com/Sound_Quality#Ro...her_Player), for example, we find
Quote:Rule 4: Don't under-spec the server
Slow servers, NAS's, and network connections can affect sound quality by preventing the Output components from receiving audio in time. This can manifests as clicks, pops, dropouts, and static.
Both Roon and all RAAT outputs use strategically placed memory playback buffers to limit the impact of this sort of thing, but poor performance can still lead to behavior in the CPU or networking hardware as it handles the audio stream in fits and spurts.
Invest in your server components just like you would in your other gear, and remember that there is no downside to a Core i7 with a fan if you've got it located two rooms away from the listening area. Take a look at our hardware specs, and try not to come in below our recommended level, and especially, plan on using an SSD to store Roon's databases.
Regards,
Kent