14-Oct-2016, 13:15
Oh sure I thougt of the sceptical non believer answers, but as a first reply?
I left this wall of psycho-acoustic doubt behind me years ago.
I do comparisons of components, cables and all the stuff as a daily business and these differences one can hear (must not hear) are real in our profession. Neglecting them implies a standstill for us even in mind and empirical knowledge. For me some of the effects we can hear mainstream sience can not messure neither explain. So what? It's just something else to discover.
I understand if you commit yourself to one side or the other you can argue to death about this topic. That's not my point.
To put it short. I don't want to discuss the pure effect but I like to have a technical explanation from some open minded technician who knows his stuff about writing software in junction with the processes this initiates in hardware.
What is the real technical process here? Is there somebody who can explain it to me?
gui
I left this wall of psycho-acoustic doubt behind me years ago.
I do comparisons of components, cables and all the stuff as a daily business and these differences one can hear (must not hear) are real in our profession. Neglecting them implies a standstill for us even in mind and empirical knowledge. For me some of the effects we can hear mainstream sience can not messure neither explain. So what? It's just something else to discover.
I understand if you commit yourself to one side or the other you can argue to death about this topic. That's not my point.
To put it short. I don't want to discuss the pure effect but I like to have a technical explanation from some open minded technician who knows his stuff about writing software in junction with the processes this initiates in hardware.
What is the real technical process here? Is there somebody who can explain it to me?
gui
"Oh, you can buy the other. But then it is a cost intensive learning process"
berlin
