From 9bb1a16f9ea089217daba1b2031d1c7d7f1a1316 Mon Sep 17 00:00:00 2001 From: Josh Coalson Date: Fri, 29 Aug 2003 05:16:32 +0000 Subject: [PATCH] fix typo --- doc/html/faq.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/html/faq.html b/doc/html/faq.html index 818fa978..9215e31b 100644 --- a/doc/html/faq.html +++ b/doc/html/faq.html @@ -227,7 +227,7 @@ Why do the encoder settings have a big effect on the encoding time but not the decoding time?

- It's hard to explain without going into the codec design, but to oversimplify, the encoder is looking for functions that approximate the signal. Higher settings make the encoder search more to find better approximations. The functions are themselves encoded in the FLAC file. Decoding only requires computing the one chosen function, and the complexity of the function is vary stable. This is by design, to make decoding easier, and is one of the things that makes FLAC easy to implement in hardware. + It's hard to explain without going into the codec design, but to oversimplify, the encoder is looking for functions that approximate the signal. Higher settings make the encoder search more to find better approximations. The functions are themselves encoded in the FLAC file. Decoding only requires computing the one chosen function, and the complexity of the function is very stable. This is by design, to make decoding easier, and is one of the things that makes FLAC easy to implement in hardware.

Why use FLAC instead of other codecs that compress more?