+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+---- Forum: Networking & Access (https://forum.jellyfin.org/f-networking-access)
+---- Thread: Poor Remote playback (/t-poor-remote-playback)
Pages:
1
2
RE: Poor Remote playback - magu2k - 2025-01-10
(2025-01-10, 09:53 PM)TheDreadPirate Wrote: I found this post.
https://stackoverflow.com/questions/182750/map-a-network-drive-to-be-used-by-a-service
Give it a try.
Well this does seem to work, but this seems like a lot of hoop to go through to make something work now, when it worked fine before without. Would love to understand why a perfectly fine and secure method of bringing the two remote resources together was determined to no longer suffice.
My last question on this is, do you know if there is a way to make this change without it forcing a rescan of all the media and changing all the covers and backgrounds? At the moment it is doing that in the test, meaning if I do this on my main installation it wipes out months of tuning and curating and downloading all the images I want?
RE: Poor Remote playback - TheDreadPirate - 2025-01-10
To Jellyfin a SMB share mapped to a drive letter is the same as an actual local disk. With UNCs, Jellyfin has to directly handle the file accesses over the SMB share. With drive letters, the OS handles the the SMB process.
Opting to remove direct UNC functionality from Jellyfin reduces the increasingly large and complex Jellyfin code base. New and consistent code contributors and reviewers are few and far between.