<p>For CBR encodings, the bitrate is always kept at the bitrate specified regardless of if it is needed.  For VBR encoding, the bitrate is an average target, however the media stream will use more or less data rate when it needs to but will try to average to the target.</p>

<p>This is why you see 1 pass and 2 pass VBR.  2 pass VBR first makes a pass to estimate where more or less data will be needed and then makes a second pass to make best use of the available data rate.  1 pass does a lot more guessing.</p>

<p>For an example of how this works, lets say we had a video that had 10 seconds of rapid action followed by 10 seconds of a still image.  </p>

<p>With CBR, the same data rate would be used the entire time, the 10 seconds of still image would be crazy high quality since nothing is changing, but the action would then fall apart because it is changing too much.  </p>

<p>With 1 pass VBR, the algorithm would adjust to use more data for the high level of action, but it might limit itself since the entire video might be like that.  Then, when it got to the still shot, it would use almost nothing, but wouldn't hit the average rate because it didn't need the storage space.  </p>

<p>With 2 pass VBR, the first pass would discover that there is no movement at the end, so then during the second pass, a lot of data rate would be used to handle the motion really well and then very little would be used for the still image, the average data rate would be hit and the high movement portion of the video would have the highest quality of any of the encodings while the still portion wouldn't really suffer.</p>

CC BY-SA 3.0
2014-04-27T06:16:41.550Z
2014-04-27T06:16:41.550Z
AJ Henderson
<p>You can see the bitrate in this case as a quality target. It will not encode the audio strictly at that bit-rate but try to encode the audio in a way that it will always be "near" your specified bit-rate.</p>

<p>Usually you can translate certain bit-rates to a specific quality level which can be compared to lames "V0", "V2" etc. VBR settings, these presets don't define a specific bit-rate but files encoded with these settings will always end up at certain "bit-rate range". The encoder will encode the audio around a specific bit-rate but will go higher or lower within a certain threshold.</p>

<p>It doesn't make all that much sense to have bit-rats present instead of the Vorbis quality targets but I assume handbrake does this because all other codecs it offers use bit-rates. Most users are used to bit-rates and can associate it to a rough quality level. Unlike Vorbis own "q5" or "q9" which you can only translate to a relative quality difference between the different levels (if you are not used to using this codec) but you wont know what you actually end up with.</p>

<p>Wikipedia has a nice table for Vorbis quality levels/settings: <a href="http://en.wikipedia.org/wiki/Vorbis#Technical_details" rel="nofollow">http://en.wikipedia.org/wiki/Vorbis#Technical_details</a>
(on the right)</p>

<blockquote>
  <p>Quality   Nominal Bitrate     Official Xiph.Org Foundation Vorbis     aoTuV<br>
  beta 3 and later</p>
  
  <ul>
  <li>-q-2   not available   32 kbit/s</li>
  <li>-q-1   45 kbit/s   48 kbit/s</li>
  <li>-q0    64 kbit/s</li>
  <li>-q1    80 kbit/s</li>
  <li>-q2   96 kbit/s</li>
  <li>-q3   112 kbit/s</li>
  <li>-q4   128 kbit/s</li>
  <li>-q5   160 kbit/s</li>
  <li>-q6    192 kbit/s</li>
  <li>-q7   224 kbit/s</li>
  <li>-q8   256 kbit/s</li>
  <li>-q9   320 kbit/s</li>
  <li>-q10  500 kbit/s</li>
  </ul>
</blockquote>

CC BY-SA 3.0
2014-04-26T21:40:47.687Z
2014-05-01T11:30:45.820Z
2014-05-01T11:30:45.820Z
timonsku
<p>My understanding is that the vorbis algorithm uses a variable rate of encoding.</p>

<p>So, when encoding videos with audio in vorbis format, why does Handbrake ask me for a bitrate? What does Handbrake do when I choose a bitrate of 160, say, in the audio section?</p>

CC BY-SA 3.0
2014-04-26T20:31:29.140Z
I posted this question in the Super User SE, but no one answered me: [link] http://superuser.com/questions/729591/encoding-audio-in-vorbis-with-handbrake.
ltcomdata
CC BY-SA 3.0
2014-04-26T20:51:05.850Z
I can't speak about vorbis, but in general "variable" rate doesn't mean "unlimited". In all cases I'm aware of, VR encoding uses a target bit rate which is the rate which, if averaged over the total length, would be equivalent to a fixed bit rate over the same duration.
Jim Mack
<encoding><compression>
Why does variable bitrate still have a bitrate specified?
ltcomdata
# Why does variable bitrate still have a bitrate specified?

(Asked by: username_0 on 2014-04-26)

My understanding is that the vorbis algorithm uses a variable rate of encoding.

So, when encoding videos with audio in vorbis format, why does Handbrake ask me for a bitrate? What does Handbrake do when I choose a bitrate of 160, say, in the audio section?

**Tags:** encoding, compression

> **Comments:**
> **username_0**: I posted this question in the Super User SE, but no one answered me: [link] http://superuser.com/questions/729591/encoding-audio-in-vorbis-with-handbrake.  
> **username_1**: I can't speak about vorbis, but in general "variable" rate doesn't mean "unlimited". In all cases I'm aware of, VR encoding uses a target bit rate which is the rate which, if averaged over the total length, would be equivalent to a fixed bit rate over the same duration.  

---

## 2 answers

### Answer by username_3 on 2014-04-26. Score: 1 | Accepted answer

You can see the bitrate in this case as a quality target. It will not encode the audio strictly at that bit-rate but try to encode the audio in a way that it will always be "near" your specified bit-rate.

Usually you can translate certain bit-rates to a specific quality level which can be compared to lames "V0", "V2" etc. VBR settings, these presets don't define a specific bit-rate but files encoded with these settings will always end up at certain "bit-rate range". The encoder will encode the audio around a specific bit-rate but will go higher or lower within a certain threshold.

It doesn't make all that much sense to have bit-rats present instead of the Vorbis quality targets but I assume handbrake does this because all other codecs it offers use bit-rates. Most users are used to bit-rates and can associate it to a rough quality level. Unlike Vorbis own "q5" or "q9" which you can only translate to a relative quality difference between the different levels (if you are not used to using this codec) but you wont know what you actually end up with.

Wikipedia has a nice table for Vorbis quality levels/settings: <http://en.wikipedia.org/wiki/Vorbis#Technical_details>
(on the right)

> Quality Nominal Bitrate Official Xiph.Org Foundation Vorbis aoTuV  
> beta 3 and later
>
> * -q-2 not available 32 kbit/s
> * -q-1 45 kbit/s 48 kbit/s
> * -q0 64 kbit/s
> * -q1 80 kbit/s
> * -q2 96 kbit/s
> * -q3 112 kbit/s
> * -q4 128 kbit/s
> * -q5 160 kbit/s
> * -q6 192 kbit/s
> * -q7 224 kbit/s
> * -q8 256 kbit/s
> * -q9 320 kbit/s
> * -q10 500 kbit/s


---

### Answer by username_2 on 2014-04-27. Score: 2

For CBR encodings, the bitrate is always kept at the bitrate specified regardless of if it is needed. For VBR encoding, the bitrate is an average target, however the media stream will use more or less data rate when it needs to but will try to average to the target.

This is why you see 1 pass and 2 pass VBR. 2 pass VBR first makes a pass to estimate where more or less data will be needed and then makes a second pass to make best use of the available data rate. 1 pass does a lot more guessing.

For an example of how this works, lets say we had a video that had 10 seconds of rapid action followed by 10 seconds of a still image.

With CBR, the same data rate would be used the entire time, the 10 seconds of still image would be crazy high quality since nothing is changing, but the action would then fall apart because it is changing too much.

With 1 pass VBR, the algorithm would adjust to use more data for the high level of action, but it might limit itself since the entire video might be like that. Then, when it got to the still shot, it would use almost nothing, but wouldn't hit the average rate because it didn't need the storage space.

With 2 pass VBR, the first pass would discover that there is no movement at the end, so then during the second pass, a lot of data rate would be used to handle the motion really well and then very little would be used for the still image, the average data rate would be hit and the high movement portion of the video would have the highest quality of any of the encodings while the still portion wouldn't really suffer.


---

