Skip to content

various ffmpeg issues #51

Description

@d00m7985

I've noticed that AMD AMF erroneously reports that the encoders might be broken, and indeed, using the internal test input, it does break.

ffmpeg -hide_banner -loglevel error -f lavfi -i color=c=black:s=64x64:r=5:d=1 -frames:v 1 -c:v hevc_amf -f null -

Changing 64x64 to something bigger like 512x512 makes this work when testing outside of VapourBox.

I have also noticed that using CQP seems to break on amf for some reason (note, this is truncated).

...: ffmpeg exited with exit code -1073741819 [hevc_amf @ 000002a98d193cc0] VBAQ is not supported by cqp Rate Control Method, automatically disabled ...

I'm not sure if this is inherent to the codec or if there is something else going on behind the curtain as I seem to have no trouble using cqp in place of bitrate outside of VapourBox. If I could figure out how to mess around with the automated inputs, I might be able to fix this, but for right now, this is unfortunately not usable with anything out of any of my cameras (which is unfortunate because SMDegrain produces visually much more pleasing results than anything I can get working in DaVinci Resolve Studio). Using software renderers seems to sidestep this entirely, but it does kind of defeat hardware acceleration and drop render rates from ~80fps to ~0.1fps.

I have tried using some AHK compiles to try and trick this program into inputting things correctly (er.. maybe not correctly, but in a manner that doesn't make ffmpeg fall over on itself), and that did end up working.. once, then some internal mechanism for integrity verification reinstalls the dependencies and kills this bodge fix.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions