Closed GoogleCodeExporter closed 9 years ago
Update: it looks like a couple of other users have reported this too (tags 191,
194)
Original comment by nash...@ccianet.org
on 20 Aug 2013 at 1:16
Please send me the address of the uploaded file by e-mail.
Issue 191 and 194 are different problem. They both doesn't raise "Error has
occurred in the decoder" message.
Original comment by tmkkmac
on 20 Aug 2013 at 1:38
[deleted comment]
Well, do not reply to this issue tracker's message (your mail is opened to
public!). Mail directly to tmkkmac at gmail dot com.
Original comment by tmkkmac
on 20 Aug 2013 at 5:00
[deleted comment]
The file is (partially) broken.
22 - Run Like Hell - Pulse - Pink Floyd.flac: *** Got error code
2:FLAC__STREAM_DECODER_ERROR_STATUS_FRAME_CRC_MISMATCH
22 - Run Like Hell - Pulse - Pink Floyd.flac: ERROR while decoding data
state = FLAC__STREAM_DECODER_READ_FRAME
08 - Aint Gonna Let You Go - Slipstream - Bonnie Raitt.flac:
*** Got error code 2:FLAC__STREAM_DECODER_ERROR_STATUS_FRAME_CRC_MISMATCH
08 - Aint Gonna Let You Go - Slipstream - Bonnie Raitt.flac: ERROR while
decoding data
state = FLAC__STREAM_DECODER_READ_FRAME
Original comment by tmkkmac
on 20 Aug 2013 at 5:48
That may be - however, other decoders work just fine, and the output has no
audible defects either. I've used both Audiogate and Audacity without issue.
Are you sure the error reported is accurate?
At a minimum, shouldn't the error message be a little clearer on what the issue
is?
Original comment by nash...@ccianet.org
on 20 Aug 2013 at 6:18
Most of FLAC decoders (from 3rd party) ignore these errors. XLD works carefully
with FLAC files, to ensure bit perfect result.
I've used the official FLAC decoder for testing (flac command line binary with
-t switch). If you doubt my result, check the files by yourself.
Original comment by tmkkmac
on 20 Aug 2013 at 6:28
geez, what a pedantic f*cker. your precious little "bit perfection" is
preventing lots of folks from converting files, unnecessarily.
Original comment by gerson.s...@gmail.com
on 21 Jan 2014 at 2:14
This is bullshit. I'd rather have an imperfect file than no file at all. Maybe
other decoders have a reason to work the way they do? Consider that? Because
now I'm going to one of them.
Original comment by bradm...@gmail.com
on 7 Jun 2014 at 4:29
I've encountered this error too now after updating to the latest version,
repeatedly!
Original comment by Exe...@gmail.com
on 7 Jul 2014 at 8:27
Original issue reported on code.google.com by
nash...@ccianet.org
on 20 Aug 2013 at 1:13