YUV piping doesn't work about vvenc HOT 4 CLOSED

I'm getting the same issue here.

ffmpeg -hide_banner -i test.mkv -c:v rawvideo -pix_fmt yuv420p10le - | vvencapp -p 1 --preset medium -o try.h266 --format yuv420_10 --size 1920x1080 --framerate 60 --qp 30 --qpa 0 --input "" -f 60

started @ Thusday Apr 8 13:47:49 2021 vvencapp [error]: failed to open input file

from vvenc.

What do you think is the issue here? FFmpeg takes too long to produce input - it would be available only after the check on the vvenc side? In this case we do should add some explicit signaling of stdin-input ( -i - or -i stdin)

from vvenc.

Using - to denote stdin (or stdout, depending on context) would certainly be an improvement over the null string, as it's commonly used elsewhere (while null strings are not).

from vvenc.

On linux, as stated above, vvenc fails to find the YUV input via stdin. However, using the same command within Windows, vvenc will read the first frame or two then stops with FFMPEG broken pipe error.

from vvenc.