Emby is not making collection items for new movies

[marktaff 14]

I've noticed this on 4.6.3 and 4.6.4.  While investigating, I learned AutoBoxSets is deprecated, and emby now does this internally.  I've noticed two instances of it failing to make new collections.  For example, there was a single movie for a long time period, which should not have a collection as it is below the threshold of two items, but then a sequel is added to the server, at which point I expect it to create the collection, but it doesn't.  I've checked TheMovieDB, and the collections both exist there.

I think ABS used to run every night, and if memory served, you could run it manually as well.  I haven't found any way to tell emby to update the collections.  Also, it is possible whatever setting changes were made to bring this functionality within emby may have invalid defaults for my use case.  In particular, I'm thinking about NFOs.  I don't use those, but there are NFO settings that are 'ON' (Collections-->Metadata Readers-->Nfo and Collections-->Metadata Savers).  If emby uses NFO files in its own application area, that is fine, just as long as it doesn't create files where my files are stored.  If I fiddle with the settings, how do I tell emby to re-check collections?

Thanks.

[Carlo 4561]

Hi, try doing a meta-data refresh on both movies that should be part of the collection and see if that helps.

[marktaff 14]

5 minutes ago, cayars said:

Hi, try doing a meta-data refresh on both movies that should be part of the collection and see if that helps.

That worked for both of the instances. Thanks.  Any idea why it didn't do it right in the first place?

[Happy2Play 9783]

7 minutes ago, marktaff said:

That worked for both of the instances. Thanks.  Any idea why it didn't do it right in the first place?

Best guess is the migration did not prep the single item like it did the new item.

As I just saw the same on issue on my test system. Only need to Refresh the OLD existing item.

 

Edited July 15, 2021 by Happy2Play

[marktaff 14]

3 minutes ago, Happy2Play said:

Best guess is the migration did not prep the single item like it did the new item.

As I just saw the same on issue on my test system. Only need to Refresh the OLD existing item.

 

So, do you think a full movie library rescan would fix it totally? I'm thinking there may be other instances, either now that I haven't noticed yet, or in the future after I add a new sequel.  Probably a good idea, huh?

[Carlo 4561]

12 minutes ago, marktaff said:

So, do you think a full movie library rescan would fix it totally? I'm thinking there may be other instances, either now that I haven't noticed yet, or in the future after I add a new sequel.  Probably a good idea, huh?

Yes, but keep in mind this can take a while to run depending on the number of media you have. You can also adjust meta-data update frequency in the library itself so every day it's updating X amount of media items so for example all items are refreshed every 30, 60 or 90 days.

[Happy2Play 9783]

4 hours ago, marktaff said:

So, do you think a full movie library rescan would fix it totally? I'm thinking there may be other instances, either now that I haven't noticed yet, or in the future after I add a new sequel.  Probably a good idea, huh?

Depends on what you are calling a Rescan as a library scan will not do anything.  You would have to do a Refresh on the Library as all items potentially need reprocessed to accommodate the database changes.

[marktaff 14]

The full library refresh finished.  It created ten new collections that were missing that I hadn't noticed yet.  Thanks for your help, @cayars and @Happy2Play.

[Carlo 4561]

Glad you got it working!  Thanks for the update.