-
-
Notifications
You must be signed in to change notification settings - Fork 7
Known Limitations
- When importing played states from Trakt, the
days since played
shown in the console output will not show the correct value.- This is an issue with the
last played date
not being populated when played states are imported from Trakt to Emby/Jellyfin. - MUMC is able to compensate for this using the
_set_missing_last_played_date
options.
- This is an issue with the
-
I am unable to find API methods to query
media_item
s the following way:- Query for
media_item
s last played before a certain date - Query for
media_item
s last played a certain number of days ago - Query for
media_item
s created before a certain date - Query for
media_item
s create a certain number of days ago
- Query for
-
If someone does know how to do this, please open an issue with examples of the queries used.
-
Based on what was said above; this is how MUMC queries for
media_item
s:-
media_item
s are queried per-user based on their:- matching whitetags/blacktags
- favorite status
- played/unplayed status
- blacklisted/whitelisted library
- each
media_item
is evaluated for played status, last played date, created date and/or played count
-
- During the querying of
media_item
s for each user; a best guess delete or keep status is shown per-user.- The true delete or keep status of a
media_item
cannot be known during the querying ofmedia_item
s for each user.
- The true delete or keep status of a
- During post-processing is when each
media_item
s goes through behavioral_statements and the true delete or keep status is determined using data from all specified users.
- Series, seasons, and episodes do not all share the same subfolder Id returned from Emby during setup
- This means a recursive query at the parent level will not return children
-
Example:
- Series-A is favorited
- The expectation is all children of Series-A (i.e. Seasons-A.x and Episodes-A.x.y) are also considered favorited
- However, when querying the sub-folder for child
media_item
s no Seasons or Episodes will be returned - This is due to the disconnect in sub-folder Ids returned from Emby for each media_type and/or
media_item
- For Series-A, one folder level up:
- The sub-folder Id is 12345678
- For Season-A.x, two folder levels up:
- The sub-folder Id is 24680246
- For Episode-A.x.y, three folder levels up:
- The sub-folder Id is 97531975
- For Series-A, one folder level up:
- The expectation is all children return the same parent library sub-folder Id; similar to the "regular" library Id
- Until this is fixed in Emby, MUMC will continue to use library Ids
- Per-subfolder blacklisting/whitelisting can still be achieved by using
byPath
orbyNetworkPath
as the library matching behavior
-
Example:
- Both Emby and Jellyfin allow multiple libraries
- Both Emby and Jellyfin allow libraries to include multiple sub-folders.
- Both Emby and Jellfyin allow assigning individual users access to individual libraries.
- Emby allows assigning individual users access to individual sub-folders within libraries.
- Jellyfin does NOT allow assigning individual users access to individual sub-folders within libraries.
When setting up and editing the mumc_config.yaml
, there are 4 options for how users and libraries will be selected. When option 0 - Select users and libraries
or option 2 - Select libraries only
are chosen for a Jellyfin server, MUMC automatically links sub-folders within the same library together. (i.e. Selecting one sub-folder will select all sub-folders with the same library Id.)
For Jellyfin, if the mumc_config.yaml
is manually modified to have sub-folders from the same library, split across blacklist
and whitelist
user library sections; media_item
s from both sub-folders will be treated as blacklisted
and whitelisted
. As mentioned, this should not happen unless the mumc_config.yaml
is manually modified.
For Emby/Jellyfin, sub-folders with the same path/network path can be used across multiple libraries. If the mumc_config.yaml
is setup or manually modified to have a sub-folder with the same path/network path both blacklist
ed and whitelist
ed for a user; media_item
s from both sub-folders will be treated as blacklisted
and whitelisted
.
Per-subfolder blacklisting/whitelisting can still be achieved by using byPath
or byNetworkPath
as the library matching behavior
-
Movie Library
- /path/to/folder/movies1
- /path/to/folder/movies2
-
TV Library
- /path/to/folder/tv_shows1
- /path/to/folder/tv_shows2
-
User0
- Movie Library
- /path/to/folder/movies1
- /path/to/folder/movies2
- TV Library
- /path/to/folder/tv_shows1
- /path/to/folder/tv_shows2
- Movie Library
-
User1
- Movie Library
- /path/to/folder/movies1
- /path/to/folder/movies2
- TV Library
- /path/to/folder/tv_shows1
- /path/to/folder/tv_shows2
- Movie Library
-
User2
- Movie Library
- /path/to/folder/movies1
- /path/to/folder/movies2
- TV Library
- /path/to/folder/tv_shows1
- /path/to/folder/tv_shows2
- Movie Library
-
User3
- Movie Library
- /path/to/folder/movies1
- /path/to/folder/movies2
- TV Library
- /path/to/folder/tv_shows1
- /path/to/folder/tv_shows2
- Movie Library
-
User0
- Movie Library
- TV Library
-
User1
- Movie Library
- TV Library
-
User2
- Movie Library
- TV Library
-
User3
- Movie Library
- TV Library
- MUMC wiki
- Install
- Files & Directories
- Terminology
- Configuration File Examples
- Configuration Tree
-
Additional Information
- OS Permissions
- Configuration Builder/Editor
- Played And Created Filter Statement Breakdown
- Played And Created Filter Tag Breakdown
- Dangerous Filter Statements
- Behavioral Statement Breakdown
- Behavioral Tag Breakdown
- Blacklisting vs Whitelisting
- Blacktagging vs Whitetagging
- Library Matching byId vs byPath vs byNetworkPath
- Minimum Episodes vs Minium Played Episodes
- Conditional Behavior Priorities
- Media Mangers
- Command-Line Arguments
- Make MUMC Run FASTERRRRRR!!!
- Known Limitations