[x265] Bug: Since x265 v3.6+56, piped input encodes eternally

Mario *LigH* Rohkrämer contact at ligh.de
Mon Aug 26 17:11:17 UTC 2024


There was a complaint in the doom9 video forum that piped input does not 
stop encoding when the pipe closes.

I just compared my little archive of x265 builds, specifically x265 
versions 3.6+[13|35|46|56|65]; and [56|65] don't stop encoding.

I used a small AviSynth script *FrameCountTest.avs* like this:

+----
ColorBarsHD()
Info()
Trim(0,99)
+----

uses https://github.com/DJATOM/avs2yuv/releases/tag/0.30 but could as 
well use ffmpeg for frameserving

avs2yuv FrameCountTest.avs -nstdr -o - | x265_3.6+13_Win64.exe -o 
FrameCountTest13.264 --input - --y4m {stops after 100 frames}
avs2yuv FrameCountTest.avs -nstdr -o - | x265_3.6+35_Win64.exe -o 
FrameCountTest35.264 --input - --y4m {stops after 100 frames}
avs2yuv FrameCountTest.avs -nstdr -o - | x265_3.6+46_Win64.exe -o 
FrameCountTest46.264 --input - --y4m {stops after 100 frames}
avs2yuv FrameCountTest.avs -nstdr -o - | x265_3.6+56_Win64.exe -o 
FrameCountTest56.264 --input - --y4m {does not stop}
avs2yuv FrameCountTest.avs -nstdr -o - | x265_3.6+65_Win64.exe -o 
FrameCountTest65.264 --input - --y4m {does not stop}


-- 

Fun and success!

Mario *LigH* Rohkrämer
maito:contact at ligh.de


More information about the x265-devel mailing list