This is not a realistic solution to this issue .
@Malcolm_Percival’s problem is that Roon’s SUBJECTIVE coloring/labeling is not something he agrees with. He has no problem with the signal path items, just the coloring/labeling of each.
we have:
yellowishorange/green/purple/blue
- blue == you did something to change the sound on purpose, probably because you felt it enhanced the sound
- purple == bitperfect
- green == not bit perfect, and not something you chose to do for enhancement, but something that was done for you and the Roon Team felt that it was for compatibility of playback and done in a way that was “good enough” for the situation at hand
- yellow == not bit perfect and not one of the above
the problem is that we label “source” material with the above categories, and the only 2 that make sense are “lossy” or “bit perfect”. Obviously some things we are unable to detect, such as audio compression or a bitperfect encoding of a previously lossy compressed stream. We went ahead and made bitperfect purple here (flacs, alacs, wavs, aiffs, etc…) and made the rest yellow.
You might disagree with them being yellow, but as @brian pointed out, we would like the world to stop throwing away content when bandwidth/storage is so cheap. It doesn’t matter if you can’t hear the difference – we just feel it’s not a wise thing to do. It’s one of the reasons we support TIDAL, and not one of the lossy services we supported in previous iterates of Roon (at Sooloos and HP).