Good question. The fact is that most of today'ss renderers can be relied on to support 44100hz and 48000hz at 16 bit but they run out of steam for higher bitrates or bit depths. So I suppose that MC tends to err on the safe side.
If your ears can't tell, why would you want to worry your eyes about it? Enjoy the music...
Thanks for responding. It seems like everyone else thinks this is a non issue.
Actually, I think most systems can stream 96K at 24 bits fine on a wireless LAN these days. I understand being conservative, but performance changes over time. I think this function should also. Personally, I would rather have the transfer not work and then have the user select the conversion than have it done automatically without informing the user. Honestly, I think a lot of people do not know how "Convert if Necessary" works, if they even know it is there.
Why not display the conversion in the audio path display? The audio display feature has been well receive by many for other purposes. It is a great way to see that the data is passing as you think it should. I just suggest extending it. Given the complexity of today's software, displaying conversions and connection types seems like a good thing to do. That is why the option was added.
I brought this up because a new user spend a full week trying to figure out why his 96K files were being delivered to his DAC at 48K. A simple display would have helped. It would be even better if the software did not do the conversion at all unless requested. I bet there are others out there who are having their files converted and do not know it. It may not sound so bad it is obvious, but the conversion does not give you the best possible sound you can get.
Just my thoughts.