Page 1 of 1

Changes to flac metadata corrupts files (version 1.97 and 1.99)

Posted: Sat Jan 18, 2020 4:32 pm
by Lionsfan
This is brand new to me. I have been a registered user for many years.

When changing the metadata on some flac files, then saving the changes, the files were totally corrupted, to the point they could not be inserted into xrecode again (causing it to freeze) and the files were a garbled mess when trying to play them. What could have happened?

Re: Changes to flac metadata corrupts files (version 1.97 and 1.99)

Posted: Sat Jan 18, 2020 5:00 pm
by Lionsfan
More information: I was changing the album title to multiple tracks. Could the album art have been a problem?

Re: Changes to flac metadata corrupts files (version 1.97 and 1.99)

Posted: Sat Jan 18, 2020 8:10 pm
by admin
Do you still have the original flac files?
If so, could you please send at least one to xrecode@gmail.com (you could use https://wetransfer.com/ if it's too big).

Re: Changes to flac metadata corrupts files (version 1.97 and 1.99)

Posted: Sun Jan 19, 2020 8:25 am
by admin
Please install the latest beta version - viewtopic.php?f=12&t=40

Re: Changes to flac metadata corrupts files (version 1.97 and 1.99)

Posted: Wed Feb 05, 2020 5:01 pm
by privalova
I've had the exact same problem resulting in good FLAC files have been corrupted, so there's no audio stream left after writing new META-information to the file. I've tryed only to remove an image, adding another (existing one) and then trying to save the files result in the corruption.
Also, if I just change a file name - say a FLAC-file name before opening in XRECODE, the file is no longer useful in the program, and I cannot convert or do anything with the file - AND what's worse_ the file is no longer playable. :-/
Now I always make a copy of the working FLAC-files BEFORE editing with XRECODE.
Never had that problem before the last two new versions.

Re: Changes to flac metadata corrupts files (version 1.97 and 1.99)

Posted: Wed Feb 05, 2020 5:08 pm
by admin
Yes, it was unfortunate issue in the program, but it was fixed.