On 3/19/18, wm4 <nfx...@googlemail.com> wrote: > On Mon, 19 Mar 2018 02:59:54 +0000 > Josh de Kock <j...@itanimul.li> wrote: > >> Hi, >> >> The new iteration API to replace the old _next() is nearing the end of >> it's completion with the lavfi patch on the mailing list and only one >> outstanding issue: >> >> AVOptions would not be found for devices as there is no AVClass for >> lavd. At the moment it would work if you were to still call >> avdevice_register_all() because then devices get registered as formats >> in the old API (which the child_class_next function still uses). When >> the format_child_class_next() function switches to the iterate() API >> it would no longer have access to devices and thus there would be no way >> for av_opt_find() to find an option for devices. The fix for this is >> simple, add an AVClass for lavd--fairly clean and unobjectionable. > > I really don't understand the problem, or why this AVClass crap is > needed. It sounds absurd.
Yes, avdevice (non)API is absurd. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
