More > JRiver Media Center 33 for Windows

FLAC file tags modified

<< < (3/3)

SBass:
Thanks for your suggestions on the topic.

I want to repeat that the files although altered are sonically intact and still perfectly usable.

IMHO content importing guides should reflect the fact that files are actually appended to avoid frustration in some cases. Being in minority doesn't change the fact that files although enhanced in some way are actually manipulated. If one downloads purchased music from services like qobuz or tidal may at some point be surprised that his files have been modified.

Finding a pattern based on 2 files comparison and applying to the rest of the files won't work probably. So the changes made are irreversible unfortunately.
So the easiest solution is to recreate the original file from the source to say it safely. And the final conclusion: don't download files from the internet or at least don't admit it anywhere.

Awesome Donkey:

--- Quote from: SBass on October 07, 2024, 07:30:12 am ---I want to repeat that the files although altered are sonically intact and still perfectly usable.
--- End quote ---

Well, yeah. The audio data itself is never altered, just the metadata. And honestly most people except those in specific circumstances (like yourself) are never going to care about that part of it because the audio data is not altered.



--- Quote from: SBass on October 07, 2024, 07:30:12 am ---If one downloads purchased music from services like qobuz or tidal may at some point be surprised that his files have been modified.
--- End quote ---

Again, wording here is important as you make it sound like it's altering the audio itself when audio data is not altered in any way, just the metadata.

Believe it or not, I'm actually in a similar situation as you. I use Beyond Compare to sync my music library between my main library, my backup library and my NAS library and because of how large it is (over 150,000+ FLAC and DSF files) I can't add any new metadata fields to it without creating a massive headache. Fortunately when I started building this library the majority of the audio analysis tags were added so it wasn't a problem. What eventually became a problem was the additional metadata audio analysis added like waveform, HDCD and more recently the audio CRC field which thankfully I can disable writing of those tags to files in MC (and then I simply clear them from the library).

To avoid this in your case;

1) Restore all affected files from your backup/secondary.

2) Turn off the audio analysis feature to avoid writing of metadata to those files. Also disable the Analyze waveform and Analyze for HDCD settings.

3) Turn off the Write tool name in version setting.

4) In the Configure Auto-Import's dialog, disable the last option to Write file tags when analyzing audio, getting cover art, and applying folder-based tags

That should help avoid this if you really want to, though I have to say having the audio analysis data can be quite handy, especially for volume leveling and displaying dynamic range.

SBass:
Appreciate your helpful response Awesome Donkey and all others with their inputs. I'll go the path you suggested to avoid writing additional metadata to files.
Cheers

JimH:

--- Quote from: JimH on October 06, 2024, 11:18:39 am ---I also can't find a license for you.  I'm jimh at jriver if you'd like to explain.

--- End quote ---
Please contact me with details.

thecrow:
If you do not want any modifications to your files, you should mark them as read-only in the O/S.
This will stop any application changing them.

Navigation

[0] Message Index

[*] Previous page