New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
qsvenc with y4m input file #442
Comments
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 |
* Fixing #460 QSVEncC not listed as encoder with FastFlix 5.4.0 (thanks to zedfreak) * Fixing #451 x265 presets and tunes not being applied properly (thanks to HannesJo0139) * Fixing #442 improper options passed to rigaya's encoders for non libavformat readers (thanks to Joet73) * Fixing poetry issues by using setuptools instead
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 shift
ffmpeg.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.
The text was updated successfully, but these errors were encountered: