Issues with seeking - 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: Issues with seeking (/t-issues-with-seeking) |
Issues with seeking - phoenixz - 2023-06-19 Hi there, First of all, congrats on the new forum away from Reddit, great move. Second, thanks for an AWESOME product, Jellyfin is all sorts of amazing I do, however, have some issues, and for this post I'll limit myself to the issue with seeking. Whenever I start a movie or show, I let it play for, say, 5 minutes, and I want to skip to to 30 minutes, I click on the seek bar, move it to 30 minutes. That moooostly seems to work, but with certain media (especially on casting) it may just kick back to 0 and start over. Say that that does work, but now I see I went ahead too far, and I want to go back to 20 minutes. So I do the same again, drag the seek bar to 20 minutes. MOST of the time, it will now kick back to 30 minutes again and continue there. Sometimes I may have video from 20 minutes and audio from 30 minutes, it becomes messy. Sometimes if I seek after that 30 minutes point, it seems to take it, and if I drag it all to 0 it sometimes picks that up and starts from 0. Most of the time though, it will just outright refuse to seek anywhere but that 30 minutes marker. This problem seems to be worse on mobile, and outright unusable when casting video to a TV. When using casting I simply wont seek because that is just "the end" of watching anything at all. Edit: Also, using the "skip ahead" button should skip maybe 10-30 seconds, but especially on mobile, may skip 5-10 minutes ahead which is way too much Is this seeking stuff a known problem, and is there something I can do to improve these issues? Have a great one everybody! RE: Issues with seeking - skribe - 2023-06-20 Can you provide a little more information on your configuration? This issue is most typically caused by either slower media storage or inadequate transcoding resources. If you can describe your setup in more detail it may provide clues. Your server log and any relevant ffmpeg logs could also be helpful. Both can be found in the logs section of your server dashboard. |