Understanding multi-disk naming ordering

[deibit 18]

I am trying to understand multi-disk (version) naming sorting, since it seems to be inconsistent in my case.

For example I have the movie

The Amazing Spider-Man (2012)

    The Amazing Spider-Man (2012) - CD1 - UHDBD.iso

    The Amazing Spider-Man (2012) - CD2 - BD3D.iso

 

And the movie:

The Amazing Spider-Man 2 (2014)

   The Amazing Spider-Man 2 (2014) - CD1 - UHDBD.iso

   The Amazing Spider-Man 2 (2014) - CD2 - BD3D.iso

Now for the first movie, in the version combo I see CD1 first and CD2 second (which is what I would expect), but in the second movie they are sorted as CD2 first and CD1 second (what?)

I have read several theories in the forum.. most accepted seems to be that "Emby does some magic and shows the best version for your device first". Which I struggle to understand in my case since Emby does not have a clue about the format inside the ISO files (not to mention the 3D blu-rays)

What's the exact logic then? in some cases it sorts it as I would expect (alphabetically.. CD1 before CD2..) but in some others not.

I then thought that the "-" in Spider-Man might confuse the parser.. but then why the the first movie is sorted differently than the second? (if there's a confusion, at least it should be consistent..)

 

Thanks!!

 

Edited December 22, 2023 by deibit
correction

[Luke 42079]

HI, can you show a screenshot of what you see? thanks.

[deibit 18]

Sure, here both screenshots (this is with the iPhone app, but it happens with every client)

One defaults to CD1 and the other one defaults to CD2.

Edited December 22, 2023 by deibit

[Luke 42079]

Ok these are being detected as multi-version and not multi-part. If they were detected as multi-part then there would be no version selection box and you'd see an additional parts section above cast and crew.

I'll have to test these exact file names to confirm, but off the top of my head I think the reason for this could be because cd1 and cd2 are not at the very end of the file names.

Having said all of this I just want to remind that for the best possible experience we suggest joining the files.

[deibit 18]

They should be multiversion, that’s fine.. one ISO is the 4K version and the other version is the Blu-ray 3D version. I can’t really merge them (because ISO and because different formats). I can change the rename script to put the CDx at the end of the name if that helps, but it’s strange that in some cases it renames them with the right order right?

[Luke 42079]

If this is supposed to be part 1 and part 2 then multi-version is not really the appropriate choice.

Quote

but it’s strange that in some cases it renames them with the right order right?

This has nothing to do with file names and is based on which one the app has calculated is the most efficient to play. that means you'll see a different default based on what Emby app you're using, where you're connecting from, as well as any app or server settings that impact the way playback happens.

So for that reason and others, naming them for multi-part is the more appropriate choice than multi-version.

[deibit 18]

The way I see it:

The amazing spider man-1 and the amazing spider-man 2 are two different movies, that’s why it’s right that they are in two different entries.

Then I have for each movie, two different versions, one is the Blu-ray 4K UHD disk and the second one is the Blu-ray-3D disk.

i down work with MKV or any similar format, I have ISOs, they can’t be played by emby anyway (they are played with an external player) I don’t really think that emby can really tell the different between both versions (it can’t play them anyway)

I have more examples of inconsistent naming if that helps… (avengers for one side and ant-man in the other side)

each one of the movies has two versions as well (one is the 4K iso and the other is the 3D iso)

And in some cases emby defaults to the 4K and in some cases it defaults to the 3D (which is odd since emby can’t tell the difference between them.. emby doesn’t analyze the contents of the iso file, if I’m not mistaken)

Edited December 22, 2023 by deibit

[Luke 42079]

Quote

The amazing spider man-1 and the amazing spider-man 2 are two different movies, that’s why it’s right that they are in two different entries.

That's right. This is correct. I'm not talking about the two movies, I'm talking about the two parts of a single movie. Those are being detected as multi-version instead of multi-part for the reasons I mentioned above.

[Luke 42079]

Quote

Then I have for each movie, two different versions, one is the Blu-ray 4K UHD disk and the second one is the Blu-ray-3D disk.

OK now I understand. It's just odd that you named them cd1, cd2 even though they are not multi-part.

[deibit 18]

On the other side I named real multi parts in the same way (for example LOTR or the 3D version of Avatar2 that comes with two discs, and they are treated different (and the naming convention is exactly the same)

im going nuts

Edited December 22, 2023 by deibit

[Luke 42079]

OK I just tested with your exact file names and for spiderman2 it is showing cd1 first for me. But I'm testing on the 4.8 beta channel so there could be a difference there.

[Luke 42079]

Just now, deibit said:

Ok the other side I named real multi parts in the same way (for example LOTR or the 3D version of Avatar2 that comes with two discs, and they are treated different (and the naming convention is exactly the same)

im going nuts

That's how multi-part is supposed to work. It's supposed to look a little nicer than that and use the movie poster, but that's the gist of it.

That's why when it comes to actual multi-part, for the best possible experience, I would suggest joining the files.

[deibit 18]

So the only parameter for the sorting is the file name? There’s nothing about the date when file was created or if there was a pre existing file first in the folder and then a version was added later on?

[Luke 42079]

10 hours ago, deibit said:

So the only parameter for the sorting is the file name? There’s nothing about the date when file was created or if there was a pre existing file first in the folder and then a version was added later on?

Those are not factored in, no. What's wrong with avatar and lord of the rings? You said those are real multi-parts, right? It looks like that's how they were detected, no?

[deibit 18]

Avatar and lord of the rings are perfect. I just wanted to show that with same naming convention, those are detected as multi part (which is perfect) and not multi version. I guess this is because the name of the files is identical and only the CDx tag is changing? Anyway, whatever logic emby applies, it works for those.

The issue is on the real multi version movies (not multi part). Just to be on the same page, to me a “version” is a different variation of movie (different ending, directors cut, 3D version… etc…)

I have several movies in 2D and 3D version for example. My naming is always consistent in those cases. CD1 is always the 4K UHD version and CD2 is always the 3D 1080p-BD version. After the CDx tag I have the version name. In this case it’s UHDBD for the 4K and 3DBD for the 3D version. I have some other examples of multi version tagging. Like “Directors Cut” (that I always label as CD2) and “Cinema Cut” (that I always label as CD1) and yes, the same issue happens again.. sometime the directors cut is shown first and sometimes the cinema cut is shown first. I don’t understand the logic behind it (seems pretty random if you ask me)

what I would expect is that CD1 is always shown first and CD2 second and CD3 third and so on…

Edited December 23, 2023 by deibit

[Luke 42079]

There's one more requirement for multi-version that is covered in our movie naming guide:

Movie Naming

Quote

Each version must begin with the folder name, followed by " - ".

So I'll bet that the ones being treated as multi-version fit this requirement, and the ones being treated as multi-part do not.

Does this help you adjust your file or folder names to get what you want?

[deibit 18]

Hi Luke, happy new year!

 

One example that is detected as multi-part:

The Lord of the Rings - The Fellowship of the Ring (2001) 

-- The Lord of the Rings - The Fellowship of the Ring (2001) - CD1 - Extended UHDBD.iso

-- The Lord of the Rings - The Fellowship of the Ring (2001) - CD2 - Extended UHDBD.iso

 

One example of one detected as multi version:

Ant-Man (2015)

-- Ant-Man (2015) - CD1 - UHDBD.iso

-- Ant-Man (2015) - CD2 - BD3D.iso

 

They both met the logic "folder name, followed by " - "" But one is treated as multi-part (LOTR) and one is detected as multi-version (Ant-Man).

 

And as mentioned, for the multi-versions, sometimes the CD1 file is shown as default and sometimes the CD2 file is shown as default. Naming is always consistent. I use FIlebot to rename, so it always applies the same naming logic (which can be consistently wrong or consistently right, but it's always the same logic)

[Luke 42079]

Can you show a screenshot of the ant man folder?

[Darkseidd 59]

hi, just chipping in some idea..

this seems to be Auto Box Sets plugin behavior rather than emby itself.

[deibit 18]

On 09/01/2024 at 22:52, Luke said:

Can you show a screenshot of the ant man folder?

This?

 

[deibit 18]

On 10/01/2024 at 10:05, Darkseidd said:

hi, just chipping in some idea..

this seems to be Auto Box Sets plugin behavior rather than emby itself.

Thanks for the hint, but I don't have the Auto Box Sets plugin installed at all

[Luke 42079]

OK I think that should be more consistent in the upcoming 4.8 server release. Thanks.

[deibit 18]

I have installed the beta version and the behaviour on the ordering of the versions is exactly the same.

I found a workaround though

I saw that in the cases where CD2 was ordered first as the CD1 version, the Metadata determination was taken from the CD2 file and not from the CD1 (and this assignement cannot be manually changed). What I did is to click on "Remove Identification" to reset the metadata, this triggers an automatic refresh of the metadata and when refreshed the CD1 file is taken first.

I have to redo manually all the versions where the ordering is wrong, but it's ok