You will learn#
- what
E_NO_ENCODERsays and what was tried; - how to read the encoder check of the doctor;
- three ways out: the bundled FFmpeg, a hardware encoder and your own libx264 build.
The idea#
An export needs an H.264 encoder, and the product only trusts one that passed a real test encode on your machine. It tries, in order, h264_videotoolbox, h264_nvenc, h264_qsv, h264_amf, h264_mf, h264_vaapi and libopenh264; libx264 joins only when the FFmpeg is your own and VUKEM_VIDEO_ALLOW_USER_X264 is true. If none passes, the export fails with E_NO_ENCODER; the message lists each candidate and why it failed (not in this FFmpeg build, or the first line of its error). The detection is cached for 24 hours.
Quick start#
- Run
vukem-video doctor --full. Theffmpeg.encodercheck prints the chosen encoder and each candidate with its status and time, orE_NO_ENCODER. - Pick the way out that fits:
- use the FFmpeg that ships with Vukem Video (the container image and the installers), which includes OpenH264;
- install the driver of your GPU, so that a hardware encoder passes the test;
- point
VUKEM_VIDEO_FFMPEGat your own build that haslibx264and setVUKEM_VIDEO_ALLOW_USER_X264=true. The licence consequences are yours: do not redistribute it.
- Run the doctor again, then export.
vukem-video doctor --full
VUKEM_VIDEO_ALLOW_USER_X264=true vukem-video serveTo test one encoder only, set VUKEM_VIDEO_ENCODER to its FFmpeg name. Then only that one is tried and the product never swaps it silently.
Common mistakes#
- Forcing an encoder the machine does not have (
VUKEM_VIDEO_ENCODER=h264_nvencwithout an NVIDIA driver). - Setting
VUKEM_VIDEO_ALLOW_USER_X264=truewhile the FFmpeg is the bundled one:libx264is used only with your own FFmpeg. - Running in a container or a virtual machine without the device nodes that a hardware encoder needs. The OpenH264 encoder of the bundled FFmpeg needs none.
- Reading
E_FFMPEG_MISSINGas the same thing. See FFmpeg is not found.