bigshot
Headphoneus Supremus
I've got no problems doing that stuff. I'm not doing things to published standards, so I don't have to be 100% anal about it. My purposes are just to determine if a difference exists under normal use (listening to music in the home). If I determine a difference, I might want to apply more stringent controls to see if it's something slipping though the cracks, but I haven't had to do that. Most stuff is close enough that I can't tell even if I try hard. That is good enough for my purposes, and it's good enough for everyone else who is just listening to music on their rigs.
Now if I was running a recording studio, I would want to be more thorough. But I'm just playing back music in my living room. Most of the stuff people obsess over in internet forums are based purely on theory. They read some minute detail and then worry about it *potentially* affecting their sound. Pretty soon the inaudible molehill becomes a mountain that costs them thousands of dollars to correct. If they determined whether they could hear it first, they would save a lot of expense and worry. I listen very carefully to my system and work on improving it. I find I have more impact when I identify an audible flaw and then try to figure out what's causing it, rather than making up a theoretical flaw then trying to prove it's audible.
If you've already proven that your capture method is audibly transparent by comparing a capture to a file that hasn't been captured, then that argument is moot.
It's a lot easier to imagine differences that don't exist than it is to overlook blatant differences. And blind testing removes the element of bias anyway.
Now if I was running a recording studio, I would want to be more thorough. But I'm just playing back music in my living room. Most of the stuff people obsess over in internet forums are based purely on theory. They read some minute detail and then worry about it *potentially* affecting their sound. Pretty soon the inaudible molehill becomes a mountain that costs them thousands of dollars to correct. If they determined whether they could hear it first, they would save a lot of expense and worry. I listen very carefully to my system and work on improving it. I find I have more impact when I identify an audible flaw and then try to figure out what's causing it, rather than making up a theoretical flaw then trying to prove it's audible.
the alternative that I use a lot is to simply record the output of the DAC unloaded, and ABX that, but I've met several people who dismiss that form of testing
If you've already proven that your capture method is audibly transparent by comparing a capture to a file that hasn't been captured, then that argument is moot.
but deep down I believe you're part of the legendary cabal against good DACs, you pretend not to notice night and day differences to push your evil agenda. prove that I'm wrong!
It's a lot easier to imagine differences that don't exist than it is to overlook blatant differences. And blind testing removes the element of bias anyway.
Last edited: