BillsMediaServe 1 Posted November 10, 2021 Share Posted November 10, 2021 Hello friends I have experienced this problem several times before and just worked around it. I have an H.264 video that I know works fine on my Nvidia Shield running Emby as well as my Android cell phone running Emby. The problem lies with my main TV which is an LG. Emby on this Tv roles its circle of doom for ever and will not play this video. Now I can't be 100% sure that the other videos that wouldn't play were the same type but I was hoping that someone could read my log file from the server I have. The Nas that I run Emby on is a Synology, DS920+, specifically. I see that the log file is labeled ffmpeg-transcode. Could this mean that Emby can not transcode to the LG Tv properly? I would much appreciate the help of anyone who may have experienced this problem before on an LG Tv or even other Tv's. Thank you in advanced ffmpeg-transcode-f0cab5bc-6c3e-4847-8261-3b5ba1f45047_1.txt Link to comment Share on other sites More sharing options...
SamES 880 Posted November 10, 2021 Share Posted November 10, 2021 As a test, can you try disabling hardware acceleration in transcoding settings and see if that makes a difference? @softworkz, can you please shed any light on what would cause these errors, see previously attached transcode log 22:18:08.156 [subtitles@f1 @ 0x1d2f500] Shaper: FriBidi 1.0.10 (SIMPLE) 22:18:08.165 [subtitles@f1 @ 0x1d2f500] Loading font file '/var/packages/EmbyServer/var/fonts/NotoSansFallback.ttf' >> ThrottleBySegmentRequest: Latest request position unknown 22:18:08.892 [subtitles@f1 @ 0x1d2f500] Using font provider fontconfig >> ThrottleBySegmentRequest: Latest request position unknown >> ThrottleBySegmentRequest: Latest request position unknown >> ThrottleBySegmentRequest: Latest request position unknown >> ThrottleBySegmentRequest: Latest request position unknown >> ThrottleBySegmentRequest: Latest request position unknown >> ThrottleBySegmentRequest: Latest request position unknown >> ThrottleBySegmentRequest: Latest request position unknown >> ThrottleBySegmentRequest: Latest request position unknown >> ThrottleBySegmentRequest: Latest request position unknown >> ThrottleBySegmentRequest: Latest request position unknown >> ThrottleBySegmentRequest: Latest request position unknown >> ThrottleBySegmentRequest: Latest request position unknown >> ThrottleBySegmentRequest: Latest request position unknown >> ThrottleBySegmentRequest: Latest request position unknown >> ThrottleBySegmentRequest: Latest request position unknown >> ThrottleBySegmentRequest: Latest request position unknown >> ThrottleBySegmentRequest: Latest request position unknown >> ThrottleBySegmentRequest: Latest request position unknown >> ThrottleBySegmentRequest: Latest request position unknown >> ThrottleBySegmentRequest: Latest request position unknown >> ThrottleBySegmentRequest: Latest request position unknown Link to comment Share on other sites More sharing options...
Solution softworkz 3301 Posted November 10, 2021 Solution Share Posted November 10, 2021 @Campsight - Can you try to disable subtitles before starting playback? @SamES - It means that no further segment has been requested yet by the client (probably because we didn't even manage to get out the first one at all) 1 1 Link to comment Share on other sites More sharing options...
BillsMediaServe 1 Posted November 10, 2021 Author Share Posted November 10, 2021 Thanks Softworkz I remembered having to disable the subtitles once before to remedy the problem. In my future attempts to solve similar problems it will be the first thing I try. If that was unclear to anyone having the same problem, I needed to disable the subtitles. You don't have to permanently disable all subtitles, just do the movie you're watching. Cheers and thanks again 1 Link to comment Share on other sites More sharing options...
softworkz 3301 Posted November 10, 2021 Share Posted November 10, 2021 Thanks for confirming, but that's not all. I got even better news: Slow transcoding startup with subtitle-burn in (especially with video files on network storage) has been a long-standing issue, but it is finally fixed right in the current beta (4.7.0.17) So if you want, you could give that a try. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now