More > JRiver Media Center 19 for Mac
Files tagged in MC 19 for Windows lose custom tag values in MC 19 for Mac
couchjr:
Just a follow-up to close out this thread.
When the person tagging the files on the Windows side checked the "Save in file tags where possible" box AND invoked the "Update tags from library" command after tagging each album's worth of files, all the metadata came through perfectly on the Mac side when using the "file swap" or "re-rip" method of replacing the old files with the new ones in the old folder and updating in both directions. Many thanks!
It took us all some time to realize that checking the "Save in file tags where possible" toggle does not mean that the tags are written into the files when created. This is a little ambiguous in the interface/documentation that I've seen. The "save" or "submit" action is done via the "Update tags from library command," which must always be run in order to write tags into the media files. Apparently the checkbox when creating/editing the tag field properties merely takes the safety off--you still have to pull the trigger in a separate step.
Many thanks to Matt and everyone for help learning and solving this. We now are looking at ways to batch these retaggings from multichannel to stereo dsf files, where the multichannel files are tagged in MC 19 for Windows and the stereo files (extracted from the same iso files, so with matching file names but different paths) need to have those tags brought over on the Mac side. I'll start a new thread for this.
Matt:
--- Quote from: couchjr on December 04, 2013, 10:30:01 am ---It took us all some time to realize that checking the "Save in file tags where possible" toggle does not mean that the tags are written into the files when created. This is a little ambiguous in the interface/documentation that I've seen. The "save" or "submit" action is done via the "Update tags from library command," which must always be run in order to write tags into the media files. Apparently the checkbox when creating/editing the tag field properties merely takes the safety off--you still have to pull the trigger in a separate step.
--- End quote ---
By default, any changes you make in the library will automatically be written to the tags in a background thread.
The only requirement is that you didn't turn off Options > General > Update tags when file info changes.
couchjr:
Thanks for that info, Matt. I think we had turned that off out of an abundance of caution, as the instructions for the tag transfer directed for auto-update/auto-import. It made us nervous with these complicated classical tags that something might change without our knowing. I'll pass this along.
mstan:
--- Quote from: Matt on December 04, 2013, 10:36:33 am ---By default, any changes you make in the library will automatically be written to the tags in a background thread.
The only requirement is that you didn't turn off Options > General > Update tags when file info changes.
--- End quote ---
But if the user creates custom fields, "update file tags" is unchecked by default, I think.
MrC:
That's correct - Save in file tags (when possible) is off by default for new user fields.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version