On 16.07.2020 04:16, Wang Bin wrote:
What happens if a struct
gets updated, and ffmpeg wants to use the new fields when available,
like happened plenty of times?
Upgrade nvEncodeAPI.h like we've already done. Part of reserved bits will
become a struct member and have a name. These bits will be recognized on
new drivers but ignored on old ones.
So if someone relies on one of the new fields, be it for quality
settings or something, it will then silently be ignored?
This needs some kind of guard for every single field, with an
appropriate error message if a feature newer than what's supported has
been used.
I'm really not sure if this is all worth it. It will massively blow up
the code and make it harder and harder to maintain with every version.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
