(If I do hear a difference, even if it's just confirmation bias, I will keep BitPerfect in the chain, since it does no harm and the $10 I spent on it was spent long ago and was totally worth the peace of mind it afforded when I was under the impression that it mattered more than it actually does. I suspect I won't, but it will be an interesting experiment. In fact, I keep meaning to turn off BitPerfect and do some listening to see if I can hear any difference even in a sighted/biased comparison test. Even with non-integer conversion (like 44.1 to 96) it's not likely to produce any audible effect. However, thanks to and others, I have become a lot less concerned about sample-rate conversion since I became a member of this site.
I used to be very concerned about this, and as a result purchased the $10 BitPerfect app, which sits between iTunes/Music app and the underlying MacOS, allowing on-the-fly resolution-switching (and also integer mode rather than floating-point mode, which keeps things bit-perfect). This is the major weakness of Apple's built-in core audio processing: it cannot do on-the-fly resolution switching.
Amazon music for mac issues software#
The padding of the bit depth is totally irrelevant - in fact, most "bit perfect" software that claims to leave the original signal totally unaltered will still pad 16-bit (and sometimes 24-bit) content with extra zeroes to match the maximum/default/internal PCM bit-depth of the receiving DAC. So if the Apple MIDI output resolution is set to 24/192, then everything - 16/44.1, 24/48, 24/96, 24/88.2 - will be upsampled to 192kHz, and any 16-bit source will have 8 bits' worth of zeros padded onto each PCM word to convert it to 24 bit.
Not sure if you meant to type 24/192 or 24/96, but either way the Apple OS is going to convert everything to that resolution.
0 kommentar(er)
