Skip to content
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

Closed
Joet73 opened this issue Mar 13, 2023 · 3 comments
Closed

qsvenc with y4m input file #442

Joet73 opened this issue Mar 13, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@Joet73
Copy link

Joet73 commented Mar 13, 2023

Describe the bug

  1. Encoder error with colorrange and chromaloc parameters automatically setup to auto. As per the QSVenc documentation says only avsw and avhw readers are able to use auto.
  2. When I manually set colorrange to limited & chromaloc to anything but auto (tried from 0 to 5), encoding works but color is shifted.

To Reproduce
Steps to reproduce the behavior:

  1. Input .y4m file downloaded here
  2. Choose qsvenc HEVC encoder option (Using V7.34 for the test)
  3. Use icq mode. I haven't tried other mode but error should be the same.
  4. Start encoding.
  5. Using a the below command line no error but the chroma is shifted as well.
    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.
@Joet73 Joet73 added the bug Something isn't working label Mar 13, 2023
@cdgriffith
Copy link
Owner

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)

@Joet73
Copy link
Author

Joet73 commented Mar 13, 2023

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.

cdgriffith added a commit that referenced this issue Apr 20, 2023
…ks 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)
cdgriffith added a commit that referenced this issue Apr 20, 2023
* 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
@cdgriffith
Copy link
Owner

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants