From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: libav/ffmpeg's bitrate options have no effect in Gentoo
Date: Tue, 6 Sep 2011 10:42:06 -0400 [thread overview]
Message-ID: <CA+czFiAP34Pq7QFHUWem48kZC3p147EmUZOLSmkhL9M3wOBrmw@mail.gmail.com> (raw)
In-Reply-To: <20110906123454.GA29490@CasperVector>
On Tue, Sep 6, 2011 at 8:34 AM, Casper Ti. Vector
<caspervector@gmail.com> wrote:
> On Tue, Sep 06, 2011 at 03:09:13PM +0300, Nikos Chantziaras wrote:
>> So try with avconv instead. But for MP3, you should probably be using
>> LAME with a VBR quality setting instead.
> In fact I don't quite know what you mean in this sentence :|
'lame' is an MP3 encoder. VBR is 'variable bitrate', which means that
high-information sections in the input stream get more bits in the
output bitstream, and low-information sections in the input stream get
fewer bits in the output bitstream. An encoded song might use 192Kb/s
for a few seconds, and then 32Kb/s for a second, and jump up to
256Kb/s for a quarter-second before dropping down to 128Kb/s--but
still sound to your ear like it was encoded at a constant bitrate of
256Kb/s. All so that audio fidelity is maintained when there's
something there to actually hear.
Or, more simply:
* 'lame' is an MP3 encoder
* 'VBR' stands for 'variable bitrate', and offers a better
size/quality tradeoff scale than saying "I want 192Kb/s"
--
:wq
next prev parent reply other threads:[~2011-09-06 14:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 11:48 [gentoo-user] libav/ffmpeg's bitrate options have no effect in Gentoo Casper Ti. Vector
2011-09-06 12:09 ` [gentoo-user] " Nikos Chantziaras
2011-09-06 12:34 ` Casper Ti. Vector
2011-09-06 14:42 ` Michael Mol [this message]
2011-09-06 14:56 ` Casper Ti. Vector
2011-09-06 16:29 ` Nikos Chantziaras
2011-09-06 16:46 ` Michael Mol
2011-09-06 23:27 ` Casper Ti. Vector
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+czFiAP34Pq7QFHUWem48kZC3p147EmUZOLSmkhL9M3wOBrmw@mail.gmail.com \
--to=mikemol@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox