[FFmpeg-trac] #9059(ffmpeg:new): (avisynth/vapoursynth) No progress, no encoding (in some cases) when ffmpeg shared is used (Linux)
FFmpeg
trac at avcodec.org
Wed Jan 6 20:26:43 EET 2021
#9059: (avisynth/vapoursynth) No progress, no encoding (in some cases) when ffmpeg
shared is used (Linux)
-------------------------------------+-------------------------------------
Reporter: artenaki | Type: defect
Status: new | Priority: normal
Component: ffmpeg | Version:
Keywords: avisynth, | unspecified
vapoursynth | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
It's about Linux. ffmpeg shared 4.3.1 is compiled with {{{--enable-
avisynth --enable-vapoursynth --enable-shared --disable-static options}}}.
For avisynth and vapoursynth ffms2 and l-smash import plugins are also
compiled, they are linked with ffmpeg shared libs. I am creating avs
script like:
{{{
ffms2("input.mkv")
#LWLibavVideoSource("input.mkv")
}}}
Example for vapoursynth:
{{{
import vapoursynth as vs
core = vs.get_core()
video = core.ffms2.Source("input.mkv")
#video = core.lsmas.LWLibavSource("input.mkv")
video.set_output()
}}}
and open them in ffmpeg (shared) for encoding:
{{{
ffmpeg -i input.avs output.mkv
ffmpeg -f vapoursynth -i input.vpy output.mkv
}}}
In this case, either nothing happens (white terminal screen), or the
encoding is performed, but no information is displayed on the terminal. I
think this is because of the recursion. In ffmpeg-static everything works
fine and information is displayed. ffmpeg static is compiled with
{{{--enable-static --disable-shared}}} options. But ffmpeg-shared normally
opens internal scripts like {{{ColorBars ()}}}.
At the moment, the situation is as follows:
'''vapoursynth:''' ffms2 and l-smash - white screen but encoding is
performed
'''avisynth+:''' ffms2 - white screen, nothing happens
'''avisynth+:''' l-smash - white screen but encoding is performed
You can find out more in these bug reports
https://github.com/AviSynth/AviSynthPlus/issues/194
https://github.com/vapoursynth/vapoursynth/issues/653
And if necessary, talk to the developers of avisynth+ and vapoursynth.
The problem has been confirmed by other people.
Since the problem is observed in different programs: avisynth/vapoursynth
and ffms2/lsmash, I suspect that the reason is ffmpeg (shared libs).
--
Ticket URL: <https://trac.ffmpeg.org/ticket/9059>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list