(2024-07-10, 03:03 PM)TheDreadPirate Wrote: Yeah. There is an issue in the WebOS app (not sure if its us or WebOS) that causes issues when we send fMP4. But fMP4 is required by WebOS for better HDR compatibility.
This is a known issue and is being worked on.
https://github.com/jellyfin/jellyfin-webos/issues/236
The related fix.
https://github.com/jellyfin/jellyfin-web/pull/5553
Awaiting this fix, and have turned off the fMP4 for the time being.
That said, I did have an odd issue that I have only experienced on a title that I had to turn off fMP4 for. The video would stop playing on its own and not go beyond a certain point. Only until I quit the application and restarted the video would it go beyond. It was a container remux only. The ffmpeg logs showed nothing, but I did find this in the main log around the time it happened. Unsure if related:
[2024-07-15 01:20:48.560 -04:00] [ERR] [9] Microsoft.AspNetCore.Server.Kestrel: Unexpected exception in TimingPipeFlusher.FlushAsync.
System.Net.Sockets.SocketException (10022): An invalid argument was supplied.
at System.IO.Pipelines.Pipe.GetFlushAsyncResult()
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Infrastructure.PipeWriterHelpers.ConcurrentPipeWriter.FlushAsyncAwaited(ValueTask
1 flushTask, CancellationToken cancellationToken)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Infrastructure.PipeWriterHelpers.TimingPipeFlusher.TimeFlushAsyncAwaited(ValueTask1 pipeFlushTask, MinDataRate minRate, IHttpOutputAborter outputAborter, CancellationToken cancellationToken)