On Thu, 2020-09-03 at 01:02 +0000, Rogozhkin, Dmitry V wrote: > > > > (If you do implement it then you can delete all of the ad-hoc > > treatment in ffmpeg, like has been done for the other hardware > > codecs.) > > I like deleting code:). Ok, this sounds good. Let's try to understand > what might be missing in the current implementation since I honestly > don't see any gaps - it just works.
@Mark. We did internal review and believe that DEVICE_CTX path is actually ready to be used and just needs to be activated. Can you, please, let me know how you would like to proceed: 1. We can either consider review and apply the fix first (this patch) then deal with ad_hoc in non-related patch series 2. Or we can go with the bigger patch series right away and address both device_ctx + ad_hoc 2nd variant might require longer time to verify and review which would hold the fix. What are your thoughts? _______________________________________________ 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".
