flac dev - Jan 2014 - "Compression failed" message

Git version of the FLAC encoder prints error message:

ERROR: Compression failed (ratio 1.xyz, should be < 1.0). Please contact the
developers.

in the following cases:
a) recompressing from FLAC 1.2.1 (sometimes)
b) encoding very short wav files (around 5k samples)
c) encoding white noise test signal.

Indeed, it happens too when you re-encode to a lower compression 
setting, for example, using flac -2f on a file that was already encoded 
with flac -8f.

Maybe this check should only be used when encoding from WAV (and not 
from FLAC).

op 31-01-14 18:12, lvqcl schreef:
> Git version of the FLAC encoder prints error message:
>
> ERROR: Compression failed (ratio 1.xyz, should be < 1.0). Please contact
the developers.
>
> in the following cases:
> a) recompressing from FLAC 1.2.1 (sometimes)
> b) encoding very short wav files (around 5k samples)
> c) encoding white noise test signal.
> _______________________________________________
> flac-dev mailing list
> flac-dev at xiph.org
> http://lists.xiph.org/mailman/listinfo/flac-dev

lvqcl wrote:
> Git version of the FLAC encoder prints error message:
> 
> ERROR: Compression failed (ratio 1.xyz, should be < 1.0). Please contact
the developers.
Yes, this was added to make sure that during encoding, the flac output
file was smaller than the input file. It may be worth replacing the
"Please contact developers" with a link to a web page with an
explanation.
> in the following cases:
> a) recompressing from FLAC 1.2.1 (sometimes)
Yes, if the file was encoded with say -8 in 1.2.1 and you are
re-encoding to something less then the output file is likley
to be bigger.
> b) encoding very short wav files (around 5k samples)
In this case, flac simply isn't given enough data to find redundancy
required to actually make the file smaler.
> c) encoding white noise test signal.
In this case, flac splits the file into blocks, tries to encode each block,
files that each block cannot be compressed (information content is too
high) and adds it to the output as a verbatim block. However each verbatim
block has a block header so the output file is bigger than the input.

Does that explain it?

Cheers,
Erik
-- 
----------------------------------------------------------------------
Erik de Castro Lopo
http://www.mega-nerd.com/

Erik de Castro Lopo wrote:
> Does that explain it?
Sure. But maybe it makes sense to write "WARNING" instead of an
"ERROR"?
Or to compare compress ratio with 1.01 (or 1.05 or 1.1) instead of 1.0?