![]() ![]() End of stack trace from previous location where exception was thrown -Īt .ThrowForNonSuccess(Task task)Īt .HandleNonSuccessAndDebuggerNotification(Task task)Īt .ProgressiveStreamWriter.d_3.MoveNext()Īt .ProgressiveStreamWriter.d_0.MoveNext()Ģ1:06:48.9210 Debug - HttpServer: HTTP Response 500 to 192.168.0.159:43913. The specified network name is no longer availableĪt (IAsyncResult asyncResult)Īt System.IO.Stream.b_17(Stream stream, IAsyncResult asyncResult)Īt `1.FromAsyncTrimPromise`1.Complete(TInstance thisRef, Func`3 endMethod, IAsyncResult asyncResult, Boolean requiresSynchronization) Response time: 54.003 msĢ1:06:48.8850 Error - App: Error streaming media Here's the relevant portion of the Media Browser Server log file (full version attached):Ģ1:06:47.4049 Info - App: C:\Users\BobaFett\AppData\Roaming\MediaBrowser-Server\ffmpeg\old\20140105\ffmpeg.exe -fflags genpts -i file:"M:\MB3\Shared\Disney\Brave (2012). Thus I suspect this is a Media Browser bug. ![]() So the WD TV is certainly capable of directly playing the videos that are failing without any transcoding, but Media Browser appears to be attempting to transcode them anyway, and for some reason it immediately kills the FFmpeg process - even though FFmpeg doesn't throw any errors or abend.Ĭuriously, if I copy the FFmpeg command that Media Browser tries to run and run it manually in command prompt, it works like a charm. However, I routinely stream and videos over DLNA using Serviio and they play fine without issue. According to the WD TV Live's User Manual, appendix page 211, the device supports a maximum of 1920×1080p30 w/ a bit rate of HD:40. Most of the videos that fail to play are or L5.1, but a few are L4.0. ![]() My entire library is MKV / H.264 encoded with HandBrake, ranging from High Profile Level 4.0 to 5.1. Please see the User Manual for a list of supported file formats."Ĭontrary to what the above message says, my WD TV can indeed play the video file as-is without transcoding (see below). ![]()
0 Comments
Leave a Reply. |