video optimizer Hardware Acceleration "None" in all backends

[SquintyG33Rs]

clearly FFMPEG is installed and detected correctly because everything does work. but it does software encode and decode on the CPU. I'm on an AM4 ryzen CPU with a multiple dedicated GPU of different generations tested that all support a hardware accelerated encoder.

The newest card should have H265 and AV1 according to the specsheet but even the oldest card I tried GTX 1070Ti has at least H264.
None of them get detected by krokiet on any of the backends. And OBS has no problems with hardware acceleration on my system.

there doesn't seem to be any discussion thread about this so I must be doing something wrong?
there's no way everyone here is happily using this at the speed the CPU can process all these files.

[widechaos]

I'd check the FFmpeg encoder probe first. In current Krokiet source, the dropdown contains None plus the encoders that pass a test encode. Detecting ffmpeg successfully only establishes that ffmpeg -version runs.

For NVIDIA, the probe tries one H.264 frame with h264_nvenc, discards stderr, and rejects a failure or a run taking over five seconds. You can expose the error by running this in the same environment you use to launch Krokiet:

ffmpeg -nostdin -f lavfi -i "color=size=128x128:rate=1" -frames:v 1 -c:v h264_nvenc -f null -

This generates a test frame and writes no video file. Unknown encoder 'h264_nvenc' points to the FFmpeg build missing that encoder. If it recognizes the encoder but fails during initialization, the stderr should narrow down the driver/device problem. If it succeeds promptly while Krokiet still offers only None, check whether Krokiet resolves a different ffmpeg executable or runs in a different package/sandbox environment.

The detection probe uses H.264 even if you intend to encode HEVC or AV1.

Could you share the probe's stderr, your OS, Krokiet version, and how you installed it? I haven't reproduced this on your hardware; those details would distinguish a failed encoder probe from a Krokiet detection issue.

[SquintyG33Rs]

if I run the command as you suggest I get an error on the requested size.

Input #0, lavfi, from 'color=size=128x128:rate=1':
  Duration: N/A, start: 0.000000, bitrate: N/A
  Stream #0:0: Video: wrapped_avframe, yuv420p, 128x128 [SAR 1:1 DAR 1:1], 1 fps, 1 tbr, 1 tbn
Stream mapping:
  Stream #0:0 -> #0:0 (wrapped_avframe (native) -> h264 (h264_nvenc))
[h264_nvenc @ 0000025fd4110c40] InitializeEncoder failed: invalid param (8): Frame Dimension less than the minimum supported value.
[vost#0:0/h264_nvenc @ 0000025fd410f1c0] [enc:h264_nvenc @ 0000025fd40d8fc0] Error while opening encoder - maybe incorrect parameters such as bit_rate, rate, width or height.
[vf#0:0 @ 0000025fd412bb00] Error sending frames to consumers: Invalid argument
[vf#0:0 @ 0000025fd412bb00] Task finished with error code: -22 (Invalid argument)
[vf#0:0 @ 0000025fd412bb00] Terminating thread with return code -22 (Invalid argument)
[vost#0:0/h264_nvenc @ 0000025fd410f1c0] [enc:h264_nvenc @ 0000025fd40d8fc0] Could not open encoder before EOF
[vost#0:0/h264_nvenc @ 0000025fd410f1c0] Task finished with error code: -22 (Invalid argument)
[vost#0:0/h264_nvenc @ 0000025fd410f1c0] Terminating thread with return code -22 (Invalid argument)
[out#0/null @ 0000025fd40d5f00] Nothing was written into output file, because at least one of its streams received no packets.
frame=    0 fps=0.0 q=0.0 Lsize=       0KiB time=N/A bitrate=N/A speed=N/A elapsed=0:00:00.31
Conversion failed!

if i just change the size to 1080p it's gone (I've also checked 480p and 256x256 successfully).

Input #0, lavfi, from 'color=size=1920x1080:rate=1':
  Duration: N/A, start: 0.000000, bitrate: N/A
  Stream #0:0: Video: wrapped_avframe, yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 1 fps, 1 tbr, 1 tbn
Stream mapping:
  Stream #0:0 -> #0:0 (wrapped_avframe (native) -> h264 (h264_nvenc))
Output #0, null, to 'pipe:':
  Metadata:
    encoder         : Lavf63.1.102
  Stream #0:0: Video: h264 (High), yuv420p(tv, progressive), 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 2000 kb/s, 1 fps, 1 tbn
    Metadata:
      encoder         : Lavc63.1.102 h264_nvenc
    Side data:
      CPB properties: bitrate max/min/avg: 0/0/2000000 buffer size: 4000000 vbv_delay: N/A
[out#0/null @ 0000025afcf092c0] video:1KiB audio:0KiB subtitle:0KiB other streams:0KiB global headers:0KiB muxing overhead: unknown
frame=    1 fps=0.0 q=8.0 Lsize=N/A time=-00:00:02.00 bitrate=N/A speed=N/A elapsed=0:00:00.62

I don't know why I would be the only one seeing this error with the way krokiet checks ffmpeg hardware?
I guess I should I file this as a bug then. Hardware encoding PR was in April does it work for your system?

I don't want to have to build from source. I'm not setup with the rust tools. but I guess it's my only immediate option😅?

[widechaos]

Yes, I'd report this as a hardware-detection bug. Your results narrow it down: h264_nvenc rejects the 128×128 probe but succeeds at 256×256 and 1920×1080. The current Krokiet probe still uses 128×128 and discards stderr. If your installed build uses that probe, it can reject an encoder that works at larger frame sizes.

I haven't tested NVIDIA hardware, so I can't answer whether that April change works on your GPU. Reporting this doesn't require installing Rust. Include both command outputs, your GPU/driver, Krokiet version and FFmpeg build; the larger-frame success is useful evidence. A larger test frame looks worth testing in Krokiet, but I haven't verified a patched build or a binary workaround.