INTERACT FORUM
Windows => JRiver Media Center 33 for Windows => Topic started by: Awesome Donkey on December 21, 2024, 04:44:05 pm
-
From time-to-time, a question (https://yabb.jriver.com/interact/index.php/topic,140232.0.html) arises about MC outputting audio at a higher bit-depth, not knowing it's padding it and not dithering. I think this should be altered/adjusted in the Audio Path to aid in avoiding that confusion. A current example...
(https://i.imgur.com/cHjPMbA.png)
If you didn't know about the bit-depth padding, you can see how a user could be confused by the output stating it's 32bit and not the source 16bit.
Maybe it can be changed to display it in my example as: 44.1 kHz 16bit (32bit padded) 2ch using WASAPI Exclusive (direct connection) or something like this? Also maybe this info, especially the info in this post (https://yabb.jriver.com/interact/index.php/topic,104255.msg724769.html#msg724769) explaining the bit-depth padding can go somewhere in the wiki might be helpful?
Thoughts?
P.S. Any reason why dashes aren't used in the Audio Path, e.g. 16bit to 16-bit? Seems the latter seems to be the 'correct' terminology, no? I know, I know now I'm just nitpicking, hahaha. Happy Holidays all! ;D
-
That isn't true as soon as you use something as simple as internal volume (as in the thread you linked), and I don't believe we should lie in that case, and I don't believe it'll really squelch many questions.