Just downloaded the new Beta Version, 1.18.1.1966. Scanning my music library now. I will let you know how it goes. Thanks.
So that makes me wonder what the server was doing for over 12 hours while it was unreachable and pegging the CPU at 100% if not scanning? Any idea?
Anything I might come up with would clearly be NSFW rated. 
Well just over an hour in and the music library scan finished. However, I think it failed somewhere. 1.5 hours on 23K files seems VERY fast.
And it also, seemed to have messed things up a bit. I can manually go changes these, but I donāt know how many are wrong. I tried re-running the music scanner, but it only seemed to run for about 5 mins and then stop. My only frame of reference to determine if it is running. Is by looking at the Activity Icon and make sure is says scanning music. Is there another way?
metadata updates can still be happening after the scan
the easiest way is to check @ Plex Web > settings > alerts
during a scan or metadata processing, you should see a bunch of stuff like
Ok. Looks like it finished then. But the Metadata is off. As you can see in previous screenshot. Maybe I can run the refresh metadata on the whole music library to fix those and others I donāt see?
there is a new āunmatchedā filter, you can use that for artists/albums to make it easier to find stuff to manually fix up.
of course that wonāt help find stuff that did match up but incorrectly
Holy Crap. I have like 7K unmatched. But when I look at the they metadata looks like it is there. What is it unmatched to? Also, those others seemed to be incorrectly matched. So, maybe I run refresh metadata on whole library and see whatās left over?
Iām down to ~600 unmatched artists, out of ~4500.
if you refresh all metadata, just be understand that it will rescan music and reprocess it, however long that takes and however much cpu (hopefully less than previous builds).
āAnything I might come up with would clearly be NSFW rated.ā
I hear you but I really canāt upgrade to that on my main server until I know it wonāt happen again. It is just too big a pain to restore the server as I donāt have any idea how to revert to a previous version of PMS.
Also, Iām setting up a folder of music with a little over 100,000 songs on my test server. Basically the A,B,C, and F folders. Iām going to make two music libraries. One with the old scanner (Plex Music) and one with the Plex Music Scanner. Iāll see if I can get some numbers on how long each scan took and what the results look like.
1.18.1 is released. Let me put up a whole new library and see what happens.
I will profile the behavior. Hopefully we can prorate from there.
Well Iāll finish this up with Version 1.18.0.1944 and when 1.18.1 shows up as available here Iāll do it again.
I am running 1.18.1 now.
It has really pulled back on the processor demands.
I see it fingerprint only 2 things of those which it can easily identify.
A few of my older albums needed to be fully fingerprinted.
Itās slowly moving along. At this rate it will take a long time.
I recommend staying where youāre at. This needs a bit more tuning.
Well my curiosity got the better of me and I again tried this new version. My results on 1.18.1 are pretty much the same as all the other 1.18s. My cpu is pegged and server is unavailable. At this point I am going to just let it sit for a few days and see if it finishes. I do have a huge 400k+ song library so Iām guessing itās going to take a while.
Please remember this thread and post a notice when a versions is released that works as well as you would like. Iām staying where I am until 1.18 (or 1.19 or 1.20) is working. Thanks for the heads up and the honesty.
keep an eye on the pms server log and possibly the scanner log (not sure if there is a log watcher type program for windows), for updates as it processes.
the scanner log may not update in the middle of some long process, but the server log should still see updates from other things.
@ all
here is what kind of load I am seeing with a music rescan/match/metadata
not near as heavy as before, but still going to be a lot of work that needs processed according to however large your music library is and however powerful or not your server is.
TeknoJunky,
The server came up a few hours after my post. So the new version def has improved as far as time to completion goes. The problem Im having is that PMS is unreachable on the local machine its hosted on, but completely reachable from any other PC on my network. If I try to connect to it on the host machine at either 127.0.0.1:32400 or app.plex.tv, it will not connect and states it as server unreachable. Also my CPU will peg to 100%. This was not an issue in anything prior to 1.18.x releases. Other then this problem it appears everything else is now working as it should, and I only had 1500 unmatched songs out of a library of 400K so Iām happy with that.
Hmm, well that that (unreachable on host/plexweb, but still accessible by clients), sounds pretty weird and unusual.
Though not sure I would be much help troubleshooting it, I would suggest open a new thread specifically for that, along with some fresh logs reproducing it, and as much details as you can provide about the system and how your network is setup.
Update. After I ran the full rescan of my library. I only have ~1400 unmatched tracks from a library of ~23K. Also, my CPU is not being pegged at 300%. There are spikes of 100%, but I would expect that during some processing. I think this version, 1.18.1.1966, has resolved the main issue I originally reported.
Maybe we can split this thread into the remaining issues?
deleted
