Media player is slow/clunky compared to jellyfin. Sometimes crashing entirely.

[indigo cedar]

OS: Android
Streamyfin Version: 0.28.0

Hi, just learned of streamyfin today and it seems perfect for what I want. The problem is when actually playing video back it's very laggy and clunky for some reason compared to jellyfin. Sometimes it even crashes the app (happened 2 times) or just freezes completely.

The seeker at the bottom also sometimes isn't in sync. Will say it's at the Beggining of playback meanwhile the video is halfway through.

The problem is constant on my tablet and my phone. The video was taken on my tablet.

The video shows jellyfin being a lot more responsive.

Both servers are connected over the internet. One does not have a local IP advantage.

Thanks in advance for any help!

https://imgur.com/a/t82m47Z

[green girder]

Hi there Chris, just to confirm this is when you are transcoding if I'm correct? I've noticed this as well when transcoding. If you use "max" it doesn't do that correct?

[indigo cedar]

This was transcoding yes. I'm having trouble testing "max" properly because my server upload speed I feel messes things up on both. I'll try find a similar bitrate file and check with direct play. I do feel like direct play has similar lag but tbf I can't be 100% right now.

[indigo cedar]

I've just tested on my local lan ip so I can compare with direct play. It does seem to be an issue only whilst transcoding.

Direct play is as snappy as expected. Whilst transcoding, if I seek it just freezes.

[green girder]

I think it might be a VLC issue (it's the player used in the app) To verify are you possibly able to run the android emulator, as we log the transcode url that you could then use with the VLC app to test with. Otherwise I'll see how you can "build" a url to paste as a stream url for VLC

[green girder]

Okay if you can download vlc player app. Then do the following:

Open the app, and once through to the home screen navigate to the more section and you should see streams, open it and then do the following tests:

1. Direct play stream : https://your-hostname/Videos/video-id/stream?static=true&container=mp4&mediaSourceId=video-id&subtitleStreamIndex=2&audioStreamIndex=1&api_key=api-key&startTimeTicks=0&maxStreamingBitrate=&userId=your-userId
2. current transcode url: https://jelly.homenetwork-sa.dedyn.io/videos/video-id/master.m3u8?MediaSourceId=video-id&VideoCodec=h264&AudioCodec=aac,mp3,ac3,dts&AudioStreamIndex=1&SubtitleStreamIndex=2&VideoBitrate=7808000&AudioBitrate=192000&MaxFramerate=23.976025&PlaySessionId=7d5add11acc445ce82076196bd269e0d&api_key=api-key&SubtitleMethod=Encode&RequireAvc=false&EnableAudioVbrEncoding=true&Tag=7a1f46c3f66942958b4feb5ae3fc177a&SegmentContainer=mp4&BreakOnNonKeyFrames=False&h264-level=41&h264-videobitdepth=8&h264-profile=high&TranscodeReasons=ContainerBitrateExceedsLimit
3. new transcode url: https://jelly.homenetwork-sa.dedyn.io/videos/video-id/master.m3u8?MediaSourceId=video-id&VideoCodec=h264&AudioCodec=aac,mp3,ac3&AudioStreamIndex=1&SubtitleStreamIndex=2&VideoBitrate=7872000&AudioBitrate=128000&MaxFramerate=23.976025&PlaySessionId=2b16d995059946029d0946f74c7dc9e2&api_key=api-key&SubtitleMethod=Encode&RequireAvc=false&EnableAudioVbrEncoding=true&Tag=7a1f46c3f66942958b4feb5ae3fc177a&SegmentContainer=ts&BreakOnNonKeyFrames=False&h264-level=41&h264-videobitdepth=8&h264-profile=high&TranscodeReasons=ContainerBitrateExceedsLimit

It could be because we are using mp4 when transcoding and should maybe be using ts instead, of course you'll have to get a video id and api key from your server, the rest of the values I think you could remove i.e the sessionID etc. but if option 3 gives a smoother experience then it's a quick fix for us to push a change for