Use upstream ffmpeg as a base version and apply kodi patches via a
patchset.
This doesn't change the ffmpeg source code we build from ATM but
allows us to easily drop kodi patches if they cause issues, update
to a newer point release or test with different ffmpeg versions
in the future.
Signed-off-by: Matthias Reichl <hias@horus.com>
av1 patch is now included in kodi ffmpeg fork so we can drop it
from our local patches.
Only Amlogic still needs the patch as it doesn't use kodi ffmpeg
fork.
Signed-off-by: Matthias Reichl <hias@horus.com>
When testing ffmpeg / hardware decoders it's very convenient
if one can do that with ffmpeg instead of only kodi. Using the
same ffmpeg patches and options as used by kodi also reduces the
risk of testing a different version than what's used by LE/kodi.
As the ffmpeg binary is way too minimal for normal use and only
intended for internal testing this feature is disabled by default
and has to be explicitly requested by building with FFMPEG_TESTING=yes
In addition to ffmpeg and ffprobe binaries this enables the null muxer
and wrapped_avframe encoder so one can test with "-f null".
On RPi it also enables vout_drm (which is only included in jc's
tree / RPi ffmpeg patches) so "-f vout_drm" can be used, too.
Signed-off-by: Matthias Reichl <hias@horus.com>
Apply v4l2-drmprime and v4l2-request patches for all projects/devices
except RPi4 and use configure options to enable/disable the required
features.
The RPi4 patch already includes v4l2-request patches, so only add the
v4l2-drmprime patch in addition to that - this is needed for H264
hardware decoding.
RPi4 configure options have been adapted to the updated RPi patch.
Misc LibreELEC patches are now in the "libreelec" patch dir and
included for all projects/devices.
Signed-off-by: Matthias Reichl <hias@horus.com>
Matthias Reichl
Christian Hewitt
SupervisedThinking
CvH
CvH
smp79
heitbaum
Lukas Rusak