Grouped Versions Display Multiple Items

[jstruebel 1]

Hi,

 

I just updated to the latest Emby server, Version 3.0.5913.0, and now all of my movies that I grouped are displaying separately. All of my movies have two versions that I create, and before the update, when I grouped them manually through the web client, there would only be one displayed in the movies view with the blue 2 indicating the multiple versions. After the update, I still see the one grouped version with the 2, but I also get a second one displayed. See the attached screenshot. I want to only have one displayed since they are the same movie. Is there a setting that I need to change now with the latest version?

 

[Luke 42077]

Hi, no setting. I'll look into it, thanks.

[jstruebel 1]

I was playing around with this some more today and if I enable the "Group movies into collections" option under my personal display settings Emby now will display only the one movie. However, it also collapses any movies that are part of a collection which I don't like. For grouped versions I think this should be the default even if this option isn't selected. If you can change it back to the previous behavior where grouped movies only display a single item that would be nice.

 

Thank you for your work on Emby!

 

Jonathan

[Luke 42077]

I was playing around with this some more today and if I enable the "Group movies into collections" option under my personal display settings Emby now will display only the one movie. However, it also collapses any movies that are part of a collection which I don't like. For grouped versions I think this should be the default even if this option isn't selected. If you can change it back to the previous behavior where grouped movies only display a single item that would be nice.

 

Thank you for your work on Emby!

 

Jonathan

 

Hi, welcome. This actually has nothing to do with the topic of this thread. Movie collections are different from grouping multiple versions of the same movie. They are independent features. Probably it sounds like you're trying to use collections as a workaround while the grouping issue is being investigated.

[jstruebel 1]

Actually, I think it does have some relevance, since I didn't change any of my groupings or collections. All I did was enable the option. I only have collections based on the Auto Boxed Sets plugin, I have not created any collections manually. All of my other movies are just groups where the different formats, m4v or mkv, are combined. With the option enabled the grouped movies display as they used to.

 

Hopefully my explanation helps your investigation. If there is anything I can do to help, I'm more than happy to do it.

 

Jonathan

[Luke 42077]

The groupings are by different characteristics. With the option enabled, it is grouping based on members that belong to the collection, which AutoBoxSets created.

[jstruebel 1]

But then why would it also "fix" my movies that aren't part of any collection? At least I didn't intentionally put them into a collection. As you can see from the screenshots below, there are several movies that aren't in a collection, so they still display on their own, but with the option set there is only the one displayed instead of the two that display when the option is unset.

 

Could this possibly be related to the database upgrade? I think when I updated it was the first time with the new database changes that you're making. Perhaps my old groupings got upgraded to collections instead of groups? Don't know if it's a reasonable speculation or not since I don't know what the changes to the database are, but just wanted to throw it out in case it helps.

 

Screenshot with "Group movies into collections" checked

 

Screenshot with "Group movies into collections" unchecked

 

[Edit] I expect the option to change e.g the Bourne or Batman movies, but it also affected the e.g. Air Force One and Appollo 13 movies.

Edited April 17, 2016 by jstruebel

[Luke 42077]

We have an older method of querying for content, and a newer, faster method. Everything works perfectly with the older method. Under certain conditions, we still use the older method because not all features are fully supported by the new method. Anytime this happens and the older methods are used, it's going to work perfectly. It's the newer methods that exhibit the problem that need to be resolved. So because the collection grouping option is not implemented with the newer methods yet, once you enable that it switches to the older querying and that's why it works.

[jstruebel 1]

Ok, that makes sense. Thanks for the explanation! I'll wait for you all to figure out how to fix the new query method. Let me know if you want me to test anything out.