Quoting Diederick C. Niehorster (2021-06-05 16:51:32) > On Sat, Jun 5, 2021 at 4:36 PM Anton Khirnov <an...@khirnov.net> wrote: > > Sorry to rain on your parade, but I don't think we should go ahead with > > this before deciding what is to be done with libavdevice. The last > > discussion about it died without being resolved, but the issues are > > still present. > > I understand. I realize I'm new here: Is there a timeline for such a > discussion and could the discussion benefit from a real usage example > such as this patch series? I guess a big change in libavdevice should > at least offer the functionality the current implementation offers (or > theoretically offers :p). I really like the current design where an > avdevice can just be used through the avformat interface. Add > avdevice_register_all(); and Bob's your uncle!
There is no timeline, it depends on someone sitting down and doing the work. The options proposed so far were 1) merging libavdevice into libavformat 2) making libavdevice into an independent library with an independent API 3) moving libavdevice functionality into ffmpeg.c I volunteered to do 1), but was stopped by some issues and Mark volunteering to do 2). But Mark did not progress far on that apparently, so now we are stuck. Maybe we should do a technical committee vote on it. -- Anton Khirnov _______________________________________________ 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".
