Zeranoe closing down

[Sharc]

https://ffmpeg.zeranoe.com/builds/

ffmpeg.zeranoe.com will close on Sep 18, 2020, and all builds will be removed. If you're using Zeranoe FFmpeg Builds in your product, please ensure that you have a hosting strategy in place by the 18th. Thank you to everyone who supported the project along the way!

[SeeMoreDigital]

hydra3333 posted back in May (in the news section) that the zeranoe forums have closed. And now it's the development too.

Always sad when a development project comes to an end...

[FranceBB]

Time to compile ffmpeg ourselves from the source, then, I guess...

[qyot27]

Originally Posted by FranceBB

Time to compile ffmpeg ourselves from the source, then, I guess...

<shameless>Well, there is a guide for that.</shameless>

It usually gets updated every six months or so, after every new Ubuntu release (sometimes with a delay if a new release of GCC is imminent).

[FranceBB]

Originally Posted by qyot27

<shameless>Well, there is a guide for that.</shameless>

It usually gets updated every six months or so, after every new Ubuntu release (sometimes with a delay if a new release of GCC is imminent).

Actually, the last time I compiled ffmpeg (years ago) I did it for windows only from Windows following the official guide and it worked like a charm. It was pretty straightforward. Next week I'll try to compile them again.

[foxyshadis]

Originally Posted by FranceBB

Actually, the last time I compiled ffmpeg (years ago) I did it for windows only from Windows following the official guide and it worked like a charm. It was pretty straightforward. Next week I'll try to compile them again.

ffmpeg compiles great on VS these days, vs back when VS couldn't even do C99... the problem is more if you want all those third-party libraries built in. Some are nice, some are painful, it's all painful to get included into the final binary.

[Selur]

Sad to see Zeranoe stopping to build FFmpeg even when started using m-ab-s to compile FFmpeg for Windows and download ffmpeg Mac OS builds from https://evermeet.cx/ffmpeg/.

[Sharc]

Originally Posted by Selur

Sad to see Zeranoe stopping to build FFmpeg even when started using m-ab-s to compile FFmpeg for Windows and download ffmpeg Mac OS builds from https://evermeet.cx/ffmpeg/.

So you will continue to provide your own compilation of ffmpeg in future Hybrid releases, based on m-ab-s for Windows?

[tormento]

I use FFmpeg almost for audio encoding only, as it's the only reliable free software up to date.

I fear I will have to compile on my own. Perhaps would be useful to open a thread with voluntary builds?

Using Linux builds with WSL might be one option.

[Sharc]

m-ab-s seems to work pretty well for Windows here. No major problems found so far ....

[GOZARCK]

Originally Posted by Sharc

m-ab-s seems to work pretty well for Windows here. No major problems found so far ....

Can you share your "media-autobuild_suite.ini", because I don't know which options to choose and which ones not. I would like my x64 build to be the most similar to the version of Zeranoe. Thanks

[Sharc]

Originally Posted by GOZARCK

Can you share your "media-autobuild_suite.ini", because I don't know which options to choose and which ones not. I would like my x64 build to be the most similar to the version of Zeranoe. Thanks

My current "media-autobuild_suite.ini":

[compiler list] 
arch=3
license2=2
standalone=2
vpx2=2
aom=2
rav1e=2
dav1d=2
libavif=2
x2643=1
x2652=1
other265=2
svthevc=2
xvc=2
vvc=2
svtav1=2
svtvp9=2
flac=2
fdkaac=2
faac=2
exhale=2
mediainfo=2
soxB=2
ffmpegB2=1
ffmpegUpdate=2
ffmpegChoice=1
mp4box=2
rtmpdump=2
mplayer2=2
mpv=2
vlc=2
bmx=2
curl=2
ffmbc=2
cyanrip2=2
redshift=2
ripgrep=2
jq=2
jo=2
dssim=2
avs2=2
CC=2
cores=3
deleteSource=1
strip=1
pack=2
logging=1
updateSuite=1
timeStamp=2
ccache=2
noMintty=2

and my "ffmpeg_options.txt" (a subset of zeranoe's):

# Lines starting with this character are ignored
# To override some options specifically for the shared build, create a ffmpeg_options_shared.txt file.

# Basic built-in options, can be removed if you delete "--disable-autodetect"
--disable-autodetect
--enable-amf
--enable-bzlib
--enable-cuda
--enable-cuvid
--enable-d3d11va
--enable-dxva2
--enable-iconv
--enable-lzma
--enable-nvenc
--enable-schannel
--enable-zlib
--enable-sdl2
--enable-ffnvcodec
--enable-nvdec
--enable-cuda-llvm

# Common options
--enable-gmp
--enable-libmp3lame
--enable-libopus
--enable-libvorbis
--enable-libvpx
--enable-libx264
--enable-libx265
--enable-libdav1d
--enable-libaom
--disable-debug

# Zeranoe
--enable-fontconfig
#--enable-gnutls
#--enable-libass
--enable-libbluray
#--enable-libfreetype
#--enable-libmfx
#--enable-libmysofa
#--enable-libopencore-amrnb
#--enable-libopencore-amrwb
#--enable-libopenjpeg
#--enable-libsnappy
#--enable-libsoxr
#--enable-libspeex
#--enable-libtheora
#--enable-libtwolame
#--enable-libvidstab
#--enable-libvo-amrwbenc
#--enable-libwavpack
#--enable-libwebp
#--enable-libxml2
#--enable-libzimg
#--enable-libshine
#--enable-gpl
#--enable-openssl
#--enable-libtls
--enable-avisynth
#--enable-mbedtls
--enable-libxvid
#--enable-libopenmpt
#--enable-version3
#--enable-librav1e
#--enable-libsrt
#--enable-libgsm
--enable-libvmaf

# Full
#--enable-chromaprint
#--enable-decklink
#--enable-frei0r
#--enable-libbs2b
#--enable-libcaca
#--enable-libcdio
#--enable-libfdk-aac
#--enable-libflite
#--enable-libfribidi
#--enable-libgme
#--enable-libilbc
#--enable-libsvthevc
#--enable-libsvtav1
#--enable-libsvtvp9
#--enable-libkvazaar
#--enable-libmodplug
#--enable-librtmp
#--enable-librubberband
#--enable-libssh
#--enable-libtesseract
--enable-libxavs
#--enable-libzmq
#--enable-libzvbi
#--enable-openal
#--enable-libcodec2
#--enable-ladspa
#--enable-vapoursynth
#--enable-liblensfun
#--enable-libglslang
#--enable-vulkan

# Full plus options that add shared dependencies
#--enable-opencl
#--enable-opengl
#--enable-cuda-nvcc
#--enable-libnpp
#--enable-libopenh264

[tormento]

Tried to compile with MAB for both x86 & x64 and I get following error:

MinGW32 GCC compiler isn't installed; maybe the download didn't work
Do you want to try it again?

If I try to compile x64 only:

MinGW64 GCC compiler isn't installed; maybe the download didn't work
Do you want to try it again?

Ideas?

Windows 10 x64 here.

[Sharc]

Close it and restart the .bat

[tormento]

Originally Posted by Sharc

Close it and restart the .bat

Strange enough, if I launch from PowerShell or CMD, it gives error.

If I launch from Explorer, double clicking, compilation starts.

[jlw_4049]

Man, I have used Zeranoe builds for as long as I have been using FFMPEG.

[FranceBB]

The last time I compiled FFMpeg was in 2018.
Back then, everything was working fine.
I even wrote a guide with screenshots about it.
I tried to compile the very latest version of FFMpeg in the very same way I used to compile it in 2018 but it failed.
The guide I wrote at the time was:


Download MSYS2: https://www.msys2.org/
Download and run the installer - "x86_64".
Enter Installation Folder "C:\msys64".




Tick Run MSYS2 now



Update the package database and core system packages by typing the following command the MSYS2 console:

pacman -Syu

Update the make package:

pacman -S make

Install GCC:

pacman -S gcc

Remove link.exe in the MSYS2 usr bin folder (C:\msys64\usr\bin\link.exe)

Install perl:

pacman -S perl

Install diffutils:

pacman -S diffutils

Download YASM: http://www.tortall.net/projects/yasm....3.0-win64.exe

Rename the downloaded executable to yasm.exe and place it in your MSYS2 path: "C:\msys64\usr\bin\yasm.exe".

Download gas-preprocessor: https://github.com/FFmpeg/gas-prepro...reprocessor.pl

Place the downloaded Perl script in your MSYS2 path: "C:\msys64\usr\bin\gas-preprocessor.pl".

Launch VS2015 x86 x64 Cross Tools Command Prompt:

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Visual Studio 2015\Visual Studio Tools\Windows Desktop Command Prompts\VS2015 x86 x64 Cross Tools Command Prompt

Set the following environment variables in the launched command prompt above:

SET LIB=%VSINSTALLDIR%VC\lib\store\amd64;%VSINSTALLDIR%VC\atlmfc\lib\amd64;%UniversalCRTSdkDir%lib\RTVersion%\ucrt\x64;;%UniversalCRTSdkDir%lib\RTVersion%\um\x64;C:\Program Files (x86)\Windows Kits\NETFXSDK\4.6\lib\um\x64;;C:\Program Files (x86)\Windows Kits\NETFXSDK\4.6\Lib\um\x64

SET LIBPATH=%VSINSTALLDIR%VC\atlmfc\lib\amd64;%VSINSTALLDIR%VC\lib\amd64;

SET INCLUDE=%VSINSTALLDIR%VC\include;%VSINSTALLDIR%VC\atlmfc\include;%UniversalCRTSdkDir%Include\RTVersion%\ucrt;%UniversalCRTSdkDir%Include\RTVersion%\um;%UniversalCRTSdkDir%Include\RTVersion%\shared;%UniversalCRTSdkDir%Include\RTVersion%\winrt;C:\Program Files (x86)\Windows Kits\NETFXSDK\4.6\Include\um;

Open MSYS2 Shell from the command prompt above:

C:\msys64\msys2_shell.cmd

Download FFmpeg from GitHub (click "Clone/Download"): https://github.com/FFmpeg/FFmpeg

Place the folder in C and rename it "ffmpeg".



In your MSYS2 shell navigate to your cloned FFmpeg folder:



Invoke the following make commands:

mkdir -p Output/Windows/x64

Then navigate to the newly created folder:

cd Output/Windows/x64

Type the following commands:

../../../configure \
--toolchain=msvc \
--disable-programs \
--disable-d3d11va \
--disable-dxva2 \
--arch=x86_64 \
--enable-shared \
--enable-cross-compile \
--target-os=win32 \
--extra-cflags="-MD -DWINAPI_FAMILY=WINAPI_FAMILY_APP -D_WIN32_WINNT=0x0A00" \
--extra-ldflags="-APPCONTAINER WindowsApp.lib" \
--prefix=../../../Build/Windows/x64

make

make install

It will take quite some time to compile.



Once everything is done, you'll find the binaries in "Build/Windows/x64".






All this was good in 2018.
Right now, I've done exactly the same, but I've used:

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Visual Studio 2019\Visual Studio Tools\VC

'cause I have Visual Studio 2019 instead of 2015 and:

SET LIB=%VSINSTALLDIR%VC\lib\store\amd64;%VSINSTALLDIR%VC\atlmfc\lib\amd64;%UniversalCRTSdkDir%lib\RTVersion%\ucrt\x64;;%UniversalCRTSdkDir%lib\RTVersion%\um\x64;C:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\lib\um\x64;;C:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\Lib\um\x64

SET LIBPATH=%VSINSTALLDIR%VC\atlmfc\lib\amd64;%VSINSTALLDIR%VC\lib\amd64;

SET INCLUDE=%VSINSTALLDIR%VC\include;%VSINSTALLDIR%VC\atlmfc\include;%UniversalCRTSdkDir%Include\RTVersion%\ucrt;%UniversalCRTSdkDir%Include\RTVersion%\um;%UniversalCRTSdkDir%Include\RTVersion%\shared;%UniversalCRTSdkDir%Include\RTVersion%\winrt;C:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\Include\um;

'cause I have NTFXSDK 4.8 instead of 4.6.

then I've done the very same things, but it says:
"cl is unable to create an executable file.
C compiler test failed."
Why? Did something change? Is it me who messed up with directories? Am I missing something? What am I doing wrong in 2020 that I was doing right in 2018?

[jlw_4049]

I have recently had success running this to compile it the way I wanted.

https://github.com/m-ab-s/media-autobuild_suite

[tormento]

Did you guys install NVIDIA CUDA SDK to have proper compile?

I did as it was complaining about ENV variable not found and I had a doubt about SDK being necessary.