[PROBLEM] Update library

[alexarz]

I currently have a "clean" library of 1310 albums and 17313 tracks on a 2Tb USB 3.0 HDD, and 13 albums on the SDCARD where Moode is installed.
I generated the library, the libcache_all.json file is about 9 Mb in size. There are no errors in the mpd logs. There is only an error in the java console -

Code:

playerlib.js:706
Uncaught ReferenceError: loadLibrary is not defined
at Object.success (playerlib.js:706:40)
at u (jquery-1.8.2.js:974:30)
at Object.fireWith [as resolveWith] (jquery-1.8.2.js:1082:7)
at N (jquery-1.8.2.js:7788:14)
at XMLHttpRequest.n (jquery-1.8.2.js:8500:8)

Then I add one album to the SDCARD and run "Update this folder", I see a message about the update and the spinner spins for a few seconds. After the spinner disappears, I see the LED on the HDD start blinking. In this case, the libcache_all.json file is reset and the variables take the values -

Code:

GLOBAL.libLoading;
true
GLOBAL.libRendered;
false

Accordingly, at this time I can no longer update the folder, I get a message that "Library update is already in progress."
This continues for 18-20 minutes.
After that, when the LED stops blinking, everything returns to normal, data appears in the libcache_all.json file, and I can update a separate folder again.
I tried several times, and the result is 100% the same
Apparently, the entire library is rebuilt, although only one album was added.
I don't know why this only occurs for individual users, maybe it is related to the location of the library or something else, but I want to figure it out.
It's just that under these same conditions on version 8.3.3, updating a separate folder is very fast, and does not entail rebuilding the entire library.
It's just not my entire library, and I think that when I hook it all up, the update time will increase even more.

[Tim Curtis]

The error below indicates there is serious breakage in your moode installation. 

Code:

playerlib.js:706
Uncaught ReferenceError: loadLibrary is not defined

I don't know how that could possibly occur but the only remedy is to start with a fresh install.

[alexarz]

This may be because I imported the settings from version 8.3.3 into the current version.
Okay, I'll try with a "clean" installation.
When will version 9.3.7 be available for download?

[alexarz]

Installed version 9.3.6 from scratch.
Nothing changed, only instead of
at Object.success (playerlib.js:706:40)
it became
at Object.success (playerlib.js:707:40)

But this error appears only when "REGENERATE Music database" is executed, and if you execute "Update library", then there are no errors.

My main question was not about the error, but about the time of updating the selected folder, when after the spinner disappears, some system work continues for another 18-20 minutes, and during this time it is impossible to update the selected folder.
I tried connecting another disk instead, nothing changes, except for the processing time. The other disk contains half as many albums.

[TheOldPresbyope]

@alexarz

The consensus seems to be that what you are observing is due to the unruly state of the files in your music library. Since we aren't experiencing the same behavior on our own systems we can only guess at what's triggering it at your end.*

I, for one, am still looking for a minimum reproducible example which would enable us to make progress. I have no idea if I will stumble on one, so don't hold your breath.

Regards,
Kent

*Reminds me of Plato's Allegory of the Cave. We see only shadows dancing on the wall of the cave (the contents of your reports in this case) and try to infer the nature of the real objects moving about in the world outside.

You can tell I was impressed by my one and only philosophy course in college

[alexarz]

I have two disks with albums, and the system reacts the same, only the time is different.

Will you be able to update your SDCARD twice in a row, for example within a couple of minutes?

[TheOldPresbyope]

I have two disks with albums, and the system reacts the same, only the time is different.

Will you be able to update your SDCARD twice in a row, for example within a couple of minutes?

Short answer --- YES.

This is with a fresh moOde 9.3.6 player containing only the Stereo Test album and track (in /mnt/OSDISK, by the way, not the old /mnt/SDCARD). I can update the library from the pulldown menu on the OSDISK folder icon as many times as I like.

Then I added an album of .m4a files to the card. Again, I can update the library from the OSDISK folder as often as I want.

Finally, I added another album, this time of hi-res .flac files to the card. Again...well, you get the picture.

This is just more fuel to the argument that your updates are hanging because of the unruly^ nature of your files.

Regards,
Kent

*by "unruly" I mean their metadata is a mess.

[alexarz]

And do you have USB drives connected with a library of more than 1000 albums?
If I didn't connect any disks, everything on my SDCARD was also updated quickly.

[the_bertrum]

We are starting to go back round in the circles that the previous thread on this issue went round.

The only thing we have seen that might be different in your collection to the many other large USB based collections that other people are using without issue, is the suspicion that your collection may not be correctly tagged. There could be other things: maybe low power to the USB drives, maybe a dodgy power supply, maybe poor USB cables, maybe actual gremlins, or even an issue in moOde. The last is the least likely since this isn't an issue that affects the vast majority of users. Lets rule out some others first, starting with your collection.

If the files on the SD card update quickly why not try those files on the USB drive to see if they update quickly there?

[alexarz]

The files on the SD card are the same as on the USB drive, I copy them from there.
Maybe you don't understand me quite correctly, because I use a translator.
The files on the SD card are updated quickly, but if the USB drive is also connected, then some system work is going on, and I cannot perform a repeated update of the SD card earlier than 18-20 minutes later.
Maybe this is normal? That's why I asked to repeat this operation on your devices.

Here is another user who has the same problem.

And here is the same thing