On 14/11/13 12:06, Hendrik Leppkes wrote: > Didn't the discussion result in that the people actually using > HWAccels greatly prefer a struct over terrible AVOptions or any other > contrived abomination?
Tell me what's contrived in: - not caring about rendering to a surface You state that you want to have to use that technology by just passing a string with its name and optionally which device to use. ** Nothing changes for your normal avframe usage ** - caring about having the opaque pointers passed to you You state that passing a boolean. You call a single function (always the same) to get the hwaccel-specific context. Then you have your hwaccel specific context and the opaque frame to play with. ** Libavcodec does all for you till the point you want to render ** - feeling obsessive compulsive You setup your hwaccel specific struct and you feed it to libavcodec, then you get back to the point above. > structs are fine. Depends on what you mean with fine. Changing them requires you to provide a custom allocator and you have lots of boilerplate code for nothing. > Also, use an API before you redesign it. :) Maybe I am and thus I'm not so happy to write N times some boring boilerplate since I do not have a just single player to care about ^^; lu _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
