Intel N100 fails converting high bitrate files

[nefariouslegion]

Hi,

I've just recently setup your tool and it's quite useful. But I've noticed with higher bitrate files (I tested with 10 second 4K game clips) that it fails almost immediately when trying to convert them.

For the failed conversions the log outputs this:

[vertd] [2026-04-28T00:05:51Z INFO  vertd::converter] running 'ffmpeg -hide_banner -loglevel error -progress pipe:1 -hwaccel vaapi -vaapi_device /dev/dri/renderD128 -hwaccel_output_format vaapi -i input/9cfe663b-0f81-4720-acd0-f1ad18a55f7c.mov -c:v h264_vaapi -pix_fmt yuv420p -level:v 5.2 -c:a aac -strict experimental -preset slow -b:v 141376540 -map_metadata 0 -map_chapters 0 output/9cfe663b-0f81-4720-acd0-f1ad18a55f7c.mp4'
[vertd] [2026-04-28T00:05:51Z ERROR vertd::converter] [h264_vaapi @ 0x55af4c15e2c0] No usable encoding profile found.
[vertd] [2026-04-28T00:05:51Z ERROR vertd::converter] [vost#0:0/h264_vaapi @ 0x55af4c15df00] Error while opening encoder - maybe incorrect parameters such as bit_rate, rate, width or height.
[vertd] [2026-04-28T00:05:51Z ERROR vertd::converter] Error while filtering: Function not implemented
[vertd] [2026-04-28T00:05:51Z ERROR vertd::converter] [out#0/mp4 @ 0x55af4c15d580] Nothing was written into output file, because at least one of its streams received no packets.
[vertd] [2026-04-28T00:05:51Z ERROR vertd::http::services::websocket] job 9cfe663b-0f81-4720-acd0-f1ad18a55f7c failed

But then when I convert a file that does work, like a 1080p file, I see this output in the log:

[vertd] [2026-04-28T00:33:58Z INFO  vertd::http::services::upload] uploaded file: 2022-02-20 21-37-37_Trim.mp4
[vertd] [2026-04-28T00:33:58Z INFO  vertd::converter] running 'ffmpeg -hide_banner -loglevel error -progress pipe:1 -hwaccel vaapi -vaapi_device /dev/dri/renderD128 -hwaccel_output_format vaapi -i input/d891592c-f6bc-476d-8625-f8c42474fe4e.mp4 -c:v h264_vaapi -c:a aac -strict experimental -preset slow -b:v 47796714 -map_metadata 0 -map_chapters 0 output/d891592c-f6bc-476d-8625-f8c42474fe4e.mkv'
[vertd] [2026-04-28T00:34:00Z INFO  vertd::http::services::download] all bytes successfully sent for output/d891592c-f6bc-476d-8625-f8c42474fe4e.mkv

One difference I noticed in those logs is that for the higher bitrate file it seems to specifically attempts to call h.264 VAAPI's -level:v 5.2. Whereas the successful 1080p conversion doesn't mention any level at all.

For reference this on a UGREEN DXP4800 Plus NAS with VA-API version: 1.22 (libva 2.21.0) and ffmpeg version 5.1.8-0+deb12u1. The vertd container is on ffmpeg version 6.1.1-3ubuntu5 but doesn't have the vainfo command. When I run a sudo vainfo on the host machine it outputs this bit in regards to h.264 supported profiles:

      VAProfileH264Main               : VAEntrypointVLD
      VAProfileH264Main               : VAEntrypointEncSlice
      VAProfileH264Main               : VAEntrypointFEI
      VAProfileH264Main               : VAEntrypointEncSliceLP
      VAProfileH264High               : VAEntrypointVLD
      VAProfileH264High               : VAEntrypointEncSlice
      VAProfileH264High               : VAEntrypointFEI
      VAProfileH264High               : VAEntrypointEncSliceLP

Also, 4K transcoding on Plex using the N100 works fine. So I'd think vertd should be able to do 4K conversions on it.