I would like to claim: If you have issues with that fork of ffmpeg, why
don't you ask there? (Honest question.) That said, that repo isn't even
a proper fork, so it's hard to understand what they changed...but okay.
It's apparently based on a quite old version of ffmpeg, so you'll have
an extremely hard time getting support here. For all we know, any
issues may have been fixed in a long time!
You order of inputs and outputs in the third command line confuses me.
It might work (does it), but I expect
$ ffmpeg [input options] -i input [output options] output
Have you tried:
$ ffmpeg -i /dev/video0 -f null -
with the Cedrus version (skipping the special encoder)?
http://linux-sunxi.org/FFmpeg where the Cedrus patch comes from recommends this:
$ ffmpeg -f v4l2 -video_size 640x480 -i /dev/video0 [...]
Have you tried that?
> Then I uninstall and reinstall ffmpeg from armbian, so I can test if my webcam itself is to blame. I see this works correctly, but it does not have the options -c:v cedrus264 and -vewait:
> cedric@bananapi:~/new/FFmpeg-Cedrus$ ffmpeg -b:v 1000k -f h264 test.h264 -i /dev/video0
> ffmpeg version 2.8.14-0ubuntu0.16.04.1 Copyright (c) 2000-2018 the FFmpeg developers
This is extremely old. Can you get hold of a newer binary build for
armbian? ffmpeg-4.0 or recent ffmpeg git, if possible.
> Where can I get a version of ffmpeg that uses the h264 hardware encoder for the Allwinner A20 SOC on the bananapi?
Assuming that Cedrus code used to work - http://linux-sunxi.org/FFmpeg hints that is was experimental and is unmaintained - you could try to
port their changes to recent ffmpeg. The feasibility of this would be
easier to check if those guys&gals had made it clear which version of
ffmpeg their code is based on[*]. Sigh.
On Mon, May 14, 2018 at 16:27:48 +0200, Moritz Barsnick wrote:
> Assuming that Cedrus code used to work - http://linux-sunxi.org/FFmpeg > hints that is was experimental and is unmaintained - you could try to
> port their changes to recent ffmpeg. The feasibility of this would be
> easier to check if those guys&gals had made it clear which version of
> ffmpeg their code is based on[*]. Sigh.