overrun!!! (at least 12.465 ms long)57250kB time=00:51:43.34 bitrate=1471.0kbits/s speed= 1x
overrun!!! (at least 134.581 ms long)8560kB time=00:51:50.38 bitrate=1471.1kbits/s speed= 1x
overrun!!! (at least 42.422 ms long)59810kB time=00:51:56.95 bitrate=1471.3kbits/s speed= 1x
overrun!!! (at least 29.663 ms long)60949kB time=00:52:02.99 bitrate=1471.4kbits/s speed= 1x
overrun!!! (at least 108.499 ms long)2188kB time=00:52:09.53 bitrate=1471.6kbits/s speed= 1x
overrun!!! (at least 28.869 ms long)63422kB time=00:52:16.13 bitrate=1471.7kbits/s speed= 1x
I made a fork of his script so that it builds ffmpeg-rockchip and itās dependencies (libdrm, rkmpp, rkrgaā¦), as well as all the usual ffmpeg included codecs, instead of the minimal build.
Iāll share the repo here if in case itās of use to anyone (Iām aware that x264, x265 and probably svt-av1 might not be of much use on RK35xx devices in terms of encoding speed)
I installed the repository above
(git clone https://github.com/nyanmisaka/ffmpeg-rockchip.git)
Then when I ran the code to build it:
./build-ffmpeg --enable-gpl-and-non-free --build
But I received this message:
./build-ffmpeg: No such file or directory
It didnāt find the builder.
So I installed the original BUILDER that is in the GITHUB description:
git clone https://github.com/markus-perl/ffmpeg-build-script.git
Then, run the ./build-ffmpeg --enable-gpl-and-non-free --build
But after 4 hours of compiling it did not show the hardware acceleration libraries.
Firstly, it didnāt move the binaries to the root directory. I had to do it manually. After installed and running in PATH, when listing the encoders there is no encoder with hardware acceleration.
$ ffmpeg -hwaccels
Returns no acceleration methods!
What did I do wrong? Could you help me?
well its RGA, nobody is responsible for its bugs, but yeah that 1 px is funny, because i would expect the green offset in the same y offset and not finish in the half of the stride, yet i am also speculating.
Ahh that old one, yes but all of those fixes are also in ffmpeg-rockchip. It is no more in a comparible form with ffmpeg-rockchip, even though it works, it utilized lots lots of hacks and was basically doing everthing itself without relying ffmpeg, rga nor mpp, may be thats the reason it works so better not use that even though it works.
In my tests, ffmpeg received 1080p nv12 input from the following sources, and after applying the software format=yuv420p filter, it encoded fine and there is no green line on my end.
According to searching, /dev/video11 seems to be RK-ISP used by the camera. I donāt have the hardware to verify it, and canāt say for sure what quirks it contains.