Let's say you set minimum at 256k and had two 30s really complex pieces of music with 2 minutes of silence in between. The main disadvantage of setting too high a minimum is it will essentially force a constant bitrate of your minimum in sections that are below the minimum. I haven't experimented so I can't provide a guideline as to which quality encodes at which rates but probably low quality would encode at something much lower than 256, so forcing it to do that wouldn't have the desired space saving of choosing a lower quality since you'd be forcing it to always use 256k. In reality probably nothing would be encoded at that bitrate even if you left it set, unless you have some pure frequency hum as large sections of the track.Ĭonversely, it would not make sense to select low quality, then force iTunes to encode at a minimum of 256k. You're leaving it up to iTunes to decide, with your bitrate setting just being the lowest quality you would want to risk. If it is indeed a minimum rate as part of a general varying bitrate coding then it seems that with choosing "highest quality" probably none of the track would end up actually being encoded at 16k.
The thing to keep straight is what happens with variable (and the number reported in variable is an average of all the rates actually used) versus constant bitrate (which is a rate of encoding from start to finish regardless of the complexity of a piece).
0 kommentar(er)
