On Tue, Sep 30, 2014 at 11:05 PM, Marc-Antoine ARNAUD <[email protected]> wrote: > Hi Vittorio, > > I see the patch "pixdesc: return color properties names" > It's look go me, I just submit it to send something, but I did not think to > use the pixdesc struct. > > Is it also possible to return something more human readable like ITU-R > BT.709 for bt709 ? > You have provide functions to get names, maybe that is can be the > description ?
Umh I am afraid that might be too volatile to let the user access that information. Also the description can be too much or too little depending on the usecase. So while doing another table and another set of api for the description is possible, I believe it's too specific to have in libavutil, and it's really something that fits more in the application level. > The other question to improve the code is to define only one time these > strings between the PixDesc and options into libavutil. > Something like that already exists in libav ? I thought the same but unfortunately strings in options_table need to be compile time constants so we cannot use functions calls unfortunately (nor crossing static table between libs or letting the names be public). Thanks for your comments. Vittorio > Marc-Antoine > _______________________________________________ > libav-devel mailing list > [email protected] > https://lists.libav.org/mailman/listinfo/libav-devel -- Vittorio _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
