INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Audio Path clarification request  (Read 96 times)

Awesome Donkey

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 7887
  • Long cold Winter...
Audio Path clarification request
« on: Yesterday at 04:44:05 pm »

From time-to-time, a question 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...



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 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
Logged
I don't work for JRiver... I help keep the forums safe from "male enhancements" and other sources of sketchy pharmaceuticals.

Windows 11 24H2 Update 64-bit + Ubuntu 24.10 Oracular Oriole 64-bit | Windows 11 24H2 Update 64-bit (Intel N305 Fanless NUC 16GB RAM/500GB M.2 NVMe SSD)
JRiver Media Center 33 (Windows + Linux) | iFi ZEN DAC 3 | JBL 306P MkII Studio Monitors | Audio-Technica ATH-M50x Headphones
Pages: [1]   Go Up