@“Kyle Verry” I would like to offer you a pre-release build with fix for this - Let me know which platform
Sorry I have not checked myelf
@sa2000 said:
@“Kyle Verry” I would like to offer you a pre-release build with fix for this - Let me know which platform
Sorry I have not checked myelf
Sure. Mac.
@sa2000 sent me the pre-release build and I installed it in a Windows VM. The tagging behavior is no longer happening! 
I can happily say it is fixed and back to expected behavior.
that is indeed VERY good to hear!! I will keep my eyes peeled for the release update and patch my servers.
A new beta update appeared today Plex Media Server 1.12.3.4947. I presume this is NOT the update that resolves this issue. On a side note in the Release announcements, where Fixes are detailed, there is a (#xxxx). What does that number refer to and is there a way to find more information on that specific issue, either by way of searching for the number, or searching for the description of the issue?
@terag1e said:
A new beta update appeared today Plex Media Server 1.12.3.4947. I presume this is NOT the update that resolves this issue. On a side note in the Release announcements, where Fixes are detailed, there is a (#xxxx). What does that number refer to and is there a way to find more information on that specific issue, either by way of searching for the number, or searching for the description of the issue?
The number is an internal reference number - the text gives a summary of the issue/fix
I expect the metadata repeated refresh issue fix to be released in version 1.13.x
thanks for that clarification sa2000.
I too am impacted by this issue, it’s driving me nuts. Looking forward to a fix, hopefully soon!
Me too. I have had to return to an earlier version of Plex server on my Synology.
Yep, I’m impacted by this issue as well. Really freaking irritating - please push this through the beta channel as a hotfix immediately!
Being demanding, and joining the Plex scanning “me too” crowd doesn’t help anyone.
There is a work-around (earlier version - you keep every previous copy for at least 5 back, right? C’mon, you should)
The devs are aware of the issue.
They have a pre-release in testing.
Be happy the bug was acknowledged in record time (at least, from what I’ve seen - this is one of the quickest 'yeah, we’re seeing it, let us fix it" from Plex I’ve ever seen)
Be patient, we’re going to get a fix.
agree with your comments JamminR. You can also turn off periodically update libraries and stay on the latest version or down versioning. At least that has helped the situation in my experience. I also agree, the devs really hopped right on this issue and appears a fix is coming soon. With our voices being heard I can be patient, especially since there are a couple of “work-arounds”, even though they may not be the most convenient stop-gaps.
@com_plex said:
Just to let the devs know: I have the same problem and it renders the Plex server unusable until a restart.
Same here - running Version 1.12.3.4973 on Windows 10
@harjon said:
@com_plex said:
Just to let the devs know: I have the same problem and it renders the Plex server unusable until a restart.Same here - running Version 1.12.3.4973 on Windows 10
The fix is planned for release in 1.3.0.xxxx
@sa2000 said:
The fix is planned for release in 1.3.0.xxxx
Could you clarify?
1.3 came out in Nov 2016
@JamminR said:
@sa2000 said:
The fix is planned for release in 1.3.0.xxxxCould you clarify?
1.3 came out in Nov 2016
wow = sorry
The fix is planned for release in 1.13.0.xxxx
Still getting this issue in my music library. On windows 7 however. Really hoping it doesn’t spread to my other libraries.
The fix for the repeated matching of unmatched music artists has now been released in beta release 1.13.0.5003
See Release Note http://forums.plex.tv/discussion/comment/1661803/#Comment_1661803
- (Metadata) Don’t rematch things which have been unsuccessfully matched (#8394)
Since we are always coming here and seemingly griping, I wanted to drop back by and say this most recent beta release does indeed appear to have solved this specific problem. Job well done, devs. And you probably hear too little of that.
@terag1e said:
Since we are always coming here and seemingly griping, I wanted to drop back by and say this most recent beta release does indeed appear to have solved this specific problem. Job well done, devs. And you probably hear too little of that.
Here here! Good job Devs! Thanks for the quick fix.
