-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
"Remove Metadata" only removes video metadata for Rigaya's hardware encoders #330
Comments
For the NVencC (and all rigaya's encoders) it will pass in I just tried it, and seems to clear the Video Language, but doesn't clear container metadata (which is cleared when that option is selected with ffmpeg) Looks like I need to also provide just --metadata clear which I missed. Thanks for pointing it out! |
…a's hardware encoders (thanks to wynterca)
* Adding #109 Support for AVC and HEVC QSV encoding with rigaya's QSVEncC (thanks to msaintauret) * Adding #196 Support for AVC and HEVC Apple Videotoolbox encoder (thanks to Kay Singh) * Adding #323 ignore errors options options for queue (thanks to Don Gafford) * Adding #331 NVEncC API v10 Quality presets: P1 to P7 (thanks to Wontell) * Fixing #321 dhdr10_opt not added for x265 commands (thanks to GizmoDudex) * Fixing #327 FastFlix Duplicates encoding task and encodes same movie to infinity (thanks to Wontell) * Fixing #324 NVEncC wrong Interlace Value set by FastFlix (thanks to Wontell) * Fixing #278 FastFlix occasionally getting stuck on a single video in a queue (thanks to kamild1996) * Fixing #330 "Remove Metadata" only removes video metadata for Rigaya's hardware encoders (thanks to wynterca) * Fixing level was not being passed to hardware encoders
Updated to provide both in https://github.com/cdgriffith/FastFlix/releases/tag/4.9.0, thanks for opening the issue! |
The "Remove Metadata" option doesn't seem to do anything the tool tip says removes titles etc? I am usually encoding with NVencC, maybe that is not supported with that particular encoder?
The text was updated successfully, but these errors were encountered: