-
-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not able to seek #208
Comments
I have this as well. Seeking works on other devices! |
I also have this issue. Seeking works fine on other web players (e.g. chrome) |
Oh! I thought I found the answer here but it seems that it was in another forum. To solve this you unfortunately for now need to disable the mp4-hevc option that you can set personally for each user on each device. So for webos you have to keep it off. I know it’s strange since it should be supported. I don’t really know exactly when it was useful to activate though, perhaps for some HDR content on some specific codecs. But keep it off and you shall seek, and seek and seek! |
@Smirra Can you possibly post a screenshot? I can't find the setting! |
@ChrisRosser |
@Smirra This was already disabled for me... |
@ChrisRosser ah! Did you check this from your tv? It is unique for every device |
Yes, it's unticked on the TV
…On Sun, 21 Apr 2024, 16:35 Smirra, ***@***.***> wrote:
@ChrisRosser <https:/ChrisRosser> ah! Did you check this from
your tv? It is unique for every device
—
Reply to this email directly, view it on GitHub
<#208 (comment)>,
or unsubscribe
<https:/notifications/unsubscribe-auth/AJ7G7Y2TUKXEOJYPDXU57A3Y6PMF5AVCNFSM6AAAAABENFTIISVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRYGA4DOMJRHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@ChrisRosser I see. Well then it must be something else. What LG TV do you have? What hardware is your jellyfin on? |
I have a G3. The server is running on a Intel 1340p mini pc with heaps of
horsepower.
…On Sun, 21 Apr 2024, 19:22 Smirra, ***@***.***> wrote:
@ChrisRosser <https:/ChrisRosser> I see. Well then it must be
something else. What LG TV do you have? What hardware is your jellyfin on?
—
Reply to this email directly, view it on GitHub
<#208 (comment)>,
or unsubscribe
<https:/notifications/unsubscribe-auth/AJ7G7Y5GWUSRR4GRB3LHFN3Y6P7XPAVCNFSM6AAAAABENFTIISVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRYGE2TKNZZGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Ok, hmmmm. You have really great specs on the integrated graphics ( my server only runs UHD 630) and a TV of the same generation as me. Then I can only suggest that you doublecheck the logs for anything out of the ordinary. Also check this video from lg about how to free up more of the memory, since the tvs are a little weak on the memory-side: https://youtu.be/mzKbRMCuYko?si=KUPpCsjui7QfcjzI. Maybe also make sure that the ffmpeg buffering/chache is written to a SSD. It writes buffering even during many direct streams and the chunks are written to a sub path under the "config"-location and not "cache" as one may think. But that's all I can think about.
Also the unstable jellyfin-versions are Mega unstable for transcoding.
|
This worked for me fwiw |
I noticed lately a lot of video files I have are not able to be seeked into on the LG WebOS app. They always start at the beginning and trying to seek just doesn't do anything.
If I load the video in the Windows Jellyfin client, it works fine and I can seek. On Windows, I checked playback info and it shows:
ffprobe looks like this:
The text was updated successfully, but these errors were encountered: