Sennheiser MX400 and MX500 Same sound quality?!?!
[407 byte] By [carlin] at [2007-11-9 13:15:31] 
I have the MX500s but they broke and now the treble is way to screechy "s"'s are just terrible. I have only had them for like 5 or 6 months and I am not impressed they are broken already, but whatever. I remember reading that the MX400 and MX500 are the same sound quality, but the 500 is blue colored and has the volume control, thats why it is like 6 bucks more expensive. Is this true?!?! Thanks!
# 1 Re: Sennheiser MX400 and MX500 Same sound quality?!?!
Originally posted by carlin I have the MX500s but they broke and now the treble is way to screechy "s"'s are just terrible. I have only had them for like 5 or 6 months and I am not impressed they are broken already, but whatever. I remember reading that the MX400 and MX500 are the same sound quality, but the 500 is blue colored and has the volume control, thats why it is like 6 bucks more expensive. Is this true?!?! Thanks!
I own the MX300 and the MX500, and I must say that the MX500 seem to sound better.
As far as the MX400 and MX500 concern, the frequency range of the MX500 goes to 22kHz,
and the MX400 stops at 20kHz. Duh, not sure if anyone of us can hear the difference.
The specs differ, but that doesn't mean the end-user experience differs as well.
Bye,
mage
mage at 2007-11-15 15:28:15 >
# 2 Re: Sennheiser MX400 and MX500 Same sound quality?!?!
a lot of people believe mx400 and mx500 are the samething except mx500 has a in-line volume control..mage, frequency chart dosnt tell anything, and i have learned not to believe in those numbers.. those are just numbers to give you an idea how phones will respond to different frequencies. not how they sound...
and plus, most of thsoe frequency charts are false claim anyway... because those companies know there's no way you can prove them wrong
PS* do you really think sony's MDR-EX70/71 can really hit donw to 6Hz when $3000+ subwoofers are having a hard time respounding to 8Hz?
profingersk8er at 2007-11-15 15:29:15 >
[an error occurred while processing this directive]