![]() ![]() The RMS average for both was unchanged (save for overall level). When I analyzed the results, there was a 4.88 dB reduction overall in the track on Tidal and a 4.9 dB reduction in Amazon (probably within the measurement and calculation MOE). Since I'm currently on both Amazon HD and Tidal Lossless, I decided to run a test, doing stream rips of the same track from both, with and without their respective normalization features turned on. Here's part of a write-up I did of that comparison experiment (Dec 2019) between Amazon HD and Tidal Hi-Fi: (But it's important to remember that the common understanding is that at least some of the services are tinkering with normalization on an ongoing basis it's likely that things have changed since 2019.) The dynamics within the so-adjusted files were identical the absolute maximum and minimum levels were the same, as was the average RMS level (RMS is very similar to the new LUFS standard).Īnd when I compared the normalization in place on those services at the time, I found that the dynamic processing appeared to be virtually identical. I found a small difference in absolute level between the two and adjusted for it so that new copies of each file were precisely the same maximum/minimum levels. I used special tools to capture the audio streams as they came into my computer for a specific track that I also owned on CD and knew there was only one digital mastering at the time. My previous service, Google Play Music, had not had normalization so I was intrigued to see how the two services would approach it. I've read most of this article and I have reasonable confidence in its accuracy at the time it was printed.įWIW, I got on Tidal and Amazon Music HD about the same time. This article (aimed at the production community) is probably considerably tweakier than most folks are going to be interested in or even perhaps able to follow, but as I was looking at alternative articles that popped up in a Google search, I noticed some errors of fact. There's not going to be a whole lot of variation on the first of those two factors from service to service, but normalization can vary considerably and may be the object of ongoing tinkering from those services. ![]() There are two factors potentially at play: the relative level a given service/player targets as its maximum (its own, relative '0 dB') and the nature of loudness normalization offered by the streamer (and, of course, whether or not normalization's turned on). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |