royalcrown
500+ Head-Fier
- Joined
- Sep 27, 2006
- Posts
- 714
- Likes
- 11
Quote:
If this post was targeted at me, I wasn't calling anyone an idiot. The point I was trying to make is that measurements don't give interpretation, and that misinterpreting the use of measurements leads to errors. It could be that you really are an idiot and didn't understand ph0rk's post. It could be that you're smarter than all of us and were distracted. You could've been tired, multitasking... any number of things could have explained why ph0rk's post was incomprehensible to you and not to me. But measurements don't go that far. They don't give you the interpretive leap, and they also won't explain things for you (such as explaining what the post actually meant). I wasn't trying to insult anyone, I was just merely pointing out that any measurement/data collection/etc only has usefulness inside of a specific purpose. In audio's case, the measurements are not there to tell you what a device sounds like, but that by itself does not make them useless, it just means that they're helpful in some ways (such as finding differences, audible limits, etc) and not in other ways (telling someone "how something sounds," in which case it's just as inaccurate as calling something "laid back, thick, chocolaty, easy going and easy to listen to")
Originally Posted by PhilS /img/forum/go_quote.gif This thread has taken a hilarious (and sort or sad) turn. phOrk posted something. I didn't understand the point he was making, and my response was not impolite. Furthermore, I'm not an idiot. I have an Economics degree and a Law degree from a top-10 U.S. University, and have been practicing complex litigation (which involves extensive writing on complex subjects) for almost 30 years. So I would suggest that the fact that the "Flesch-Kincaid grade level" and "Flesch reading ease score" indicates phOrk's post was written at a specific grade level tells you nothing. And mike1127's point is right on. Instead of dealing with the substance of my post, and explaining what was said, the response was to (1) refer to certain measurements, which are even more irrelevant in this context than they are in audio, and (2) suggest I'm an idiot (which is what many of the skeptics do when we debate the audio issues). |
If this post was targeted at me, I wasn't calling anyone an idiot. The point I was trying to make is that measurements don't give interpretation, and that misinterpreting the use of measurements leads to errors. It could be that you really are an idiot and didn't understand ph0rk's post. It could be that you're smarter than all of us and were distracted. You could've been tired, multitasking... any number of things could have explained why ph0rk's post was incomprehensible to you and not to me. But measurements don't go that far. They don't give you the interpretive leap, and they also won't explain things for you (such as explaining what the post actually meant). I wasn't trying to insult anyone, I was just merely pointing out that any measurement/data collection/etc only has usefulness inside of a specific purpose. In audio's case, the measurements are not there to tell you what a device sounds like, but that by itself does not make them useless, it just means that they're helpful in some ways (such as finding differences, audible limits, etc) and not in other ways (telling someone "how something sounds," in which case it's just as inaccurate as calling something "laid back, thick, chocolaty, easy going and easy to listen to")