📄 switchs.html
字号:
<hr width="50%" noshade align="center">
<br>
<dl> </dl>
<dt><strong>* <kbd>--noshort</kbd><a name="-noshort"> disable
short blocks frames</a></strong></dt>
</dl>
<dl>
<dd> Encode all frames using long blocks only. This could increase quality when
encoding at very low bitrates, but can produce serious pre-echo artefacts.
<dt><br>
</dt>
</dl>
<dl>
<hr width="50%" noshade align="center">
<br>
<dl> </dl>
<dt><strong>* <kbd>--notemp</kbd><a name="-notemp"> disable
temporal masking</a></strong></dt>
</dl>
<dl>
<dd>Don't make use of the temporal masking effect.
<dt><br>
</dt>
</dl>
<dl>
<hr width="50%" noshade align="center">
<br>
<dl> </dl>
<dt><strong>* <kbd>-o</kbd><a name="o"> non-original</a></strong>
</dt>
</dl>
<dl>
<dd> Mark the encoded file as being a copy.
<dt><br>
<br>
</dt>
<hr width="50%" noshade align="center">
<br>
<dl> </dl>
<dt><strong>* <kbd>-p</kbd><a name="p"> error protection</a></strong></dt>
</dl>
<dl>
<dd> Turn on CRC error protection.<br>
It will add a cyclic redundancy check (CRC) code in each frame, allowing to
detect transmission errors that could occur on the MP3 stream. However, it
takes 16 bits per frame that would otherwise be used for encoding, and then
will slightly reduce the sound quality.
<dt><br>
<br>
</dt>
<hr width="50%" noshade align="center">
<br>
<dl> </dl>
<dt><strong>* <kbd>--preset presetName</kbd> <a name="-preset"> use
built-in preset</a></strong></dt>
</dl>
<dd> Use one of the built-in presets (phone, phon+, lw, mw-eu, mw-us, sw, fm, voice, radio, tape, hifi, cd, studio).
<br>
<dd> "--preset help" gives more information about the used options in these presets.
<dt><br>
<br>
</dt>
<hr width="50%" noshade align="center">
<br>
<dl> </dl>
<dt><strong>* <kbd>--alt-preset presetName</kbd> <a name="-alt-preset"> use updated and much higher quality "alternate" presets</a></strong></dt>
</dl>
<dd> Use one of the built-in alternate presets (standard, fast standard, extreme, fast extreme, insane, or the abr/cbr modes).
<br>
<dd> "--alt-preset help" gives more information about the usage possibilities for these presets.
<dt><br>
<br>
</dt>
<hr width="50%" noshade align="center">
<br>
<dl> </dl>
<dt><strong>* <kbd>--priority 0...4</kbd><a name="-priority"> OS/2
process priority control</a></strong> </dt>
<dl>
<dd> With this option, LAME will run with a different process priority under
IBM OS/2.<br>
This will greatly improve system responsiveness, since OS/2 will have more
free time to properly update the screen and poll the keyboard/mouse. It should
make quite a difference overall, especially on slower machines. LAME's performance
impact should be minimal.<br>
<br>
<dd><b>0 (Low priority)</b><br>
Priority 0 assumes "IDLE" class, with delta 0.<br>
LAME will have the lowest priority possible, and the encoding may be suspended
very frequently by user interaction.<br>
<br>
<dd><b>1 (Medium priority)</b><br>
Priority 1 assumes "IDLE" class, with delta +31.<br>
LAME won't interfere at all with what you're doing.<br>
Recommended if you have a slower machine. <br>
<br>
<dd><b>2 (Regular priority)</b><br>
Priority 2 assumes "REGULAR" class, with delta -31.<br>
LAME won't interfere with your activity. It'll run just like a regular process,
but will spare just a bit of idle time for the system. Recommended for most
users. <br>
<br>
<dd><b>3 (High priority)</b><br>
Priority 3 assumes "REGULAR" class, with delta 0.<br>
LAME will run with a priority a bit higher than a normal process. <br>
Good if you're just running LAME by itself or with moderate user interaction.<br>
<br>
<dd><b>4 (Maximum priority)</b><br>
Priority 4 assumes "REGULAR" class, with delta +31.<br>
LAME will run with a very high priority, and may interfere with the machine
response.<br>
Recommended if you only intend to run LAME by itself, or if you have a fast
processor. <br>
<br>
<br>
Priority 1 or 2 is recommended for most users.
<dt><br>
<br>
</dt>
<hr width="50%" noshade align="center">
<br>
<dl> </dl>
<dt><strong>* <kbd>-q 0..9</kbd><a name="q"> algorithm
quality selection</a></strong></dt>
</dl>
<dl>
<dd> Bitrate is of course the main influence on quality. The higher the bitrate,
the higher the quality. But for a given bitrate, we have a choice of algorithms
to determine the best scalefactors and huffman encoding (noise shaping).<br>
<br>
-q 0: use slowest & best possible version of all algorithms. -q 0 and -q 1
are slow and may not produce significantly higher quality.<br>
<br>
-q 2: recommended. Same as -h.<br>
<br>
-q 5: default value. Good speed, reasonable quality.<br>
<br>
-q 7: same as -f. Very fast, ok quality. (psycho acoustics are used for pre-echo
& M/S, but no noise shaping is done.<br>
<br>
-q 9: disables almost all algorithms including psy-model. poor quality.
<dt><br>
<br>
</dt>
<hr width="50%" noshade align="center">
<br>
<dl> </dl>
<dt><strong>* <kbd>-r</kbd><a name="r"> input file is
raw pcm</a></strong></dt>
</dl>
<dl>
<dd> Assume the input file is raw pcm. Sampling rate and mono/stereo/jstereo
must be specified on the command line. Without -r, LAME will perform several
fseek()'s on the input file looking for WAV and AIFF headers.<br>
Might not be available on your release.
<dt><br>
<br>
</dt>
<hr width="50%" noshade align="center">
<br>
<dl> </dl>
<dt><strong>* <kbd>--resample 8/11.025/12/16/22.05/24/32/44.1/48</kbd><a name="-resample"> output
sampling frequency in kHz</a></strong></dt>
</dl>
<dl>
<dd> Select ouptut sampling frequency (for encoding only). <br>
If not specified, LAME will automatically resample the input when using high
compression ratios.
<dt><br>
</dt>
</dl>
<dl>
<hr width="50%" noshade align="center">
<br>
<dl> </dl>
<dt><strong>* <kbd>--r3mix</kbd><a name="-r3mix"> r3mix
VBR preset</a></strong></dt>
</dl>
<dl>
<dd> Uses r3mix VBR preset. <br>
See <a href="http://www.r3mix.net">www.r3mix.net</a> for more details.
<dt><br>
</dt>
</dl>
<dl>
<hr width="50%" noshade align="center">
<br>
<dl> </dl>
<dt><strong>* <kbd>-s 8/11.025/12/16/22.05/24/32/44.1/48</kbd><a name="s"> sampling
frequency</a></strong> </dt>
</dl>
<dl>
<dd> Required only for raw PCM input files. Otherwise it will be determined
from the header of the input file.<br>
<br>
LAME will automatically resample the input file to one of the supported MP3
samplerates if necessary.
<dt><br>
<br>
</dt>
<hr width="50%" noshade align="center">
<br>
<dl> </dl>
<dt><strong>* <kbd>-S / --silent / --quiet</kbd><a name="-silent"> silent
operation</a></strong> </dt>
</dl>
<dl>
<dd> Don't print progress report.
<dt><br>
<br>
</dt>
<hr width="50%" noshade align="center">
<br>
<dl> </dl>
<dt><strong>* <kbd>--scale n</kbd><a name="-scale"> scales
input by n</a></strong> </dt>
<dt><strong>* <kbd>--scale-l n</kbd><a name="-scale-l"> scales
input channel 0 (left) by n</a></strong> </dt>
<dt><strong>* <kbd>--scale-r n</kbd><a name="-scale-r"> scales
input channel 1 (right) by n</a></strong> </dt>
</dl>
<dl>
<dd>Scales input by n. This just multiplies the PCM data (after it has been
converted to floating point) by n. <br>
<br>
n > 1: increase volume<br>
n = 1: no effect<br>
n < 1: reduce volume<br>
<br>
Use with care, since most MP3 decoders will truncate data which decodes to
values greater than 32768.
<dt><br>
<br>
</dt>
<hr width="50%" noshade align="center">
<br>
<dl> </dl>
<dt><strong>* <kbd>--short</kbd><a name="-short"> use
short blocks</a></strong> </dt>
</dl>
<dl>
<dd>Let LAME use short blocks when appropriate. It is the default setting.
</dl>
<dl>
<dd>
<dt><br>
<br>
</dt>
<hr width="50%" noshade align="center">
<br>
<dl> </dl>
<dt><strong>* <kbd>--strictly-enforce-ISO</kbd><a name="-strictly-enforce-ISO"> strict
ISO compliance</a></strong> </dt>
</dl>
<dl>
<dd> With this option, LAME will enforce the 7680 bit limitation on total frame
size.<br>
This results in many wasted bits for high bitrate encodings but will ensure
strict ISO compatibility. This compatibility might be important for hardware
players.
</dl>
<dl>
<dd>
<dt><br>
<br>
</dt>
<hr width="50%" noshade align="center">
<br>
<dl> </dl>
<dt><strong>* <kbd>-t</kbd><a name="t"> disable INFO/WAV
header </a></strong></dt>
</dl>
<dl>
<dd> Disable writing of the INFO Tag on encoding.<br>
This tag in embedded in frame 0 of the MP3 file. It includes some information
about the encoding options of the file, and in VBR it lets VBR aware players
correctly seek and compute playing times of VBR files.<br>
<br>
When '--decode' is specified (decode to WAV), this flag will disable writing
of the WAV header. The output will be raw pcm, native endian format. Use -x
to swap bytes.
<dt><br>
<br>
</dt>
<hr width="50%" noshade align="center">
<br>
<dl> </dl>
<dt><strong>* <kbd>-V 0...9</kbd><a name="V"> VBR quality
setting</a></strong></dt>
</dl>
<dl>
<dd> Enable VBR (Variable BitRate) and specifies the value of VBR quality.<br>
default=4<br>
0=highest quality.
<dt><br>
<br>
</dt>
<hr width="50%" noshade align="center">
<br>
<dl> </dl>
<dt><strong>* <kbd>--vbr-new</kbd><a name="-vbr-new"> new
VBR mode</a></strong></dt>
</dl>
<dl>
<dd> Invokes the newest VBR algorithm. During the development of version 3.90,
considerable tuning was done on this algorithm, and it is now considered to
be on par with the original --vbr-old. <br>
It has the added advantage of being very fast (over twice as fast as --vbr-old).
<dt><br>
<br>
</dt>
<hr width="50%" noshade align="center">
<br>
<dl> </dl>
<dt><strong>* <kbd>--vbr-old</kbd><a name="-vbr-old"> older
VBR mode</a></strong></dt>
</dl>
<dl>
<dd> Invokes the oldest, most tested VBR algorithm. It produces very good quality
files, though is not very fast. This has, up through v3.89, been considered
the "workhorse" VBR algorithm.
<dt><br>
<br>
</dt>
<hr width="50%" noshade align="center">
<br>
<dl> </dl>
<dt><strong>* <kbd>--verbose</kbd><a name="-verbose"> verbosity</a></strong></dt>
</dl>
<dl>
<dd> Print a lot of information on screen.
<dt><br>
<br>
</dt>
<hr width="50%" noshade align="center">
<br>
<dl> </dl>
<dt><strong>* <kbd>-x</kbd><a name="x"> swapbytes</a></strong>
</dt>
</dl>
<dl>
<dd> Swap bytes in the input file or ouptut file when using --decode.<br>
For sorting out little endian/big endian type problems. If your encodings
sounds like static, try this first.
<dt><br>
<br>
</dt>
<hr width="50%" noshade align="center">
<br>
<dl> </dl>
<dt><strong>* <kbd>-X 0...7</kbd><a name="Xquant"> change
quality measure</a></strong> </dt>
</dl>
<dl>
<dd> When LAME searches for a "good" quantization, it has to compare the actual
one with the best one found so far. The comparison says which one is better,
the best so far or the actual. The -X parameter selects between different
approaches to make this decision, -X0 beeing the default mode:<br>
<br>
<b>-X0 </b><br>
The criterions are (in order of importance):<br>
* less distorted scalefactor bands<br>
* the sum of noise over the thresholds is lower<br>
* the total noise is lower<br>
<br>
<b>-X1</b><br>
The actual is better if the maximum noise over all scalefactor bands is less
than the best so far .<br>
<br>
<b>-X2</b><br>
The actual is better if the total sum of noise is lower than the best so far.<br>
<br>
<b>-X3</b><br>
The actual is better if the total sum of noise is lower than the best so far
and the maximum noise over all scalefactor bands is less than the best so
far plus 2db.<br>
<br>
<b>-X4</b> <br>
Not yet documented.<br>
<br>
<b>-X5</b><br>
The criterions are (in order of importance):<br>
* the sum of noise over the thresholds is lower <br>
* the total sum of noise is lower<br>
<br>
<b>-X6</b> <br>
The criterions are (in order of importance):<br>
* the sum of noise over the thresholds is lower<br>
* the maximum noise over all scalefactor bands is lower<br>
* the total sum of noise is lower<br>
<br>
<b>-X7</b> <br>
The criterions are:<br>
* less distorted scalefactor bands<br>
or<br>
* the sum of noise over the thresholds is lower
</dl>
</BODY>
</HTML>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -