Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: FLAC Reliability (Read 5807 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: FLAC Reliability

Reply #25 –
Bandcamp does update FLAC to newer releases.  They have done so many times.

They simply do not want to upgrade to 1.4.x
 

Re: FLAC Reliability

Reply #26 –
Bandcamp allows upload as .flac, and since we know that some sixteen year old Reaper version did indeed write corrupted files that were not detected, it is very likely that one of those have been uploaded. And will be.
Detecting it? Uh-oh, extra work - better ignore and gloss over the errors of others eh?


Actually, in case of this particular error, it might be. To the extent that this hesitancy is a design choice: 
Quote from: jcoalson on
now this could have been avoided if libFLAC did range checking on the input but this noticeably slows things down, which I am hesitant to do for something that should be caught in testing.  (maybe it could be done in debug builds.)
So ... choosing not to check other applications' errors, because it would slow down for everyone and those applications should do it themselves - but also: this particular error rectifies itself.

I'd suggest that flac 1.4.next should at least update its error messages, saying that certain software did produce this sort of corruption and refer to the help file for workarounds.