[Flac] flac -- exhaustive model search vs. -A <*>?
flac at tlinx.org
Sun Jun 17 13:09:45 PDT 2012
Martin Leese wrote:
> it states, "If the max LPC order is high this
> can significantly increase the encode time."
> This suggest that if the max LPC order is low
> then using -e will not be slow.
That brings up another question then... What is 'hi' (v. low?)...
The doc on -l makes it look like 12 is the max for "subset streams":
-l #, --max-lpc-order=#
Specifies the maximum LPC order. This number must be <=
Subset streams, it must be <=12 if the sample rate is
If 0, the encoder will not attempt generic linear
and use only fixed predictors. Using fixed predictors is
but usually results in files being 5-10% larger.
What's a subset stream? Under "--lax", it says:
--lax Allow encoder to generate non-Subset files. The resulting FLAC
file may not be streamable or might have trouble being
all players (especially hardware devices), so you
use this option in combination with custom encoding
meant for archival.
There -- it sounds like "subset" refers to the subset of "flac encodings"
that is "streamable" and/or work on all(or most) players... Sorta like
320Kbps being the max rate for "MP3's that conform to the standard"...
If that's the case then the highest -l value one can 'portably' use would
be 12? FWIW, I've tried 16 & 12 and noticed no difference in exhaustive's
Another "nit" I noticed, from
in the inter-channel-decorrelation section -- it mentions -m vs.
-M, where -m always uses mid+side channel whether it is bigger or not,
while -M adaptively uses mid+side or stereo depending on which is better.
Why would flac levels 7 and 8 use -m (always when -M allows adaptive
based on which is better?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Flac