Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Thread Closed 
Problem: Library update in progress message
(06-23-2025, 04:48 PM)Yawarakaimono Wrote:
(06-23-2025, 04:14 PM)Nutul Wrote: P.S.
I am getting a little sick of all these discussions going on for days, just to see in the end that the problem is 99% due to the presence of files not tagged properly.
We should have a go-through list, and point every "library does not end updating" thread to it; it could save us some precious time, to be dedicated to other, more relevant issues.

The 'problem' is that it is not possible to update the library when some Javascript variable is 'true'.
The real problem is that people do not understand WHAT can get the variable not to be updated to its correct state, because some of the missing / wrong metadata prevent the program flow from doing that.
Now, I do have c==some 17K files in my library, and never, NEVER, have gotten my update process to FAIL. And if I had, I went to analising those NEW files, to see if, prhaps, there was some corrupt / inconsistent data.
It's not your due to monitor the libraryLoaded or libraryUpdated flags, that is a job of the software. You just need to check your files for correct tagging. Nothing more, nothing less.
If you are used to some software that does not care about audio files AND their correct tagging mechanism, that is YOUR fault.
We tend to do things the right way, around here.

Sorry for the rant, but, as I said, I am beginning to get very p***ed about all blablabla without any intention, by the posters, to check and provide the information WE request (because we need it...) in order to help them; and in response, all we get is some "I don't understand why LibraryLoaded is called some 20 seconds after the library scan completed"!

Did I get understood?
It is not 20 seconds, it is several hours on my Pi 3.



My intention really is to give you valuable information.

Database regenerations and updates never gave errors.

But it is very difficult to accomplish updates because most of the time an alert pops up that an update process is already running. Except sometimes. It took many hours-long tries in the hope to find a pattern.

The json file with all library data for loadLibrary() is about 28 megaByte.
Would that take long to produce and process?


Gert
(06-23-2025, 09:53 PM)Yawarakaimono Wrote: It is not 20 seconds, it is several hours on my Pi 3.



My intention really is to give you valuable information.

Database regenerations and updates never gave errors.

But it is very difficult to accomplish updates because most of the time an alert pops up that an update process is already running. Except sometimes. It took many hours-long tries in the hope to find a pattern.

The json file with all library data for loadLibrary() is about 28 megaByte.
Would that take long to produce and process?


Gert

A 28MB libcache file should load into the Browser very quickly. 

Keep in mind that the code behind the "Update library" process has been working fine for most of our users including for those with fairly large collections of 30K, 50K or more tracks. It's part of the moOde codebase that hasn't really changed that much for many years.

Whats happening on your end is a mystery but it looks like something external to moode software.

This thread is not really productive anymore .
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
OK

Have a nice day!


Forum Jump: