This is applicable absolutely to everything.the record is still good, but DXD sounds significantlybetterdifferent. And I like it better!
Last edited:
This is applicable absolutely to everything.the record is still good, but DXD sounds significantlybetterdifferent. And I like it better!
I am sure we hear differences and have preferences but i think they are very small compared to the production differences. I would like to see studio standard for consumers, you know the same thoughout the whole chainIn one of Jason`s chapters (I don`t remember in which one) there was a good story about tests. How he could not tell the difference between amplifiers in improperly organized test.
When I`m trying a new food, I just taste it. No special conditions, no weighted portions or calories calculating. Because this is how I normally eat. When I want to understand if something sounds better or worse, I just listen to it (usually for a long period of time). I trust my ears and my perception of sound. Otherwise there is no point in all this expensive audio gear, which could be easily "outperformed" on paper by a cheap off-the-shelf-DAC.
There is no sense in telling me I could not tell the difference, because I hear it clearly and have no doubts about it. You can convert that albums and listen to them yourself. If you could not tell the difference.. Well, my congratulations, it makes things easier for you, that`s great.
With MP3 as a mature (lossy) technology, I wonder how that'll affect the media player market. In the 2017 article that I linked to, paragraph 5 muses how this codex, at high bit-rates can subjectively sound identical to uncompressed tracks. It might become even more common way to stream music 'from the cloud'. Meh, until electronic storage becomes expensive, FLAC all the way!Well quoted, sir. Makes sense to me.
I am perfectly happy with my Schiit MB DAC and 16/44.1 Redbook music.
If DSD or DXD sounds better then go for it!
After all, it's a personal experience. You're not going to sell me any DXD recordings
The tutus were excessive...
The only problem I have with that approach is all the power cords and power supplies.Too many people want audio to be the "Swiss Army Knife" approach: one device does everything. The problem with that approach is there are inevitable compromises and trade-offs that means it might "do" everything but it does not necessarily mean it does them well. I point to the average "receiver" as an example.
Decide what function you need and get a device to accomplish that task. One box, one function. It usually leads to the best result, IMO.
After that digression through surround sound decoders, gaming rigs, and phones let me return to the three building blocks of digital to analog converter boxes. The first was digital input selection, formatting, and routing circuits. This where the digital input signal gets picked, converted to I2S or BWD or whatever the engine requires, and de-jittered in a more sophisticated design. To properly execute this, an engineer should be very conversant with digital theory and if clever will analyze the analog characteristics of the digital signal.
Mike, perhaps you could expand upon what you mean when you say what I've bolded. I would imagine some of that is proprietary, but maybe not. I can math to Calc3/Diffeq.
Many, many years ago I worked with an analog engineer. He had a fair amount of disdain for digital engineers because they basically just assumed that everything in the digital domain worked like the math said it would. Once a digital device was put on a board maybe it did, maybe it didn't according to his measurements.Mike, perhaps you could expand upon what you mean when you say what I've bolded. I would imagine some of that is proprietary, but maybe not. I can math to Calc3/Diffeq.
That's what MQA claims to beI am sure we hear differences and have preferences but i think they are very small compared to the production differences. I would like to see studio standard for consumers, you know the same thoughout the whole chain
Too many people want audio to be the "Swiss Army Knife" approach: one device does everything. The problem with that approach is there are inevitable compromises and trade-offs that means it might "do" everything but it does not necessarily mean it does them well. I point to the average "receiver" as an example.
Decide what function you need and get a device to accomplish that task. One box, one function. It usually leads to the best result, IMO.