Separate different movie cuts

[ITGuy1024 18]

How are you guys separating different cuts of movies?

I have mine like this:

• Name: Apocalypse Now (Redux)
• Media path: \movies\Apocalypse Now (Redux)
   
• Name: Apocalypse Now (Theatrical)
• Media path: \movies\Apocalypse Now (Theatrical)

 

• Name: Aliens (Directors Cut)
• Media path: \movies\Aliens (Directors Cut)
   
• Name: Aliens (Extended Cut)
• Media path: \movies\Aliens (Extended Cut)

Title, sort title and original title are all named respectively.

The problem is that if I watch one version it will show both versions under "continue watching"

[roaku 842]

That's currently the expected behavior when the versions are separated:

 

You can also use the 'multi-version'  feature to combine your editions into one movie item. This solves your continue watching duplicates, but introduces issues like Emby getting confused about resume points and which version to resume.

https://emby.media/support/articles/Movie-Naming.html

There's no 100% drawback free approach to handling multiple editions right now, but maybe in the future.

[rbjtech 5284]

The way I get around this problem is once they have been identified and duplicate metadata has been retrieved - give them a unique tmdb id (made up - I just prefix 000 to the current number - and remove the other provider Id) and then lock the metadata after that.    Then that item is treated as a seperate item - still  appearing in a search and browsing (as you would want them to be) - because that is based on the 'Name' but they appear seperately as watched status (as this is done by provider Id, not name).   

This does not work if you use the multi-version/drop down - as they use the same metadata, thus you cannot change it.    You need to split the items if you want to use this 'workaround'.

and then ...

 

 

Edited January 12, 2024 by rbjtech

[roaku 842]

20 minutes ago, rbjtech said:

The way I get around this problem is once they have been identified and duplicate metadata has been retrieved - give them a unique tmdb id (made up - I just prefix 000 to the current number - and remove the other provider Id) and then lock the metadata after that.    Then that item is treated as a seperate item - still  appearing in a search and browsing (as you would want them to be) - because that is based on the 'Name' but they appear seperately as watched status (as this is done by provider Id, not name).   

This does not work if you use the multi-version/drop down - as they use the same metadata, thus you cannot change it.    You need to split the items if you want to use this 'workaround'.

and then ...

 

 

Do you know if the Trakt plugin is compatible with this approach and if Emby's watched status falls back to the item path rather than provider id?

[rbjtech 5284]

5 minutes ago, roaku said:

Do you know if the Trakt plugin is compatible with this approach and if Emby's watched status falls back to the item path rather than provider id?

I don't use Trakt myself - but if it does any internal lookup's of the ProviderId (?) I imagine it may have a hard time as it's not a valid tmdb id.    It may allow it, just not associate it with a valid movie.  If you had another system (px,jf etc)where you could change that tmdb id as well, then it may sync up as the two tmdb id's should at least 'match' - certainly worth testing

[ITGuy1024 18]

3 hours ago, rbjtech said:

The way I get around this problem is once they have been identified and duplicate metadata has been retrieved - give them a unique tmdb id (made up - I just prefix 000 to the current number - and remove the other provider Id) and then lock the metadata after that.    Then that item is treated as a seperate item - still  appearing in a search and browsing (as you would want them to be) - because that is based on the 'Name' but they appear seperately as watched status (as this is done by provider Id, not name).   

This does not work if you use the multi-version/drop down - as they use the same metadata, thus you cannot change it.    You need to split the items if you want to use this 'workaround'.

and then ...

 

 

I'm going to try this out - that's kind of what I was thinking of doing. It would only be an issue if you rescanned the media folder for metadata. I assume it would keep what is currently there.

[rbjtech 5284]

1 minute ago, ITGuy1024 said:

I'm going to try this out - that's kind of what I was thinking of doing. It would only be an issue if you rescanned the media folder for metadata. I assume it would keep what is currently there.

Yep - but you need to lock the other 'versions' post changing the tmdb id etc otherwise during a metadata refresh, they would get wiped as 'unknown'.

[ITGuy1024 18]

Ah yes good call. Can you lock the images too?

[rbjtech 5284]

12 minutes ago, ITGuy1024 said:

Ah yes good call. Can you lock the images too?

Yes, by locking the entire item (see my image above) it should lock everything related to that item.

[ITGuy1024 18]

Ah got it - wasn't showing up on mobile.