3 ms·
> But FFmpeg does not have the resources to fix these at the speed Google is finding them. Google submitting a patch does not address this issue. The main work
by walletdrainer 11mo ago
> But FFmpeg does not have the resources to fix these at the speed Google is finding them.
Google submitting a patch does not address this issue. The main work for maintainers here is making the decision whether or not they want to disable this codec, whether or not Google submits a patch to do that is completely immaterial.