§!è^$%%µ$$$$##&é2 … typical issue indeed… I have double checked this, but missed the point… sh#####
Ok, PMS server restarted now, I’m logged in the web interface. So far, so good
What would be your recommendation: scan the libs and then upgrade, or upgrade first?
Leave it be for 15 minutes. Then upgrade to 1.13.2
because this one contains a critical fix for tv shows poster art.
If you don’t have any tv shows, I guess you could stay on 1.13.0 for a while.
But then - you’ll have to upgrade at some time. Might as well do it now. 
Ok, I will follow your recom and upgrade later tonight and - finally- scan the libs!
I will keep you posted on the outcome
Thanks a million for your support!! you have saved hundreds of hours of verification, tagging, sorting, renaming…
I have no idea about your location, but if you ever come to Belgium, drop me a mail, I definitely owe you a beer (I mean to start with) !
Now back to the initial issue:
If you are using a ‘Premium Music’ library, you must always have your music in a folder structure
Music > Artist > Album > Tracks
A big folder of ‘uncategorized’/‘unsorted’ tracks with more than ~4 dozen files in it is not possible.
The Premium Music agent will fail and timeout while analysing this folder, as it tries all possible combinations of files to find an actual existing album which contains those songs …
My music is organised as follows:
\mp3\0\Album Artist - Year - Album\Track - Title.mp3
\mp3\A\Album Artist - Year - Album\Track - Title.mp3
…
\mp3\Z\Album Artist - Year - Album\Track - Title.mp3
Every single track contains the following tags:
As every track is properly tagged before being discovered by PMS, I don’t care too much about the agents
Actually, I use PMS essentially as a streaming engine
I know, the folder structure is not as per PMS recommendations, but considering the sheer volume, I have no plan to reorganise the whole stuff in this way, especially as all the albums have been properly discovered so far (I mean until the issue popped up)
@“patrick@derwael.be” said:
\mp3\0\Album Artist - Year - Album\Track - Title.mp3
\mp3\A\Album Artist - Year - Album\Track - Title.mp3
…
\mp3\Z\Album Artist - Year - Album\Track - Title.mp3
I know, the folder structure is not as per PMS recommendations, but considering the sheer volume, I have no plan to reorganise the whole stuff in this way, especially as all the albums have been properly discovered so far (I mean until the issue popped up)
That should actually be OK, but then I recommend you to do 2 things:
edit the music library, go to the ‘Advanced’ tab and tick the check box ‘Use embedded tags’
Settings - Server - Agents - Albums - last.fm
activate (if not ‘checked’ already) the line ‘Local Media Assets’ and drag it upwards, so it is the topmost line
repeat the same under
Settings - Server - Agents - Albums - Premium Music
This relies on your embedded meta tags being correct and complete.
That should actually be OK, but then I recommend you to do 2 things:
- edit the music library, go to the ‘Advanced’ tab and tick the check box ‘Use embedded tags’
Already done that
- Settings - Server - Agents - Albums - last.fm
activate (if not ‘checked’ already) the line ‘Local Media Assets’ and drag it upwards, so it is the topmost line
repeat the same under
Settings - Server - Agents - Albums - Premium MusicThis relies on your embedded meta tags being correct and complete.
Already done that as well !!
BTW: I have just started a scan… let’s see
And… it works :=)
New stuff appears as it should…
When finished, I will upgrade to 1.13.2 and see what happens
@“patrick@derwael.be” said:
When finished, I will upgrade to 1.13.2 and see what happens
Make sure that it is really finished.
Updating music libraries can take a long time, even after the icon on the library name has stopped spinning.
I guess the difficulty is to properly define “long” by integrating the #tracks, the average CPU load, the network throughput, the speed of the disks, the outside temperature and humidity and the age of the captain… right ?
Ok, sorry, couldn’t resist… I’ll upgrade tomorrow, after making sure the CPU usage is down to “not much”…
Hi,
I have just upgraded to 1.13.2
After restarting PMS, it took something like 20-30 minutes before the web interface became responsive, but at the end of the day, it started up properly, and new music is (currently) being discovered properly
Again, thanks a million for your support, this was really appreciated (and I do mean it)
