.
Sep 24, 2012 at 10:27 PM Post #16 of 32
I wouldn't worry about it...  too much. For IEMs, don't worry. For hi-fi speakers or full size audiophile headphones, it does matter a little.


Not in myexperience. I have a pretty fantastic stereo, and my media serveris all AAC 256 VBR. No need for lossless. Do a controlled test and you'll find out too.
 
Sep 24, 2012 at 10:42 PM Post #18 of 32
You don't need to do anything with VBR. It will raise or lower the bitrate as needed.
 
Sep 25, 2012 at 1:13 AM Post #20 of 32
Quote:
Well when i turn on vbr, it asks ne what quality i should choose (lowest to highest) i chose highest of course which compressed the song above 256 so i guess ill stick with that one

 
Its a good choice, but doesn't work that way really. What you choose is the average bit rate. The algorithm will adjust itself based on the data it needs to compress in that frame. MP3 is usually read in 'frames', something like video. Each frame will have an associated bitrate, essentially limiting the amount of information that can be put in that frame.
The good thing about VBR is that its not hard limited by the bit rate you specify, so it can go both ways from your specified bit rate. Quiet portions use less bitrate, portions with more data use higher bitrates. Of course the hard limit here is the max bit rate supported by the encoder.
 
Sep 25, 2012 at 11:40 AM Post #21 of 32
Quote:
Not in myexperience. I have a pretty fantastic stereo, and my media serveris all AAC 256 VBR. No need for lossless. Do a controlled test and you'll find out too.

 
I have done a blind listening test in a studio with some professional Focal monitors, and although I personally couldn't tell the difference for every song, the people who worked there were able to, and pointed out certain things that I picked up on.
I doubt you have an acoustically treated room (most people don't). It makes a big difference.
 
Hard drive space is dirt cheap. There is no reason to rip at less than the highest quality if you are using expensive hi-fi equipment.
 
Sep 25, 2012 at 11:48 AM Post #22 of 32
I tried once doing an ABX test with Foobar.
Its really hard to tell which one is which, and you'll develop a certain knack for it after repeated listening. That lasts for one song.
confused_face.gif
A new song, and there'll be new artifacts you'll need to recognize.
 
However, I'm curious as to whats the golden benchmark I keep hearing about. Usually everywhere I've read, the pros say they can pick the two apart, and the common answer is, "you'll be able to do as well, once you know what to look for."
 
Please can someone impart this wisdom to us uninitiated??
 
Sep 25, 2012 at 12:28 PM Post #23 of 32
I have done a blind listening test in a studio with some professional Focal monitors, and although I personally couldn't tell the difference for every song, the people who worked there were able to, and pointed out certain things that I picked up on.


I bet that was MP3, not AAC.
 
Sep 25, 2012 at 12:29 PM Post #24 of 32
'm curious as to whats the golden benchmark I keep hearing about. Usually everywhere I've read, the pros say they can pick the two apart, and the common answer is, "you'll be able to do as well, once you know what to look for." Please can someone impart this wisdom to us uninitiated??


It either artifacts, or it doesn't.
 
Sep 25, 2012 at 5:17 PM Post #25 of 32
Quote:
 
Its a good choice, but doesn't work that way really. What you choose is the average bit rate. The algorithm will adjust itself based on the data it needs to compress in that frame. MP3 is usually read in 'frames', something like video. Each frame will have an associated bitrate, essentially limiting the amount of information that can be put in that frame.
The good thing about VBR is that its not hard limited by the bit rate you specify, so it can go both ways from your specified bit rate. Quiet portions use less bitrate, portions with more data use higher bitrates. Of course the hard limit here is the max bit rate supported by the encoder.

i once had a VBR codec for MP3 that i could set to go as low as 32kbps and as high as 320. it was pretty cool to watch the bitrate indicator on winamp and see how some musically "bland" stuff would dip down to 32-64kbps while other things with tons of harmonics would send it up to 320.
 
Sep 25, 2012 at 11:24 PM Post #27 of 32
What was the difference in sound? Did they level match?
 
Oct 2, 2012 at 2:18 AM Post #29 of 32
Quote:
What was the difference in sound? Did they level match?

 
Yeah the levels were not touched.
They noticed differences in the high frequencies. In particular, snare drums sounded more "crunchy" on the mp3. I actually preferred it during blind listening tests. It was very subtle though. I mean, the addition of air conditioning noise would be enough to mask it.
 
Oct 2, 2012 at 2:23 AM Post #30 of 32
Five bucks says that they were using a track that was peaked out. The drum beats were probably clipping. I've found that certain MP3 encoders tend to shift the volume a little bit as they encode. iTunes generally encodes a little quieter than the original track, but there are some that boost the level a hair. If the track was normalized up to 100% (like almost all rock music is) and they used one of those encoders, it would push the loudest part of the track (the snare drum transients) up into clipping and make them sound crunchy.
 
If you see them again, take a track that is normalized down to 90% off the peak and see if it's still crunchy. I bet that fixes it.
 

Users who are viewing this thread

Back
Top