-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
[FEATURE REQUEST] Zoning Support #84
Comments
Shouldn't |
How do you do it, is it hassle-free with av1an? I don't see command line support for zoning in av1an, i.e. different vmaf targets or crf/qp settings for specified time or frame ranges. I guess the segment settings av1 itsself generate could be modified, I didn' try that yet. If it's not in av1an already, cli zoning support would certainly be a more natural feature there than in the encoder itsself. |
sorry for the strange formatting, the most I can do from phone is copy-pasting from my script
example inside the zoning file:
u can even use different av1 encoders (but iirc in the last versions it needed some fixes to not crash); any setting in the zone file will only override the same general setting; av1an can also only create a file containing all the scenes with vmaf target was not working last time I checked but it's not worth it anyway; also av1an is the only way to use 100% of your cpu and make eventual correct speed tests |
Thanks a lot for the insights and the link, I didn't know that script yet :-)
On this, I have to comment that bare SVT-AV1 saturates my 6-core Zen4 just fine, and av1an just adds uneccessary hassle and overhead - plus my system has too limited memory for further parallel encoding. For me, the reason to use av1 is the segment vmaf target (which does work for me), but I only use this on very select encodes because of the significant overhead. Edit: I now see svt-av1_keyframes.py made for same reason "I made this because standalone SVT-AV1 would run faster than chunked SVT-AV1 in Av1an on my 4-core system" : https://github.com/trixoniisama/scripts |
Sometimes during encoding, certain scenes require a higher bitrate or different parameters to meet encoding needs. Similar to how x264 and x265 support the parameter (--zones). Can AV1 support this feature natively instead of requiring users to manually cut the video segments for separate processing, encoding them individually, and then merging them back together? I believe this feature would be very useful. I hope everyone will consider and support it.
The text was updated successfully, but these errors were encountered: