Not really a feature, well maybe - but at least a map

[lexisdude 133]

It would be extremely helpful to have a "non-technical" process map that Emby goes through when a new library or library refresh is ran. Just so we know what emby does in the background and what stages are where in it's processing.

Such as:
 

• Creates library
• Reads each individual media from library and creates map in metadata directory
• copies xml/thumbnail data to metadata directory map
• updates mapping to library.db
• runs plugin > subtitle update 

etc, etc..

I think it would be good to know where certain events trigger during the updates because it would aid in determining where the system is either hung up or moving slow. I know you guys do try to answer questions on an individual complaint basis, but for those of us who would be more than welcome taking some of that investigation off your hands it might be beneficial to have such a thing. Maybe even a sub-status indicator below the percentage bar with a text indicator telling us what Emby is doing currently would really be effective. 

 

Edited December 12, 2019 by lexisdude

[Luke 37240]

Hi, yes I think more status reporting is needed. Thanks for the feedback.