> You (or anyone) are welcome to contribute to the SVT-AV1 project, and
> submit the FFmpeg plugin changes you'd like to make here:
> https://github.com/OpenVisualCloud/SVT-AV1/tree/master/ffmpeg_plugin,
> and we will take your commits seriously. But I have not got any code
> changes made by you in our project GitHub and it seems you haven't made
> any contribution to the project yet.

I prefer to contribute on FFmpeg mainline instead of a forked branch. However, 
once get aligned in the community, of course I can contribute to the branch as 
well.
(Many SVT core library and API patches hold on my hand will also be sent out 
after my leave of next 2~3 weeks)

And let me provide more detail about the purposes:
1. SVT encoders (01.org/svt ) show very impressive performance benefit and get 
much attention . 
  Let's collect some feedback as early as possible, this patch is not call for 
merge bug call for feedback, comments. Not only collect feedback of SVT FFmpeg 
wrapper, but also feedback of SVT core libraries and APIs.

  e.g : SVT-AV1 reused libaom. If you enable both libsvt-av1 and libaom as 
static link, then will have name conflict. 
  Such issue is not easily found if you keep wrapper patch on 
https://github.com/OpenVisualCloud/SVT-AV1/tree/master/ffmpeg_plugin ,
  But will easily found if works on FFmpeg mainline. 

2. Many review comments from community (including mine) haven't been well 
addressed in SVT-HEVC wrapper patch. 
  This patch is just to address them, probably it can be a reference of 
SVT-HEVC wrapper too. 

3. As mentioned in the patch annotation, this wrapper patch is a response of 
ticket #7914, though it is not quite mature.
_______________________________________________
ffmpeg-devel mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".

Reply via email to