2024-09-11, 11:59 AM
(This post was last modified: 2024-09-11, 12:03 PM by mcarlton00. Edited 1 time in total.)
I haven't read through this entire thread, but it looks like this entire situation started with a misunderstanding.
The "network location" text box that you could enter a path has no effect on media scanning. Exactly zero relevance. That text box was purely for a very niche feature that's been basically unsupported since the project started, and has finally been removed for future versions.
Jellyfin does not read networked filesystems directly, and it never has. It's always required that media be mounted to the host OS in a way that allows the software to read it locally. ie: Giving Jellyfin a path of
If you're running Jellyfin as admin, but mounted the paths as your user, it might not work. If you're running Jellyfin as a service but mounted the paths as your user, it might not work. I haven't used Windows in 10 years, but it has permissions quirks that you should be aware of if you're trying to use it as a server. There are similar situations when trying to set up HWA on Windows based servers.
Additionally, you should know that your "by-letter" folder organization is not one of our supported formats. The scanner expects to be given a folder containing the media itself, not with another arbitrary letter folder thrown in the middle. It might work, it might not, but that's not a use case we're set up to handle.
from our examples:
* for movies, Jellyfin expects to be given the "Movies" folder: https://jellyfin.org/docs/general/server/media/movies/
* for shows, Jellyfin expects to be given the "Shows" folder: https://jellyfin.org/docs/general/server/media/shows
The "network location" text box that you could enter a path has no effect on media scanning. Exactly zero relevance. That text box was purely for a very niche feature that's been basically unsupported since the project started, and has finally been removed for future versions.
Jellyfin does not read networked filesystems directly, and it never has. It's always required that media be mounted to the host OS in a way that allows the software to read it locally. ie: Giving Jellyfin a path of
\\MainPC\Movies 4 will not work. It needs to be mounted and accessible by the user running Jellyfin.If you're running Jellyfin as admin, but mounted the paths as your user, it might not work. If you're running Jellyfin as a service but mounted the paths as your user, it might not work. I haven't used Windows in 10 years, but it has permissions quirks that you should be aware of if you're trying to use it as a server. There are similar situations when trying to set up HWA on Windows based servers.
Additionally, you should know that your "by-letter" folder organization is not one of our supported formats. The scanner expects to be given a folder containing the media itself, not with another arbitrary letter folder thrown in the middle. It might work, it might not, but that's not a use case we're set up to handle.
from our examples:
* for movies, Jellyfin expects to be given the "Movies" folder: https://jellyfin.org/docs/general/server/media/movies/
* for shows, Jellyfin expects to be given the "Shows" folder: https://jellyfin.org/docs/general/server/media/shows