Collections Issues

[Brendon 119]

Firstly, today since updating to 4.9.1.90 they seem to have become incredibly slow and laggy to load compared to what they were prior to the update. (log is attached for that), couple of seconds for the first covers to load, another couple seconds for the alphabetical nav bar on the right to appear and then it's a pause and wait scenario as you scroll for covers to load.

Secondly while investigating i have noticed that when adding new content to collections it is creating a new folder with the same name and adding -tmdb-##### to the new folder, why is this happening? FYI i do not scrape tmdb for collections, all my collections are manually curated so not sure why or how this is happening.

embyserver.txt

[GrimReaper 4739]

2 hours ago, Brendon said:

Secondly while investigating i have noticed that when adding new content to collections it is creating a new folder with the same name and adding -tmdb-##### to the new folder, why is this happening? FYI i do not scrape tmdb for collections, all my collections are manually curated so not sure why or how this is happening.

Maybe the update enabled/toggled some settings: in your Collections library, do you have TMDB meta-downloader enabled? Likewise, in your Movies library, is "Import collection information" toggled on? 

[Brendon 119]

55 minutes ago, GrimReaper said:

Maybe the update enabled/toggled some settings: in your Collections library, do you have TMDB meta-downloader enabled? Likewise, in your Movies library, is "Import collection information" toggled on? 

It was the first thing i went and checked because it has indeed done that before, but nothing has changed, also I don't recall it ever tagging the folders with a tmdb id when the metadata fetching was on.

[GrimReaper 4739]

15 minutes ago, Brendon said:

also I don't recall it ever tagging the folders with a tmdb id when the metadata fetching was on.

Maybe that's just the new manner of saving collections folder, akin to people folders: if no externalID - plain name, if externalID present - folder name appended? 

Anyway, auto-collections can only be created from item metadata, meaning "Import collection info" must've been enabled on your library (unless you're providing metadata - NFOs - externally/locally). Otherwise I don't see how would they be created. 

Edit: Also, those collections were created on 06/11 and 07/11, your log covers 12/11 so that can't be traced, maybe if you have logs covering those days you could post them or post server log when you notice same occurrence next time. 

Edit2: Does anyone else have admin rights on your server? 

Edited November 12, 2025 by GrimReaper
Append

[Luke 42077]

Quote

Maybe that's just the new manner of saving collections folder, akin to people folders: if no externalID - plain name, if externalID present - folder name appended? 

Yes that is correct.

[Brendon 119]

3 hours ago, GrimReaper said:

Maybe that's just the new manner of saving collections folder, akin to people folders: if no externalID - plain name, if externalID present - folder name appended? 

Anyway, auto-collections can only be created from item metadata, meaning "Import collection info" must've been enabled on your library (unless you're providing metadata - NFOs - externally/locally). Otherwise I don't see how would they be created. 

Edit: Also, those collections were created on 06/11 and 07/11, your log covers 12/11 so that can't be traced, maybe if you have logs covering those days you could post them or post server log when you notice same occurrence next time. 

Edit2: Does anyone else have admin rights on your server? 

 

I posted the log for the load issue which only started today with the update, the tmdb business i only just discovered but can create a log with the event if required.

there are collections that have the tmdb id in the nfo as they were grabbed during a previous update that switched the metadata on and I wasn't going through hundreds of collections to remove them, they fact they turned on and started overwriting all my custom data and auto making collections was annoying enough at the time, if i remove them it should stop duplicating the collection then? 

No, no-one has admin rights on my server but me.

Edited November 12, 2025 by Brendon

[Brendon 119]

I have attached a video of the lag i am seeing in collections since the update this morning, yesterday they were fine, fast and snappy, loaded and moved instantly when clicking a letter, now i am waiting up to 10 seconds after clicking.

 

 

[Luke 42077]

Hi there, please attach the Emby server log from when the problem occurred:

How to Report a Problem

Thanks!

 

[GrimReaper 4739]

4 hours ago, Brendon said:

if i remove them it should stop duplicating the collection then? 

Never tested, but I would assume you have to remove items from the collection first, else their metadata will retain <set>/collection info and they'd just be recreated upon next library scan and/or refresh. 

[Brendon 119]

10 hours ago, GrimReaper said:

Never tested, but I would assume you have to remove items from the collection first, else their metadata will retain <set>/collection info and they'd just be recreated upon next library scan and/or refresh. 

Tested it and if you go in and remove the tmdb id from the collection, then add the additional items it does not create a duplicate folder.

[Brendon 119]

13 hours ago, Luke said:

Hi there, please attach the Emby server log from when the problem occurred:

How to Report a Problem

Thanks!

 

My log in the first post was for this problem @Luke

[Luke 42077]

What did you do during the time of that log?