Doing some "tag" maintenance work this weekend and have come across some bizarre behavior within the last build of v23 (I presume this is part of v24 as well).
Some background on what I am seeing started from here:
https://yabb.jriver.com/interact/index.php/topic,114021.msg789098.html#msg789098and then here
https://yabb.jriver.com/interact/index.php/topic,114763.0.htmlToday - I decided to run some tests - and I do not understand at all what I am seeing.
First off - I am convinced that there continues to be some major internal issues with MC picking up tag changes from network based files - especially if the changes are made by another instance of JRiver.
I have two instances of MC installed here - one running Media Server and another stand alone install that I have on my personal workstation. All my music is FLAC based and is stored in a single location on a Windows 2012 File server in a share called Music.
For reasons I will not get into - I find it much easier to add/edit and maintain our master library using my standalone install of MC. It gives me complete freedom to add/change and delete music at will. And up until recently - I thought the server install of MC would pick up my changes via Library Auto Import when changes are available.
Let me clarify - this seems to work great when adding new tracks - I can prep a new album on my standalone instance of MC, tag it up, analyze audio etc etc and then hit F6 to move it to the master share. A few minutes later - the album appears in the server install and everything is great.
NOTE: Within Auto-Import on the server instance - I do have Update for External Changes checked. The overall intent is to ensure whatever I do on my workstation instance of MC - replicates to the server instance of MC - once the server picks up any changes.
Where this start to fall apart is when I want to make changes to albums out in the share (from my workstation) - which were previously imported and appear correctly in either instance of MC. The server version of MC usually ignores these changes or worse - the tracks in the share - when examined on the server instance - display tags which are not longer present in the file - even after a manual auto-import or even something more aggressive like Update Library from tags.
Earlier this week - I even had the server instance in an RDP window - made a change or two to a specific file from my workstation and confirmed the change had occurred - then quickly switched to the server instance, pressed Auto-import manually - only to see MC report that this one file had changed - but none of the actual changes I made - were displayed within the Tag Editor on the server?
Today I noticed something even more bizarre. Based on Matt's update in the first thread I referenced above - when one does "Remove Tags" on an album - MC should strip the tags completely from all files. Which it does. (See "Tags Stripped" attachment below)
But if I keep the same file highlighted and switch back to the Tag Editor (See attachment "Tag Window - Mystery Tags") - I see a while pile of old tags - even after the strip. And after a manual auto import AND a manual Update Library From Tags - I still see old tags that I thought would be removed when I hit "Remove Tags"
If tags are stripped - I would expect to see an empty tag editor window after all this messing around.
What is going on here? What exactly am I missing or not seeing here? Am I seeing a mismatched library database displaying old data against the files that should have no tags in them? Is Update Library From Tags simply not working?
Very confused on this one.
Appreciate any intel from the field.
VP