

Please refer to the Test Invite article from mid July 2017.

Who are the people who tested and submitted results? What overall were their preferences? What was the result for each specific track? How confident were the respondents about their choice? And how significant were these findings ultimately?Īs you are probably aware, through the last 2 months on this blog, I've been collecting data to determine the audibility of decoded MQA versus the same piece of music originating from the "master" high resolution source. Today, let's focus on the "core" or "headline" results I think most of us are interested in. I feel this is the only way to properly thank those who took their time and provide as much information as possible to answer any lingering questions. I'm currently anticipating at least another couple of posts to fully flesh out the data set including posting some of the subjective comments made by listeners. While I will try to conclude with some general points by the end of this post, I will not have had time to analyze everything quite yet. Today, we'll embark on the exploration of the data itself. Within it, I laid out in detail the test, how it was constructed, and how data was collected. Yet another example of the myopia of the audiophile press and an inability to muster any leadership in changing the industry and hobby in meaningful ways.Īs you know, Part I - Procedure is now published. Unlike yet another megabuck product that provides a few minutes of eye-candy at best and affects the few, "infrastructural" changes can affect the many. To me, it is issues like these, while perhaps not "sexy" nor provides the press something to market to consumers, that when addressed can actually move the hobby forward. This IMO truly has been a ridiculous state of affairs for so many years! Despite years of cheerleading in the industry and even smaller sales outfits like NativeDSD Music already putting files out there for consumers, the relative inelegance of it all is rather silly.Īs usual, I find it rather baffling that the typical mainstream audiophile press remains silent on deficiencies like this.
Logitech media server 7.9.1 software#
The main issue is simply this: the lack of ability for gear and software to support both tagging and data compression when dealing with DSD. JRiver realtime conversion listening, PCM DSD conversion, conversion 2015, equipment DSD playback measurements like PonoPlayer / TEAC UD-501 / Oppo BDP-105 / Oppo Sonica DAC), concerns from that very first discussion about DSD still irks me these days! While over the years I've talked about DSD from a a number of different angles (eg. Many moons ago (back in 2013), I discussed DSD audio.
