2023-10-15, 07:56 PM
(This post was last modified: 2023-10-15, 08:14 PM by IceToast. Edited 1 time in total.)
Okay so i've investigated further. I did lie in my OP a little bit since i thought i have tested it enough. The files are on my smb share.
When having it locally (on the JF server) it plays nicely without a bandwidth limit to the client (directplay).
When playing it from smb share -> buffering not above 5Mbps.
But i can't get over it, that on the one hand transcoding works flawlessly and on the other hand the bandwith to the share is fast enough with way above 200 Mbps.
Edit:
So when direct playing the file from the share (file streaming) i only get about 2-5 Mbps. Which leads to buffering since the avg. bitrate is about 9 Mbps.
When transcoding the file i get about 6Mbps avg. Which doesn't lead to too bad buffering, since the bitrate goes down too.
When downloading the file using 'cp' directly to the local storage i get over 100MBps.
Those numbers are from the JF server.
In conclusion this seems to be a smb issue of file streaming, not a jellyfin issue really.
When having it locally (on the JF server) it plays nicely without a bandwidth limit to the client (directplay).
When playing it from smb share -> buffering not above 5Mbps.
But i can't get over it, that on the one hand transcoding works flawlessly and on the other hand the bandwith to the share is fast enough with way above 200 Mbps.
Edit:
So when direct playing the file from the share (file streaming) i only get about 2-5 Mbps. Which leads to buffering since the avg. bitrate is about 9 Mbps.
When transcoding the file i get about 6Mbps avg. Which doesn't lead to too bad buffering, since the bitrate goes down too.
When downloading the file using 'cp' directly to the local storage i get over 100MBps.
Those numbers are from the JF server.
In conclusion this seems to be a smb issue of file streaming, not a jellyfin issue really.