We believe we have identified the issue (I was wrong about it being related to transcoding) and have fixed it in this build. The fix has also been backported to 1.41.3.
We believe we have identified the issue (I was wrong about it being related to transcoding) and have fixed it in this build. The fix has also been backported to 1.41.3.