if you just skip the part about the RPi’s hardware decoder, the rest of the instructions should also apply to the Vero.
What you will not get without further support from @sam_nazarko is de- and encoding in hardware as this is not part of the standard ffmpeg. So don’t expect video processing in real time.
thanks @sam_nazarko - i dont know enough osmc and building from source to know whats going wrong, but i cloned the git repo and tried a ./configure and make and got the following:
git clone git://github.com/osmc/libamcodec/
cd libamcodec/
/sources/libamcodec/amffmpeg$ ./configure
libavutil/avconfig.h is unchanged
WARNING: unknown architecture aarch64
osmc@osmcmoneykings:~/sources/libamcodec/amffmpeg$ make
libavcodec/Makefile:695: /home/osmc/sources/libamcodec/amffmpeg/libavcodec/aarch64/Makefile: No such file or directory
make: *** No rule to make target '/home/osmc/sources/libamcodec/amffmpeg/libavcodec/aarch64/Makefile'. Stop.
$setarch ./configure
$make
In file included from libavformat/CacheHttp.c:26:0:
libavformat/internal.h:26:27: fatal error: amconfigutils.h: No such file or directory
#include "amconfigutils.h"
compilation terminated.
common.mak:31: recipe for target 'libavformat/CacheHttp.o' failed
make: *** [libavformat/CacheHttp.o] Error 1
Edit: If you clone the whole thing, the missing header is under amavutils/include.
Edit 2 : Maybe I’ve jumped the gun a bit. I see that you cloned some source code from OSMC. Nevertheless, the missing headers are in the location I linked to.
Are you sure you have the hardware acceleration that you need?
On the Pi it uses the openmax (omx) encoder, but that’s most likely incompatible with the AMLogic hardware of the 4K. There’s no reference to openmax or omx on the page you linked to, so I’m guessing everything will be running in the CPU.
Yes, please do post or pm them. Best would be a full log including the commands you used, so I can adjust the instruction page.
Having watched this I don’t see where you would need ffmpeg at all. If you just stick to the walk through, the recording profile is all default which means, no de- or encoding whatsoever. When you record a stream, the data is simply passed to disk, when you watch live or recorded TV, the decoding is all handled by Kodi.
ffmpeg only comes into play if you try things like I described in the tutorial. A nice toy – at least for me – but far from necessary.
Hi,
I’ve a question: can i use my vero 4K to convert h264 in hevc? With ffmpeg i can convert from command line, but the hardware? Is it possible? Thanks
I am trying to follow this but can’t seem to compile. At the very end I ran make install and it failed trying to find a header. Can we get a How-To on how to install amffmpeg on a Vero 4K/4K+?