SOLVED: Tracking/Starting Slow

SOLVED: Tracking/Starting Slow - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: Tracking/Starting Slow (/t-solved-tracking-starting-slow)

Pages: 1 2

RE: Tracking/Starting Slow - JellyEll - 2025-01-14

Now using QSV, this is the logs from Jellyfin. 2 attempts to play the same file, both on the same device (iPhone using Jellyfin app): https://pastebin.com/DDM8hVXY

First attempt at playing failed outright, second took ~22 seconds.

FFMPEG logs: https://pastebin.com/gz4pGiqU

Now using QSV (It seems I didn't save last time, after reading the logs)

Seems significantly faster right now (7s to load, I'm not sure how long people expect it to be), I'll do some more testing over the next 2 days. A precautiously optimistic thank you for all of your help.

For a quick once over, do these logs seem as they should?

Jellyfin logs: https://pastebin.com/ZrawuxEN
FFMPEG logs: https://pastebin.com/mAatDsRG

The container has access to all 4 cores

Code:
root@jellyfin-76d4d6768c-qqxj7:/# lscpu

Architecture:            x86_64

  CPU op-mode(s):        32-bit, 64-bit

  Address sizes:          39 bits physical, 48 bits virtual

  Byte Order:            Little Endian

CPU(s):                  4

  On-line CPU(s) list:    0-3

Vendor ID:                GenuineIntel

  Model name:            Intel(R) N100

    CPU family:          6

    Model:                190

    Thread(s) per core:  1

    Core(s) per socket:  4

    Socket(s):            1

    Stepping:            0

    CPU(s) scaling MHz:  85%

    CPU max MHz:          3400.0000

    CPU min MHz:          700.0000

    BogoMIPS:            1612.80

RE: Tracking/Starting Slow - TheDreadPirate - 2025-01-14

115fps on a transcode with subtitle burn-in is MUCH better and about right for an N100.

On my system, a transcode + subtitle burn-in takes like 3-5 seconds before playback starts. So 7 seconds to start playback is about right for an N100.

RE: Tracking/Starting Slow - JellyEll - 2025-01-14

Awesome, thank you.
Is there any tuning that can be done to make it faster? Or would it be upgrading the CPU that's the answer to quicker playback start times?

RE: Tracking/Starting Slow - TheDreadPirate - 2025-01-14

Upgrading would be the only way to get it faster than what you're seeing now. And even then, it isn't THAT much faster. 2-3 seconds faster at 3-5X the cost of your N100 system.

RE: Tracking/Starting Slow - JellyEll - 2025-01-14

This has definitely sped a lot up, thank you.

I'm struggling with a film, Oppenheimer, @ 4k (18GB/3hours). It stutters for ~20 seconds every ~20 seconds or so.
Would be icing on the cake to get this working, as I don't think the service has ever ran 4k films without stutter.

Can you see what the issue is, based on logs? I'm assuming the hardware is capable. The internet speed seems fast enough.

Jellyfin container logs:

Code:
[17:22:32] [INF] [34] Jellyfin.Api.Helpers.MediaInfoHelper: User policy for House. EnablePlaybackRemuxing: True EnableVideoPlaybackTranscoding: True EnableAudioPlaybackTranscoding: True

[17:23:44] [INF] [55] Emby.Server.Implementations.HttpServer.WebSocketManager: WS 10.42.0.1 closed

[17:23:45] [INF] [73] Emby.Server.Implementations.HttpServer.WebSocketManager: WS 10.42.0.1 request

[17:23:58] [INF] [90] Emby.Server.Implementations.HttpServer.WebSocketManager: WS 10.42.0.1 closed

[17:23:58] [INF] [90] Emby.Server.Implementations.HttpServer.WebSocketManager: WS 10.42.0.1 request

[17:24:06] [INF] [86] Emby.Server.Implementations.HttpServer.WebSocketManager: WS 10.42.0.1 request

[17:24:33] [INF] [90] Emby.Server.Implementations.HttpServer.WebSocketManager: WS 10.42.0.1 closed

FFmpeg.remux logs:
https://pastebin.com/ve1ynbEN

If I need to raise another thread, or if you can point me to things I should be looking at, thank you. I get you've helped me with my original problem!

RE: Tracking/Starting Slow - TheDreadPirate - 2025-01-14

The ffmpeg log you shared is for a Spider Man movie. Find the one for Oppenheimer, if there is one. If the jellyfin log snippet is from the Oppenheimer playback, it isn't transcoding.

If there is no ffmpeg log, I'd need to see the media info. In the Jellyfin UI click on the "..." context menu for Oppenheimer and click "Media Info". Click the copy icon at the top and share that info.

RE: Tracking/Starting Slow - JellyEll - 2025-01-14

In my eagerness to get the 4K question answered, I failed to test properly. It only buffers on the Jellyfin app on the TV I was testing with.
I've just tried via the iOS app and the laptop and it's running without any buffering. I think it may just be the TV that's having problems.

Thank you so much for all of your help - appreciate both of you for getting this up and running better.

RE: Tracking/Starting Slow - bitmap - 2025-01-14

One closing suggestion: if you can get functional text-based subtitles via the OpenSubtitles plugin for anything transcoding due to burning in subtitles, your performance will increase drastically because then you're looking at direct streaming for more clients.