Let's put this ongoing crap about nobody hearing differences between those interconnect samples to bed, please - a number of people did, to varying degrees, including myself. Of course, the biggest blowhards here about such matters never actually do any of these tests - much easier to exercise the jaw muscles, connected to the ... finger bones, 😉.
The only guy who got significant results in potato-vs-copper was caught cheating. He still brags about his superior hearing.
As regards a very specific comparison result, yes, there was some carry on. But that wasn't the only test done, there were a number - nobody got them perfectly right, it would have been a miracle, a fluke if that happened ... but there were definite differences that were audible to several people, who then attempted to rank them, with varying degrees of success.
I liked this one better...
Isn't this more or less true of all software?
GIGO
Have to confess I feel masochistic reading these kinds of threads.
No. We are talking about having a car that when you come out of the driveway that you need to turn the steering wheel to the right. If you turn it to the left, the wheels fall off, and the roof flies into the air. The vehicle didn't come with the bits of paper that explain this subtle behaviour trait, you have to work it out by trial and error.
In contrast, here is some excellent software around, quite brilliant in fact: it quietly goes about doing what it is told to, and nothing more - and makes very intelligent guesses about what you were probably trying to achieve; never spits in your face. A good example of this is the programming language Perl - extremely satisfying to work with ...
In contrast, here is some excellent software around, quite brilliant in fact: it quietly goes about doing what it is told to, and nothing more - and makes very intelligent guesses about what you were probably trying to achieve; never spits in your face. A good example of this is the programming language Perl - extremely satisfying to work with ...
Frank have you ever posted something tangible that helps someone get more out of their setup?
Hi,
Based on Unix and C code.
This is industrial grade stuff, Frank. Simple, fast and effective.
Cheers, 😉
P.S. At Siemens it is used on the mainframes quite a lot.
Based on Unix and C code.
This is industrial grade stuff, Frank. Simple, fast and effective.
Cheers, 😉
P.S. At Siemens it is used on the mainframes quite a lot.
Let's see ...
There was a room full of all types of loudspeakers, hooked up to a switching panel - we had a listen to them, and it was suggested they should all sound identical, irrespective of how expensive they were ... but there were definite differences that were audible to several people, who then attempted to rank them, with varying degrees of success.
Another example of writing something that means absolutely nothing ...?
There was a room full of all types of loudspeakers, hooked up to a switching panel - we had a listen to them, and it was suggested they should all sound identical, irrespective of how expensive they were ... but there were definite differences that were audible to several people, who then attempted to rank them, with varying degrees of success.
Another example of writing something that means absolutely nothing ...?
Talking about a programming language vs. an application program written in that language is a meaningless exercise. You can write bad software in any language.
Scott, I would suggest I have done that on frequent occasions - what I emphasise is the approach one takes, because that is what is all-important, as far as I'm concerned.
Simple first step: put on a recording that you would like to enjoy, but can't because there is something or many things 'wrong' with the sound that you hear. Rather than toss it off as a bad recording, narrow your focus in on what actually is bugging you about the sound - that's your symptom, you're a doctor, you have to determine the cause of that symptom, and administer an effective cure. That's a process I use over and over again, and repetition of that gives the sound I'm after.
Hi,
In which case you just wrote a bad program.
Talking about writing a program and choosing the right language for it is however very important in most cases.
Cheers, 😉
In which case you just wrote a bad program.
Talking about writing a program and choosing the right language for it is however very important in most cases.
Cheers, 😉
Last edited:
Software is software, at any level. A programming language is an application program for someone who wants to build a computing tool, as compared with, say, organising their email. I did quite a bit over the years with metaprogramming - software that "writes" software, high level system building tools, that type of thing.
Good software doesn't get in your way - Microsoft is pretty notorious for creating products that tend to do this a lot ... 😉
At the next level of importance, consider all the supposed "minor" things. That's the lesson I've learnt from all my experiences over the years: raw, easily measured distortion figures mean little, but the robustness of the components in combination, working as a system means a tremendous lot. This means the integrity of each and every connection, the quality of the mains power each unit sees, the resistance of the setup to electrical interference in any form, are all crucial - my experiences have told me over and over again, if I take care over, fuss about those things, then the sound I'm after will start falling into place; it's a proven formula, for me ...
Also for others - here, Richard, abraxalito, is following his own course, his own journey of trying "way out there" ideas, and getting some excellent results. In our local area, an enthusiast interested in my thinking started to "get it", started worrying about the little things - and is having a tremendous buzz dragging out all the super dodgy recordings, and seeing how far he's progressed ... 😀.
What was interesting is that he very often fell back into the trap of listening to the sound like the typical audiophile - and adjusting the system to suit. This meant that a certain recording nominally sounded better, but many of the others sounded much worse - he was trying to make it sound 'nicer', and this is the wrong path; the system must always become more revealing - this is where you get major gains when everything is taken care of.
What was interesting is that he very often fell back into the trap of listening to the sound like the typical audiophile - and adjusting the system to suit. This meant that a certain recording nominally sounded better, but many of the others sounded much worse - he was trying to make it sound 'nicer', and this is the wrong path; the system must always become more revealing - this is where you get major gains when everything is taken care of.
Right fix, wrong science.
The usual reason for a transformer intermittently humming loudly is DC on the mains supply. Electric utilities often have control systems where they can remotely turn off some loads, such as storage water heaters, during periods of peak loads. They use either injected DC or injected tone to switch the management relays.
- Status
- Not open for further replies.