Quote:
Originally Posted by foxyshadis
The reason the second succeeded is because a wav file exists, but it's just a header with zero data. A new empty flac file may or may not exist, either way it signaled some sort of spurious success.
|
Huh?
Note that each conversion job consists of (at least) two phases: The
decoding phase and the
encoding phase. We are talking about the
decoding phase here. In
this phase, LameXP will decode the original input file (a FLAC file in this case) to a
temporary WAV file. This temporary WAV file will
never exist before. LameXP generates a
random file name in its TEMP directory for this purpose and even makes sure the file really does not exist yet. The "overwrite existing file" option has absolutely
no effect in this phase! It
does have an effect only on the final
encoding phase (where LameXP encodes from the temporary WAV to the target output file), but we didn't even get to this point, in the case where the job failed.
And indeed, if you look at his
two logs, you'll notice that
both logs start with the
exactly same FLAC decoding command (except for the randomly generated TEMP file name, of course). The "strange" thing is that the
identical command has failed in his
first log, but apparently has succeeded in the
second log. In the
first log, FLAC rejected his input file. In the second log it didn't. This can only mean the original
input FLAC file has changed in the meantime. Either that, or FLAC has some strange bug that triggers depending on the phase of moon. Or some buggy anti-virus software has interfered with FLAC (wouldn't be the first time). But it's impossible to say from here...
(Just to make it clear: The "overwrite existing file" option does
not touch the original
input file at all. Instead, it overwrites the target
output file, if such file happens to already exist in the selected
output directory)
Quote:
Originally Posted by foxyshadis
Overall, overwriting the original files seems more dangerous than it's worth. Don't do it unless you're so space limited that you have no choice.
|
I perfectly agree with you. But the "overwrite existing file" option has been requested by users. It's
not enabled by default. And there's a fat warning, when you select this option.