Help with Custom FFmpeg version

[SevenViewSolutions]

Say I have a forked version of FFmpeg that I want to use with this FFmpegKit, any idea or guidance on how to use that custom FFmpeg version with this project? I'm looking to use it with iOS and tvOS.

This was asked before but no response.

TIA!

[tanersener]

The FFmpeg version used by the build scripts is specified by this line . To build a different version of FFmpeg with FFmpegKit, simply update this line with the desired version number and run the build scripts.

Alternatively, you can replace the source files in the src/ffmpeg folder. The build scripts automatically download FFmpeg source code to this folder, but if it already contains source files, they will use the existing files instead.

Both methods will attempt to build FFmpegKit with a different FFmpeg version. Note, however, that if there are incompatibilities between FFmpegKit and the selected FFmpeg version, the build will fail.

[SevenViewSolutions]

This is exactly what I needed, thanks, the issue as you pointed out though is the build fails when I try to using FFmpeg version 6.1 or 7.0 via either changing the version tag in the sources file or by replacing the source ffmpeg directory with my version which is also on 6.1 or 7.0.

Any idea how to get around this? I've tried using the "development" branch but the result is the same.

cp: /Users/macuser/Downloads/ffmpeg/src/ffmpeg/libavutil/x86/emms.h: No such file or directory

TIA!

[tanersener]

Yes, we had some hardcoded paths in ffmpeg.sh file. We fixed them on the development branch. You can copy those lines from there and build ffmpeg.

# MANUALLY ADD REQUIRED HEADERS
mkdir -p "${FFMPEG_LIBRARY_PATH}"/include 1>>"${BASEDIR}"/build.log 2>&1
overwrite_file "${BASEDIR}"/src/ffmpeg/config.h "${FFMPEG_LIBRARY_PATH}"/include/config.h 1>>"${BASEDIR}"/build.log 2>&1
rsync -am --include='*.h' --include='*/' --exclude='*' "${BASEDIR}"/src/ffmpeg/ "${FFMPEG_LIBRARY_PATH}"/include/ 1>>"${BASEDIR}"/build.log 2>&1

However, there is a general issue with the ffmpeg-kit API in versions 6.1 and 7.0. These versions include changes that break the ffmpeg-kit core, which is why we haven't been able to release ffmpeg-kit 6.1 and 7.x. Releasing these versions will require a rewrite of the ffmpeg-kit engine. Therefore, simply fixing those lines will not resolve all the problems."

[PierfrancescoSoffritti]

However, there is a general issue with the ffmpeg-kit API in versions 6.1 and 7.0. These versions include changes that break the ffmpeg-kit core, which is why we haven't been able to release ffmpeg-kit 6.1 and 7.x. Releasing these versions will require a rewrite of the ffmpeg-kit engine. Therefore, simply fixing those lines will not resolve all the problems."

Is this documented somewhere? i'd like to learn more about it.

[tanersener]

Sorry, I didn't quite understand. Which type of document are you asking for?

[PierfrancescoSoffritti]

Does the comment above mean that ffmpeg-kit will not be updated to use ffmpeg 6.1/7.0 because there are breaking changes in the API that require rewriting parts of ffmpeg-kit? If I understood correctly, I was wondering if there is an issue tracking this.

[tanersener]

There are questions about when ffmpeg-kit will support versions 6.1 or 7.x, but they don't mention the challenges we're facing.

Right now, I'm testing different alternatives. Depending on the results, we might have to drop some features, especially support for concurrent sessions. I still need some time to confirm this. The development branch has the latest changes.