Hello!
We are having an interesting issue with 1.3.1. The command we are using is:
flac -s -V -2 "$INPUT_PATH" -o "$OUT"
output:
test.wav: ERROR during encoding
state = FLAC__STREAM_ENCODER_VERIFY_MISMATCH_IN_AUDIO_DATA
test.wav: ERROR: mismatch in decoded data, verify FAILED!
Absolute sample=197925, frame=171, channel=0, sample=933, expected -1102, got -1101
In all known cases, verify errors are caused by hardware problems,
usually overclocking or bad RAM. Delete /tmp/test.wav-12.flac
and repeat the flac command exactly as before. If it does not give a
verify error in the exact same place each time you try it, then there is
a problem with your hardware; please see the FAQ:
http://xiph.org/flac/faq.html#tools__hardware_prob
If it does fail in the exact same place every time, keep
/tmp/test.wav-12.flac and submit a bug report to:
https://sourceforge.net/p/flac/bugs/
Make sure to upload the FLAC file and use the "Monitor" feature to
monitor the bug status.
Verify FAILED! Do not trust /tmp/test.wav-12.flac
This is an example of one of many. With the compression set at '-2' we get this:
"Absolute sample=197925, frame=171, channel=0, sample=933, expected -1102, got -1101"
over and over, but sometimes it passes. So the above note "each time" is not true, but the "exact same place" is true. We muck around with -0, -1, -3, etc. and sometimes we get two distinct frame/sample pairs that recur over multiple runs, but never true random as we see in some other closed tickets here. The above frame/sync numbers occur across multiple devices (still 171/933). Odd thing is that out of a hundred devices with identical firmware, we only see the failure on ~10% of them (after 50 iterations), and the number of fails (all at 171/933) is not repeatable from run to run.
TI Sitara AM3352 at 1 GHz, 128 MB 200MHz DRAM, Linux 4.4
We have some critical deadlines, but are not making much progress. Thank you.
FLAC 1.3.1 is a very old version, and has been superseded by newer versions for more than 5 years. Please update.
Thank you. Close this bug, we figured out that it happens when only when the Sitara is clocked at 1GHz. Thank you