Follow-up from "va: Move PROP_RATE_CONTROL to the end of the array"
There are encoder properties that are hardware dependent: if the driver offers them, they are installed in the class. But currently that code is quite fragile: if new properties are added we could fall again in a segmentation fault.
These hardware dependent properties should be handled in helper or in the VA encoders base class.
The following discussion from !6319 (merged) should be addressed:
-
@slomo started a discussion: (+2 comments) This sounds like a footgun that will trigger again in a few months when someone adds new properties. Can this be refactored a bit to avoid this?