2023-10-12, 08:28 PM
(This post was last modified: 2023-10-12, 10:00 PM by zaudio. Edited 3 times in total.)
"just for my curiosity - what operating system is your jellyfin server running?"
Ubuntu Jellyfin server Docker container prebuilt for the Nas.
"I'm not a developer, but my assumption for requiring the jellyfin server to mount the network share has to do with client limitations for communicating with the network share. For example, if you are enforcing a particular SMB protocol and SMB encryption, will the client support it? Does Jellyfin have to bundle SMB support with jellyfin? Now the devs have to maintain that."
Not so; all Jellyfin has to do is provide a direct network path for the file being played to the external player. It can do this using the existing library config field for Network share path. The external player client has to then know what to do with that path and have all the appropriate permissions to access it... which typically it can have as it's able to access remote shares itself. Mine does for sure, as I can stream the same file directly from the external player. But I want to be able to use the Jellyfin client to manage my library viewing and playing.
I understand why Jellyfin requires a mounted location for files it needs to access itself, ie for transcoding etc... that way all the networking authentication and set up is not contained within Jellyfin. But that need not apply for Directly playing to an external player... that can get a direct path, and not the mounted location.
Ubuntu Jellyfin server Docker container prebuilt for the Nas.
"I'm not a developer, but my assumption for requiring the jellyfin server to mount the network share has to do with client limitations for communicating with the network share. For example, if you are enforcing a particular SMB protocol and SMB encryption, will the client support it? Does Jellyfin have to bundle SMB support with jellyfin? Now the devs have to maintain that."
Not so; all Jellyfin has to do is provide a direct network path for the file being played to the external player. It can do this using the existing library config field for Network share path. The external player client has to then know what to do with that path and have all the appropriate permissions to access it... which typically it can have as it's able to access remote shares itself. Mine does for sure, as I can stream the same file directly from the external player. But I want to be able to use the Jellyfin client to manage my library viewing and playing.
I understand why Jellyfin requires a mounted location for files it needs to access itself, ie for transcoding etc... that way all the networking authentication and set up is not contained within Jellyfin. But that need not apply for Directly playing to an external player... that can get a direct path, and not the mounted location.