its really hard to describe what i dont like couse english is not my native and knowing adjectives isnt my strenght eaven with the link u gave me i am not sure if that adjectives have the same meaning as if they were translated in my language some words doesnt eaven exist if u catch me.
OK, let me try a little bit, but of course some things may still be lost in translation...
Originally Posted by markidjani /img/forum/go_quote.gif
sound is not clear
Usually the term would be to describe this as "veiled," like if you speak with a scarf over your mouth. It's not getting in the way of your mouth moving, but it gets in the way of the soundwaves, and cloth
usually affects higher frequencies a lot more. Think of how a band starts playing while the theater curtain is still down, and that's a heavy cloth. Or how a terrorist might sound like in a video anonymously sent to Al Jazeera (or a ninja, except they didn't survive into the time when we have cameras) or BBC Singapore; in tv shows or movies, for the sake of people hearing the dialogue more than realism, they might have the actor speak into a mic and overlay that on the same scene, or wear a smaller microphone under the scarf.
In more severe cases the term used is "muffled," like someone is deliberately holding the scarf over your mouth, or you're too far from the theater curtain and so is the band.
some instruments are much louder then others
This may or may not be a flaw. In some cases, some instruments are deliberately recorded at a lower gain, as they are in support of the other instruments in some passages - like on a power metal tracks, the whole time the band is playing you can see the keyboardist and bassist playing, but in the parts of the song where the guitar (or both guitars if they have two) are really shredding notes, it's harder to hear the bass, and sometimes the keyboard/synthesizer too, over the guitars and also the drums. In some cases it might be psychological - the engineer might have recorded them at only slightly lower gain,
but the listener's brain focuses on the main instruments, which is how the brain works really (it doesn't "see" everything the eye sees, but sorts it out to be more comprehensible to the other parts of the brain). If it is a flaw of any sort, it would be attributable to extreme deviations in the frequency response of the system. For example, the HD600's graph shows a plateau in the upper bass to lower midrange. Usually it sounds "flat" in practice, as do my amp and DAC (on a sinewave, anyway), but when I hooked up a Cambrdige 651C CDplayer, the bass drum is a lot louder and is positioned* forward of the vocalist, and I suspect there is a further bump in the same region where the HD600 does, and makes it worse.
*On good headphones and speakers you can pick out a general location for where each sound is coming from
Originally Posted by markidjani /img/forum/go_quote.gif
sometime i hear distortion and there is always like some noice (not like when u volume up speakers too much) buts its like a music is blurred like a notes are lasting too much
There are lots of types of distortion, which, broadly defined, is any deviation from the original signal. In that example two things may be happening simultaneously. First, at higher volume, the amp circuit on the smartphone is already producing distortion in the signal as it might be boosting the frequency response in some areas. The second possible problem is that the headphones you are using require a lot of current, and also voltage, that your smartphone's amp cannot provide, and one factor in an amp that can determine the PRAT is the amplifier's slew rate.
Similarly, aside from the amp's slew rate, the speaker or headphone driver may be having difficulty reproducing those notes, regardless of the amp. On a speaker for example the enclosure design can be such that you can squeeze low bass response out of a small midwoofer, like 40hz out of a 4" speaker, but at that point it may lose control and keep vibrating instead of stopping one note to start another, or you might be hearing echoes from the port on the enclosure that don't arrive at your ears at the same time. In cars that can come from the sound from each speaker arriving at different times, even with only microseconds between them, with the listener sitting off-center and the subwoofer way back in the trunk. This is less of a problem with headphones, and I wouldn't immediately suspect those Sonys, as I would give a bit of due credit to the reviews posted here, although I didn't seem to have read that any of them used it with a smartphone (I only read through the page quickly to get an idea how good those headphones are).
PRAT - pace, rhythm, attack, timing - in subjective terms, the system should produce a sound with a "groove" to it that you would tap your feet to or otherwise get you to "groove" with the music. Even metal tracks can produce such a pleasing "groove" if the notes sound "fast," without any pitch control applied (some playback devices can go faster than the actual playback time, ie each second of it can be reduced to 0.75 seconds to make it sound faster). Take for example the following tracks from Epica - pay particular attention to how the bass guitar and drums play. On a proper system the notes should attack (the strike on the drum or the pluck on the string) and decay (fade, like when one grabs the cymbals or puts a palm on the strings to stop the vibration of the strings) quickly, except here you have a quick succession of notes.
http://www.youtube.com/watch?v=8DwMJggG-vs
And this track from Feist - it sounds "slow" on some amps, but when I switched out my NAD304, it sounds "fast."
http://www.youtube.com/watch?v=uzCjBfdrGuM
but myb i just expect too much i just dont rly enjoy listening music through it.
If i can just add that this headphones doesnt give me much better sound then my last siberia v2 which i think wasn't even genuine since i payed it 35$ from China and plastic wasnt that good
Not expecting much out of playback, but you are expecting a bit much from the smartphone - which for one doesn't have the same slew rate as an amplifier with at least two capacitors* on each channel - and perhaps also for that smartphone to drive a headphone like that, even if it gets loud easily. Amps aren't all about power, like I said there's power then there's "clean" (undistorted) power, and then there's slew rate, among others.
* http://www.ultraaudio.com/features/pics/200801_secondo.jpg - see those red barrel-like things? Those (they're black in other amps). They store energy there and they recover much quicker than batteries, so when a loud note hits, the amp sucks it up, then in an instant, they're full, ready for the next note. Car audio people use huge caps for their subwoofers for the same reason, and even some hybrid cars are beginning to use capacitors instead of batteries. My Meier Cantate.2 has two smaller caps in each channel (they only produce around 500mW per channel), and my NAD304 has one in each (35watts per channel). BTW that slew rate can be a problem elsewhere, like how I used a cheap tube preamp before, and after I replaced the cheap ceramic caps with the Mundorfs that went on sale here, it sounded as fast as when I used the NAD.
I have tried just my pc but its old one and my phone sound better and its note1 not note3
Well, there we go - the reason why you only see 16-bit/44.1khz is because the Note 1 isn't high-res compatible, even if you loaded true 24bit files in it (the Note 3 is though). However, refer to the details on my first post regarding the 64bit processor, and the link posted by billybob regarding the practical gains from high-res tracks vs redbook. Still, I still think the descriptions you gave have a lot more to do with the amplification mismatch than the bit depth.
Still, where did you get the FLAC files? Did you rip them off the CDs or did you download them off a torrent? (which means you won't really know how the seeder ripped them) While I think compressed audio would have less issue with the PRAT (less bass, less current required from the amp, less deep bass notes that would have a problem with the drivers), it's also good to have uqlity tracks to start with rather than guessing what hardware isn't performing well.
