Transcode failures on DS415+ after 4.4.1.0-1 update

[mechalas 0]

Updated emby on my Synology DS415+ yesterday and transcoding broke completely. I checked out the logs, and it looks like there's an issue with the FFmpeg version:

17:35:24.410 [h264 @ 0xa794c0] data partitioning is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.
17:35:24.410 [h264 @ 0xa794c0] If you want to help, upload a sample of this file to ftp://upload.ffmpeg.org/incoming/ and contact the ffmpeg-devel mailing list. (ffmpeg-devel@ffmpeg.org)
17:35:24.410 [h264 @ 0xa794c0] data partitioning is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.
17:35:24.410 [h264 @ 0xa794c0] If you want to help, upload a sample of this file to ftp://upload.ffmpeg.org/incoming/ and contact the ffmpeg-devel mailing list. (ffmpeg-devel@ffmpeg.org)
17:35:24.410 [h264 @ 0xa794c0] data partitioning is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.
17:35:24.410 [h264 @ 0xa794c0] If you want to help, upload a sample of this file to ftp://upload.ffmpeg.org/incoming/ and contact the ffmpeg-devel mailing list. (ffmpeg-devel@ffmpeg.org)
17:35:24.410 [h264 @ 0xa794c0] no frame!
17:35:24.410 [h264 @ 0xa794c0] non-existing PPS 0 referenced
17:35:24.410 [AVBSFContext @ 0xa87fc0] Invalid NAL unit 25, skipping.
17:35:24.410 [h264 @ 0xa794c0] Invalid NAL unit 25, skipping.

The suggestion to upgrade FFmpeg sounds great, if only there was an easy way to do that.

 

This is using the Web player. The system in question does not have direct access to the files (though if I download them they play just fine).

[mechalas 0]

Full log attached.

xcodelog.txt

Edited April 7, 2020 by mechalas

[Luke 37065]

Hi, yes, this is a known issue with m4v files. We'll be getting a 4.4.2 update out to resolve it. Thanks for the feedback.