You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've come across some strangely-encoded* FLAC files in my library which loudgain gave a "Couldn't write to" error for. However, because loudgain doesn't exit with an error status in such cases, I only detected the issue well after the fact, while I was separately checking files for the presence of RG tags.
If loudgain were instead to exit with a non-zero code when encountering issues like this, wrapper scripts like rgbpm would be able to sanely detect and report issues to the user.
*: Somehow the original encoder managed to have a metadata block type other than STREAMINFO as block 0, which is I presume what caused loudgain to refuse to write to the file.
The text was updated successfully, but these errors were encountered:
I've come across some strangely-encoded* FLAC files in my library which loudgain gave a "Couldn't write to" error for. However, because loudgain doesn't exit with an error status in such cases, I only detected the issue well after the fact, while I was separately checking files for the presence of RG tags.
If loudgain were instead to exit with a non-zero code when encountering issues like this, wrapper scripts like rgbpm would be able to sanely detect and report issues to the user.
*: Somehow the original encoder managed to have a metadata block type other than
STREAMINFO
as block 0, which is I presume what caused loudgain to refuse to write to the file.The text was updated successfully, but these errors were encountered: