Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 5fef5a91 authored by Lajos Molnar's avatar Lajos Molnar Committed by android-build-merger
Browse files

Merge "media: clarify frame dropping behavior for decoder output" into qt-dev am: cfb6f934

am: 46cb9bed

Change-Id: I546b2851e7d7064beeb7e1bccf6d1615a88ef9f6
parents b6cca296 46cb9bed
Loading
Loading
Loading
Loading
+10 −0
Original line number Diff line number Diff line
@@ -644,6 +644,16 @@ import java.util.concurrent.locks.ReentrantLock;
 <p>
 Also since {@link android.os.Build.VERSION_CODES#M}, you can change the output Surface
 dynamically using {@link #setOutputSurface setOutputSurface}.
 <p>
 When rendering output to a Surface, the Surface may be configured to drop excessive frames (that
 are not consumed by the Surface in a timely manner). Or it may be configured to not drop excessive
 frames. In the latter mode if the Surface is not consuming output frames fast enough, it will
 eventually block the decoder. Prior to {@link android.os.Build.VERSION_CODES#Q} the exact behavior
 was undefined, with the exception that View surfaces (SuerfaceView or TextureView) always dropped
 excessive frames. Since {@link android.os.Build.VERSION_CODES#Q} the default behavior is to drop
 excessive frames. Applications can opt out of this behavior for non-View surfaces (such as
 ImageReader or SurfaceTexture) by targeting SDK {@link android.os.Build.VERSION_CODES#Q} and
 setting the key {@code "allow-frame-drop"} to {@code 0} in their configure format.

 <h4>Transformations When Rendering onto Surface</h4>