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

Commit 2af4fbc9 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... 

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

Change-Id: Ie2920cafc7213528a8acb878c638550a056d3607
parents 7735c641 83cfaf6d

media/java/android/media/MediaCodec.java

+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>