Even though I'm not a professional audio/video editor I'm trying to reach a good balance between quality and file size for movies and TV Shows, mostly very old, I have on my computer so, maybe, I could throw away the original files in favor of the reduced ones.

Despite a noticeable color change already being counter-measured on the videos, I believe I'll stick to the WebM format that's making the videos around 50% smaller without noticeable changes, at least to me.

I'm talking about video in an audio community because the source file is going to be encoded with Adobe Premiere/Adobe Media Encoder (CC 2017, for what matters) using Fnord's WebM Plugin providing me access to Vorbis and Opus Audio Codecs.

The thing is I've been searching the whole morning and I didn't find anything on how I could actually compare audio samples encoded with, in this case, Vorbis, at different bitrates.

I've generated 3 small samples at 96kbps, 128kbps and 192kbps (being this one the same of original audio source) and, honestly, I didn't hear any difference at all. Like I said, I'm not a pro, so I lack all the usual hardware professional engineers have and I don't have trained ears for the task either.

That's why I came here asking if there's something easier, maybe even visual, that would help me choose between one or another. Of course, not only the tool for the task, but how to proceed as well.

Just an example, ONE episode of a ~20mins TV Show on my disk at 96kbps occupies ~169MB while at 192kbps it's 184 MB. 15 MB per episode, 75 episodes, that's a whooping ~1.1 GB I could save. And even if I don't lower too much down to 96kbps and stick to 128kbps the difference still of 10 MB per episode.

Unfortunately, where I live, the price (literally, cash price) per MB isn't too shabby because of the excessive number of taxes to simply ignore this matter.

1 Answer 1


There's no easy way to measure the perceptual differences (i.e. as perceived by an average audience) between different audio encodings or bitrates.

The common way to do these tests is ABX tests.

ABX tests are commonly used in evaluations of digital audio data compression methods;

Some organizations have setup such tests : http://opus-codec.org/comparison/

The figure below illustrates the quality of various codecs as a function of the bitrate. It attempts to summarize results from a collection of listening tests and (when no data exists) show anecdotal evidence. It is overall fairly representative, but attempting to extract any exact value at a particular bitrate is certainly not recommended.

bitrate/quality comparaison

This figure might help you determine which perceptual gain you can expect by raising the bit rate.

Notice that you could encode a test signal at different bit rates, decode them to PCM and visually look at the difference of the decoded files. This is not significant in terms of perceptual differences.

As for your actual problem, there are at least two alternatives :

  • trust your small own tests and go for the lower bitrate as you didn't hear any difference at all.
  • consider the small amount of disk space required to use one of the higher bit rate and act conservatively, as you don't know how things will change in the future.
  • Focusing on AAC and MP3 usually present on MP4/MKV containers and Vorbis / Opus of WebM, from what I can see from (missing) 96 kbps and onwards there's a diminishing return being the differences more and more subtle with the bitrate increments, right? Commented Jun 10, 2017 at 16:47
  • You're right. The point is how 'subtle' is perceived ...
    – audionuma
    Commented Jun 10, 2017 at 17:24
  • Alright, I won't lie that you answered my question because coming from the outside world of audio engineering (even though at a very low point like this) I'll have to work hard over what you said to understand. But your information was a very good kickstart, which is kind of rare in other StackExchange communities, and for that I thank you you ;) Commented Jun 10, 2017 at 19:26

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.