I did just test this one, and it does allow the probe info to appear again. Some distros may be more kind about this one, since the libs are shared now, but will probably object to having to use RPATH (Debian would, for sure as I'm testing on Ubuntu, that may be why using LD_LIBRARY_PATH was necessary other distros may be okay with it with just RPATH set). Link FFMS2 against it using LDFLAGS="-Wl,-rpath-link=/path/to/alternate/ffmpeg" (only so ffmsindex will actually link and the compilation process finishes) and pass LD_LIBRARY_PATH=/path/to/alternate/ffmpeg to the client (FFmpeg) when you open an FFMS2-using script.
#Avisynth ffmpeg install install
Solution 2: Build a minimal FFmpeg (like in 1.1) as shared, and install it to somewhere else on the system. Because the FFmpeg libraries are static, FFMS2 itself is fine with it, and it never touches the system libraries the CLI uses, so the conflict never appears.
#Avisynth ffmpeg install windows
FFMS2 doesn't use things like the muxers and encoders anyway, so this option is more tailor-made for what FFMS2 actually requires to function (it's also basically what Windows builds have always done). Less overtly objectionable, but puts the onus on the user to keep that minimal copy somewhere. Solution 1.1: Build a minimal version of FFmpeg as static, install it somewhere else on the system (like /opt or somewhere in $HOME), and link FFMS2 against that one using PKG_CONFIG_PATH. If the distro provides both static and shared versions of the libraries (meaning they don't explicitly pass -disable-static), link FFMS2 against the static ones. Most distros don't like this idea (read: hate, detest, etc., will flatly refuse to do it), but it works exactly as you would expect it to work. Solution 1: Build the system FFmpeg as static, link FFMS2 to it as usual. Regardless, I have not experienced it actually hanging, only that the probe info and progress are not pushed to stdout and displayed in the Terminal session (the probe info still appears in the output of ffmpeg -report, the output file is still created, FFplay and mpv still play the script back normally). The problem is the circular dependency between FFMS2 and FFmpeg CLI both depending on the same set of shared libraries when FFmpeg has been built shared and FFMS2 was linked to that shared FFmpeg.
#Avisynth ffmpeg install update
Revert "doc/general: update avisynth docs with a way to install just the headers using CMake" Revert "avformat/avisynth: fix deprecation warning" Revert "doc/general: AviSynth+ works on Linux now, AvxSynth is gone."
Revert "avformat/avisynth: switch to AviSynth+ on Linux"
Revert "compat/avisynth: remove avisynth headers" I have no idea which changes you're referring to.