Closed Joet73 closed 1 year ago
Hi @Joet73 thanks for the detailed write up! As you have already stripped it down to a base command and looks to be a possible issue with QSVEnc directly, I would copy and paste your findings onto their issues page https://github.com/rigaya/QSVEnc/issues
If FastFlix is making it worse in some way please let me know! (for example I set everything to auto in most cases, if there is something wrong there or needs to be unset entirely, FastFlix might need to be updated)
Hi Issue reported here But i still believe that there is an issue with fastflix automatically setting chromaloc and colorrange to auto which throw an error with y4m input file. BTW, just tested eith avi file, same error.
Thanks for the extra details about it trying to add stuff it can't to avi / y4m. Right now have a quick fix for qsv / nvenc that will always specify the avsw reader that should fix it, but going to be adding option to allow it to use the default y4m reader as well https://github.com/cdgriffith/FastFlix/releases/tag/5.4.1
Describe the bug
To Reproduce Steps to reproduce the behavior:
QSVEncC64.exe --y4m -i input.y4m --icq 18 -c hevc -u best -o output.mp4
Using this ffmpeg piping no chroma shiftffmpeg.exe -y -i input.y4m -an -f yuv4mpegpipe - | QSVEncC64.exe --y4m -i - --icq 18 -c hevc -u best -o output.mp4
It might be a bug with Rigaya's y4m reader.