![]() |
Freeze when jumping timeline on web browser - 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: Freeze when jumping timeline on web browser (/t-freeze-when-jumping-timeline-on-web-browser) |
RE: Freeze when jumping timeline on web browser - Chaperone - 2025-01-05 Yes, I have it set like: Code: volumes: And now, I switched to: Code: volumes: And the issue still the same. RE: Freeze when jumping timeline on web browser - Chaperone - 2025-01-06 I made a completely new installation of versions:
Using:
No config inside Jellyfin. All the defaults, including the transcoding. Which means "Hardware acceleration: None". And I get exactly the same behavior on the web browser. The dockercompose.yml is the following:Code: services: Any other ideas to try? Thanks! RE: Freeze when jumping timeline on web browser - TheDreadPirate - 2025-01-06 I'm out of ideas. Sorry. RE: Freeze when jumping timeline on web browser - Chaperone - 2025-01-06 (2025-01-06, 08:24 PM)TheDreadPirate Wrote: I'm out of ideas. Sorry. ![]() Thank you! Just let me know if you can think about something else. RE: Freeze when jumping timeline on web browser - Chaperone - 2025-02-17 I installed versión 10.7.7, as recommended by https://www.reddit.com/r/jellyfin/comments/vtari3/comment/if6efiz/, and it works. Time scrolling works perfect. Hardware transcoding works. I don't know what's different from the latest version... But now works. A direct play now looks like: Code: Playback Info And when transcoding because of resize: Code: Playback Info My docker-compose.yml is the following:Code: services: The Playback > Transcoding I have it set as:
Any ideas what could be wrong when I try to update the container? RE: Freeze when jumping timeline on web browser - Chaperone - 2025-02-20 Here is an example, playing an audio FLAC. Notice the playback position blue dot, is outside the lighter area of the audio. If I move the cursor to the lighter (cached) part of the timeline, the music plays... But if I move the cursor outside that lighter area, there is no music. And I have to wait for a few long seconds for the player to fill below where the cursor is. ![]() The same happen with video but takes longer to fill the timeline below the cursor. Also, notice the other pages from Jellyfin, are not working as intended when the playback is "halted". This is the media information: ![]() RE: Freeze when jumping timeline on web browser - TheDreadPirate - 2025-02-20 Revisiting what we've already posted, I didn't ask whether you are using a reverse proxy or not. RE: Freeze when jumping timeline on web browser - Chaperone - 2025-02-20 @TheDreadPirate, thank you. You had found my problem. At the very beginning, I have Jellyfin not thru a reverse proxy. Because was so great, I added Jellyfin to the Synology DSM reverse proxy. Later, I pointed Jellyfin to a Cloudflare Tunnel. In conclusion, it's been working wrong since the Synology DSM reverse proxy, and worst since the Cloudflare Tunnel. Now, I can move the cursor over the timeline on my Windows Edge browser, on my Samsung Tizen tv, and on my iPhone. Also, now on Firefox, I can use the Hardware transcoding. ![]() Thank you! RE: Freeze when jumping timeline on web browser - TheDreadPirate - 2025-02-20 Cloudflare tunnels can definitely cause weird issues. It is also against Cloudflare's TOS to serve streaming media through their free tier tunnel service. So definitely don't do that. But a misconfigured reverse proxy can also cause issues. Are you able to tell how the reverse proxy was configured? Caching on the proxy can cause weird behaviors in Jellyfin. RE: Freeze when jumping timeline on web browser - Chaperone - 2025-02-20 On my Synology NAS (DS216+II), I had the reverse proxy set like: ![]() ![]() On Cloudflare, I had set a Cloudflare Tunnel. I was using a Docker container to run the Cloudflared application. But as you said, it is not recommended. Now I realize, when I had the Synology reverse proxy was working not as bad as when I had the Cloudflare Tunnel. Again, thank you for your kind support. |