ffmpeg64.exe has a return code of 1.

[Nadahar]

The "return code of 1" is about as informative as "general error". It just means that something went wrong. So, one would need to study it further to see what it is that goes wrong - chances are that FFmpeg outputs a hint, but you'd probably be in "trace" mode for it to be logged.

[Nadahar]

I took a quick look at the log, but it's not immediately clear to me what goes wrong. It seems to be some issue with the Windows pipe being used. UMS claims that the pipe has been created and is ready for use, while FFmpeg claims that it doesn't exist. It could mean that FFmpeg doesn't have the permissions needed to write to the pipe, but I'm not sure exactly how permissions work for pipes.

First the claim that the pipe has been created:

Code: Select all

DEBUG 2020-02-11 21:01:12.025 [HTTPv2 Request Worker 12] net.pms.io.WindowsNamedPipe Creating pipe \\.\pipe\ffmpegvideo_102_1581454872024
DEBUG 2020-02-11 21:01:12.027 [Thread-798] net.pms.io.WindowsNamedPipe Waiting for Windows names pipe connection "\\.\pipe\ffmpegvideo_102_1581454872024"
DEBUG 2020-02-11 21:01:12.453 [Thread-798] net.pms.io.WindowsNamedPipe Result of \\.\pipe\ffmpegvideo_102_1581454872024: true
TRACE 2020-02-11 21:01:12.528 [HTTPv2 Request Worker 12] net.pms.dlna.DLNAResource Sleeping for 2500 milliseconds
DEBUG 2020-02-11 21:01:12.715 [ffmpeg64.exe-262] net.pms.io.ProcessWrapperImpl Reading pipe: \\.\pipe\ffmpegvideo_102_1581454872024

Then FFmpeg's claim that it doesn't exist:

Code: Select all

DEBUG 2020-02-11 21:01:12.806 [ffmpeg64.exe-262-2] net.pms.io.OutputTextLogger \\.\pipe\ffmpegvideo_102_1581454872024: No such file or directory

It's especially strange if this behavior isn't consistent, if it takes a number of hours to start happening. I have no idea what might be causing this at the moment, maybe it's an issue "outside of UMS" (Java/Windows) or maybe it's interference by anti-virus software or unusually strict permissions somewhere. I really don't know what to think.

[Nadahar]

I'm not sure of the details, but problems that aren't there after installation but appears after the first reboot is something the more recent versions of UMS is plagued with. I would try an older version to see if the problem goes away.