2023-12-31, 01:39 AM
(This post was last modified: 2023-12-31, 01:40 AM by tmsrxzar. Edited 1 time in total.)
need to address each individually
ffmpeg logs will only be generated when transcoding
for the browser;
when the browser is asking for transcoding, the ffmpeg log then should be available for when the browser is stuttering
my expectation is that log will show a low framerate from ffmpeg when encoding because of the lack of GPU acceleration, the server load will likely show high usage to accompany this
(sidenote: in my experience browsers are terrible jellyfin clients and an official should be installed when able)
for the shield;
if it is direct streaming there will not be an ffmpeg log generated, this is what needs to be confirmed to isolate the issue to either client side or server side
if it is truly direct playing and not transcoding then it will be client side and then things on the client side need to be looked at
some reports on android regarding DTS on shield causing stuttering but typically more pronounced than the occasional you are reporting
ffmpeg logs will only be generated when transcoding
for the browser;
when the browser is asking for transcoding, the ffmpeg log then should be available for when the browser is stuttering
my expectation is that log will show a low framerate from ffmpeg when encoding because of the lack of GPU acceleration, the server load will likely show high usage to accompany this
(sidenote: in my experience browsers are terrible jellyfin clients and an official should be installed when able)
for the shield;
if it is direct streaming there will not be an ffmpeg log generated, this is what needs to be confirmed to isolate the issue to either client side or server side
if it is truly direct playing and not transcoding then it will be client side and then things on the client side need to be looked at
some reports on android regarding DTS on shield causing stuttering but typically more pronounced than the occasional you are reporting