Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request: Possible to compile a previous version of FFMpeg ? #2759

Open
lhksoft opened this issue Aug 21, 2024 · 4 comments
Open

Request: Possible to compile a previous version of FFMpeg ? #2759

lhksoft opened this issue Aug 21, 2024 · 4 comments

Comments

@lhksoft
Copy link

lhksoft commented Aug 21, 2024

Is it possible to compile a previous version of ffmpeg? As for what I require, it seems it is malfunctioning in current version of ffmpeg (current 7.x). I need to rebuild version 6.01 but don't know what I'm doing wrong, unless it's not possible.
In the file media-autobuild-suite.ini I have set ffmpegPath=/c/ffmpeg601 in that directory I've a local copy of ffmpeg n6.0.1. When the suite is running it fails with the compilation of x264 saying :

┌ x264 git  ........................................... [Recently updated]
Likely error (tail of the failed operation logfile):
CFLAGS: -D_FORTIFY_SOURCE=2 -fstack-protector-strong -mtune=generic -O2 -pipe -D__USE_MINGW_ANSI_STDIO=1 -mthreads
CXXFLAGS: -D_FORTIFY_SOURCE=2 -fstack-protector-strong -mtune=generic -O2 -pipe -D__USE_MINGW_ANSI_STDIO=1
LDFLAGS: -D_FORTIFY_SOURCE=2 -fstack-protector-strong -mtune=generic -O2 -pipe -D__USE_MINGW_ANSI_STDIO=1 -static-libgcc -static-libstdc++
vcs_fetch
++ git rev-parse --git-dir
+ [[ -f .git/shallow ]]
+ unshallow=
+ git fetch --all -Ppft
+ git remote set-head -a origin
error: Cannot determine remote HEAD
git.fetch failed. Check C:/mab/build/ffmpeg601-git/ab-suite.git.fetch.log
This is required for other packages, so this script will exit.
  Creating diagnostics file...

So I gues it's not supported to use a local copy of (a previous version of) ffmpeg, or I'm doing something wrong.

Please some advise.

logs.zip

@L4cache
Copy link
Contributor

L4cache commented Aug 24, 2024

Is your local copy a git folder?

If all you need is using old release tags, then a local copy is not necessary, you can just specify tag name / branch name by appending #<tag name or branch name> to the original ffmpegPath url.
For 6.0.1 it should be https://git.ffmpeg.org/ffmpeg.git#n6.0.1.

@lhksoft
Copy link
Author

lhksoft commented Aug 24, 2024

Is your local copy a git folder?

I tried that, the suite wants to do a git-clone then it doesn't accept a local copy of ffmpeg..

If all you need is using old release tags, then a local copy is not necessary, you can just specify tag name / branch name by appending #<tag name or branch name> to the original ffmpegPath url. For 6.0.1 it should be https://git.ffmpeg.org/ffmpeg.git#n6.0.1.

I tried that too. For the "light-build" used for x264 it uses the previous release I gave (I checked with the file RELEASE in ffmpeg-git folder. But when building actual ffmpeg it ignores my path for previous release and still latest release will be gitted (I checked with RELEASE file, it said 7.0)

As it was kinda urgent I've got a working copy of ffmpeg (previous build, so took release n6.1.2) and I could not compile such via m-ab-s I went to ffmpeg-windows-build-helpers where such is much easier to implement. Cross compiling in linux itself, only it's not so extended as m-ab-s but at least I have my n6.1.2 copy of ffmpeg now.
Now I use 2 versions of ffmpeg, latest build by m-ab-s for all coding, but the previous build for merging multiple ass/ssa files to the matroska file (after it's been coded by the latest build). Seems something got changed in latest built or there's a bug in 7.x - merging multiple subtitles doesn't seem to work anymore in n7.x though it worked in previous builds.

@Jamaika1
Copy link

try this:
https://www.sendspace.com/file/ikiji4

@L4cache
Copy link
Contributor

L4cache commented Sep 1, 2024

Is your local copy a git folder?

I tried that, the suite wants to do a git-clone then it doesn't accept a local copy of ffmpeg..

If all you need is using old release tags, then a local copy is not necessary, you can just specify tag name / branch name by appending #<tag name or branch name> to the original ffmpegPath url. For 6.0.1 it should be https://git.ffmpeg.org/ffmpeg.git#n6.0.1.

I tried that too. For the "light-build" used for x264 it uses the previous release I gave (I checked with the file RELEASE in ffmpeg-git folder. But when building actual ffmpeg it ignores my path for previous release and still latest release will be gitted (I checked with RELEASE file, it said 7.0)

As it was kinda urgent I've got a working copy of ffmpeg (previous build, so took release n6.1.2) and I could not compile such via m-ab-s I went to ffmpeg-windows-build-helpers where such is much easier to implement. Cross compiling in linux itself, only it's not so extended as m-ab-s but at least I have my n6.1.2 copy of ffmpeg now. Now I use 2 versions of ffmpeg, latest build by m-ab-s for all coding, but the previous build for merging multiple ass/ssa files to the matroska file (after it's been coded by the latest build). Seems something got changed in latest built or there's a bug in 7.x - merging multiple subtitles doesn't seem to work anymore in n7.x though it worked in previous builds.

I have had no problem building old ffmpeg release tags, that must be a bug I assume. Maybe you can try disable the "light-build" in x264 (I think it's the ffms input support).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants