Framepacing issue for 900p 120fps stream

[Dum4G]

Version

Media3 1.9.1, also 1.8.0

More version details

No response

Devices that reproduce the issue

TCL 50V6B (bugreport-G07_4K_GB_NF-RP1A.200622.001-2026-02-06-21-14-08.zip, bugreport-G07_4K_GB_NF-RP1A.200622.001-2026-02-07-18-09-05.txt)
Android 11 (2024-12-05)
SOC rtd2851a

xiaomi mibox4 (bugreport-oneday-PI-2026-01-31-17-02-33.zip, bugreport-oneday-PI-2026-02-04-22-26-32.zip)
Android 9 (PI.3933 release-keys)
SOC Amlogic S905L

Devices that do not reproduce the issue

Same TV using MX Player (allows to watch the VOD at 30fps or so it seems)

Vivo X100 Pro
Android 15
SOC Dimensity 9400

nothing phone 1
Android 15
SOC Snapdragon 778G+ 5G

Reproducible in the demo app?

Yes

Reproduction steps

1. Play the attached media in the demo app or any other app that uses ExoPlayer (like SmartTwitchTV or ViMu player)

Expected result

The media will play at the best framerate that is allowed by hardware. Or at least the framerate will be limited to screen refresh rate (that is 60 fps for this device)

Actual result

Drammatic framedrops, very low fps

From TCL 50V6B during SmartTwitchTV (Exoplayer 1.8.0) playback
2026-1-29___4-47_20.txt
2026-1-29___5-6_6.txt

Media

https://d3fi1amfgojobc.cloudfront.net/c1f3508efbaaf62d1a12_kisimov_316115642981_1769641008/chunked/index-muted-VP408PBB3V.m3u8

Bug Report

• You will email the zip file produced by adb bugreport to android-media-github@google.com after filing this issue.

[microkatz]

@Dum4G

Thank you for reporting your issue. I checked out all the log files and traces you sent but there does not appear to be any ExoPlayer-related logs. In the bugreport you emailed, the logcat is completely empty. Are you sure that you collected a trace after reproducing the issue using the Demo Application?

[Dum4G]

Another trace has been sent. Captured during playback by my collegue

[microkatz]

@Dum4G

I checked the file your colleague sent. That file did not contain any ExoPlayer logs. Please review https://developer.android.com/media/media3/exoplayer/debug-logging. The ExoPlayer Demo application does add the mentioned EventLogger(). All you should have to do is create a bugreport using adb. See additional details on how to create a bug report here.

It would be great to see logcat traces from androidx.media3.demo.main containing messages about dropping frames etc. If you can make sure the relevant logs described in https://developer.android.com/media/media3/exoplayer/debug-logging in your trace before sending it to us then that would be great!

[Dum4G]

I checked the file your colleague sent. That file did not contain any ExoPlayer logs. Please review https://developer.android.com/media/media3/exoplayer/debug-logging.

Some logs can be found by searching I edia3.demo.mai: for whatever reason

The ExoPlayer Demo application does add the mentioned EventLogger()

There a 1290 matches for event logger and many of them do mention dropped frames in bugreport-oneday-PI-2026-02-04-22-26-32 file. Is there something particular that we're missing?

All you should have to do is create a bugreport using adb

This is exactly what has been done. We didn't fake zip structure to mimic typical bugreport collected by dumpstate

[Dum4G]

UPD: sent a zip from TCL, thanks for the guidance. It's not as informative as mibox4 tho
UPD2: bugreport-G07_4K_GB_NF-RP1A.200622.001-2026-02-07-18-09-05.txt has been sent with increased log buffer size and a few setprops in attempt to collect more debug info. Please note that I'm using a user build firmware that may have restrictions to logd. Any suggestions are welcome as current documentation assumes logd is unrestricted out of the box as if it were user-debug builds.

[microkatz]

@Dum4G

Ah. I think the issue was that I wasn't able to get the file. All I see in my inbox is an orignal email from you with a file called "bugreport.txt". I didn't see any other messages or responses in addition to the first with a file called "bugreport-oneday-PI-2026-02-04-22-26-32". I think there was some issue with the "reply all" that did not forward the messages. I was able to check the actual group and I now see the files. I'll take a look.

[microkatz]

@Dum4G

Thank you for responding and pointing me towards the oddity that you had indeed sent the traces! I just wasn't originally able to see them.

Yes, I do see all the trace messages reporting frame drops:

01-31 16:57:29.917 10052  6547  6547 D EventLogger: droppedFrames [eventTime=13.37, mediaPos=2.14, window=0, period=0, 50]
01-31 16:57:30.553 10052  6547  6547 D EventLogger: droppedFrames [eventTime=14.05, mediaPos=2.82, window=0, period=0, 50]
01-31 16:57:31.127 10052  6547  6547 D EventLogger: droppedFrames [eventTime=14.62, mediaPos=3.40, window=0, period=0, 50]
01-31 16:57:31.667 10052  6547  6547 D EventLogger: droppedFrames [eventTime=15.16, mediaPos=3.93, window=0, period=0, 50]
01-31 16:57:31.780 10052  6547  6547 D EventLogger: metadata [eventTime=15.28, mediaPos=4.04, window=0, period=0
01-31 16:57:31.781 10052  6547  6547 D EventLogger:   TRCK: description=null: values=[2]
01-31 16:57:31.781 10052  6547  6547 D EventLogger:   TDEN: description=null: values=[2026-01-28T22:56:54]
01-31 16:57:31.781 10052  6547  6547 D EventLogger:   TDTG: description=null: values=[2026-01-28T22:56:54]
01-31 16:57:31.781 10052  6547  6547 D EventLogger:   TOFN: description=null: values=[index-0000000002.ts]
01-31 16:57:31.782 10052  6547  6547 D EventLogger:   TSSE: description=null: values=[0576bf0e6e08f90f76d0d1094f1448769bdf2e0e-1.0.1230.0]
01-31 16:57:31.782 10052  6547  6547 D EventLogger:   TXXX: description=segmentmetadata: values=[{"cmd":"ld_lat_data","broadc_r":0,"broadc_s":0,"ingest_r":1769641014369,"ingest_s":0,"transc_r":1769641014373,"transc_s":1769641014394,"stream_offset":4,"stream_loudness":-90,"segment_loudness":-89.447113}]
01-31 16:57:31.782 10052  6547  6547 D EventLogger: ]
01-31 16:57:32.284 10052  6547  6547 D EventLogger: droppedFrames [eventTime=15.78, mediaPos=4.55, window=0, period=0, 50]
01-31 16:57:32.804 10052  6547  6547 D EventLogger: droppedFrames [eventTime=16.30, mediaPos=5.02, window=0, period=0, 50]
01-31 16:57:32.929 10052  6547  6547 D EventLogger: metadata [eventTime=16.43, mediaPos=5.15, window=0, period=0
01-31 16:57:32.930 10052  6547  6547 D EventLogger:   TRCK: description=null: values=[3]
01-31 16:57:32.930 10052  6547  6547 D EventLogger:   TDEN: description=null: values=[2026-01-28T22:56:55]
01-31 16:57:32.930 10052  6547  6547 D EventLogger:   TDTG: description=null: values=[2026-01-28T22:56:55]
01-31 16:57:32.930 10052  6547  6547 D EventLogger:   TOFN: description=null: values=[index-0000000003.ts]
01-31 16:57:32.931 10052  6547  6547 D EventLogger:   TSSE: description=null: values=[0576bf0e6e08f90f76d0d1094f1448769bdf2e0e-1.0.1230.0]
01-31 16:57:32.932 10052  6547  6547 D EventLogger:   TXXX: description=segmentmetadata: values=[{"cmd":"ld_lat_data","broadc_r":0,"broadc_s":0,"ingest_r":1769641015436,"ingest_s":0,"transc_r":1769641015475,"transc_s":1769641015485,"stream_offset":6,"stream_loudness":-90,"segment_loudness":-89.4333}]
01-31 16:57:32.932 10052  6547  6547 D EventLogger: ]
01-31 16:57:33.407 10052  6547  6547 D EventLogger: droppedFrames [eventTime=16.90, mediaPos=5.68, window=0, period=0, 50]
01-31 16:57:34.091 10052  6547  6547 D EventLogger: droppedFrames [eventTime=17.58, mediaPos=6.35, window=0, period=0, 195]

That is quite the number of frame drops. I believe that the decoder is just not able to run fast enough to handle decoding all the input in time for playback.

You can try enabling dynamic scheduling with this experimental api. That would perhaps run additional work loops & quicker. You can test this out in the Demo app in PlayerActivity(https://github.com/androidx/media/blob/release/demos/main/src/main/java/androidx/media3/demo/main/PlayerActivity.java#L264) where the player is initialized.

However, judging by that there are periods of dramatic frame drops where the content skips to the next key frame(because its so late), not sure if that will help enough.

What would you expect or want the Player to do if the decoder for your device is too slow to keep up with the content?

[Dum4G]

What would you expect or want the Player to do if the decoder for your device is too slow to keep up with the content?

At this time it's hard to tell because there might be several reasons for this:

On Mibox4 device with AmlogicVideoDecoderAwesome there was a Vsync related crash:

02-04 22:21:23.591 u0_a9  3862  4118 I OpenGLRenderer: Davey! duration=844ms; Flags=0, IntendedVsync=50225431282, Vsync=50858764590, OldestInputEvent=9223372036854775807, NewestInputEvent=0, HandleInputStart=50862855082, AnimationStart=50862885207, PerformTraversalsStart=50863157832, DrawStart=51057425726, SyncQueued=51061680394, SyncStart=51061842310, IssueDrawCommandsStart=51062648019, SwapBuffers=51068463561, FrameCompleted=51070332228, DequeueBufferDuration=1859000, QueueBufferDuration=1414000,

02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai:   at androidx.media3.exoplayer.video.VideoFrameReleaseHelper$VSyncSampler androidx.media3.exoplayer.video.VideoFrameReleaseHelper$VSyncSampler.access$000(android.content.Context) (VideoFrameReleaseHelper.java:467)
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.video.VideoFrameReleaseHelper.onStarted() (VideoFrameReleaseHelper.java:163)
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.video.VideoFrameReleaseControl.onStarted() (VideoFrameReleaseControl.java:241)
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.video.MediaCodecVideoRenderer.onStarted() (MediaCodecVideoRenderer.java:1121)
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.BaseRenderer.start() (BaseRenderer.java:159)
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.RendererHolder.start() (RendererHolder.java:437)
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.ExoPlayerImplInternal.startRenderers() (ExoPlayerImplInternal.java:1232)
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.ExoPlayerImplInternal.doSomeWork() (ExoPlayerImplInternal.java:1431)
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai:   at boolean androidx.media3.exoplayer.ExoPlayerImplInternal.handleMessage(android.os.Message) (ExoPlayerImplInternal.java:711)
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai:   at void android.os.Handler.dispatchMessage(android.os.Message) (Handler.java:102)
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai:   at void android.os.Looper.loop() (Looper.java:193)
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai:   at void android.os.HandlerThread.run() (HandlerThread.java:65)
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai: Caused by: java.lang.ClassNotFoundException: Didn't find class "android.view.Choreographer$VsyncCallback" on path: DexPathList[[zip file "/data/app/androidx.media3.demo.main-OC0sz9f-jWZkfnc4YMiEFw==/base.apk"],nativeLibraryDirectories=[/data/app/androidx.media3.demo.main-OC0sz9f-jWZkfnc4YMiEFw==/lib/arm, /system/lib, /product/lib]]
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai:   at java.lang.Class dalvik.system.BaseDexClassLoader.findClass(java.lang.String) (BaseDexClassLoader.java:134)
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai:   at java.lang.Class java.lang.ClassLoader.loadClass(java.lang.String, boolean) (ClassLoader.java:379)
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai:   at java.lang.Class java.lang.ClassLoader.loadClass(java.lang.String) (ClassLoader.java:312)
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai:   at androidx.media3.exoplayer.video.VideoFrameReleaseHelper$VSyncSampler androidx.media3.exoplayer.video.VideoFrameReleaseHelper$VSyncSampler.access$000(android.content.Context) (VideoFrameReleaseHelper.java:467)
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.video.VideoFrameReleaseHelper.onStarted() (VideoFrameReleaseHelper.java:163)
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.video.VideoFrameReleaseControl.onStarted() (VideoFrameReleaseControl.java:241)
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.video.MediaCodecVideoRenderer.onStarted() (MediaCodecVideoRenderer.java:1121)
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.BaseRenderer.start() (BaseRenderer.java:159)
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.RendererHolder.start() (RendererHolder.java:437)
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.ExoPlayerImplInternal.startRenderers() (ExoPlayerImplInternal.java:1232)
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.ExoPlayerImplInternal.doSomeWork() (ExoPlayerImplInternal.java:1431)
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai:   at boolean androidx.media3.exoplayer.ExoPlayerImplInternal.handleMessage(android.os.Message) (ExoPlayerImplInternal.java:711)
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai:   at void android.os.Handler.dispatchMessage(android.os.Message) (Handler.java:102)
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai:   at void android.os.Looper.loop() (Looper.java:193)
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai:   at void android.os.HandlerThread.run() (HandlerThread.java:65)
02-04 22:23:52.270 10052  6748  6777 I edia3.demo.mai: 
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai: Rejecting re-init on previously-failed class java.lang.Class<androidx.media3.exoplayer.video.VideoFrameReleaseHelper$VSyncSamplerV33>: java.lang.NoClassDefFoundError: Failed resolution of: Landroid/view/Choreographer$VsyncCallback;
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai:   at androidx.media3.exoplayer.video.VideoFrameReleaseHelper$VSyncSampler androidx.media3.exoplayer.video.VideoFrameReleaseHelper$VSyncSampler.access$000(android.content.Context) (VideoFrameReleaseHelper.java:467)
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.video.VideoFrameReleaseHelper.onStarted() (VideoFrameReleaseHelper.java:163)
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.video.VideoFrameReleaseControl.onStarted() (VideoFrameReleaseControl.java:241)
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.video.MediaCodecVideoRenderer.onStarted() (MediaCodecVideoRenderer.java:1121)
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.BaseRenderer.start() (BaseRenderer.java:159)
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.RendererHolder.start() (RendererHolder.java:437)
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.ExoPlayerImplInternal.startRenderers() (ExoPlayerImplInternal.java:1232)
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.ExoPlayerImplInternal.doSomeWork() (ExoPlayerImplInternal.java:1431)
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai:   at boolean androidx.media3.exoplayer.ExoPlayerImplInternal.handleMessage(android.os.Message) (ExoPlayerImplInternal.java:711)
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai:   at void android.os.Handler.dispatchMessage(android.os.Message) (Handler.java:102)
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai:   at void android.os.Looper.loop() (Looper.java:193)
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai:   at void android.os.HandlerThread.run() (HandlerThread.java:65)
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai: Caused by: java.lang.ClassNotFoundException: Didn't find class "android.view.Choreographer$VsyncCallback" on path: DexPathList[[zip file "/data/app/androidx.media3.demo.main-OC0sz9f-jWZkfnc4YMiEFw==/base.apk"],nativeLibraryDirectories=[/data/app/androidx.media3.demo.main-OC0sz9f-jWZkfnc4YMiEFw==/lib/arm, /system/lib, /product/lib]]
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai:   at java.lang.Class dalvik.system.BaseDexClassLoader.findClass(java.lang.String) (BaseDexClassLoader.java:134)
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai:   at java.lang.Class java.lang.ClassLoader.loadClass(java.lang.String, boolean) (ClassLoader.java:379)
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai:   at java.lang.Class java.lang.ClassLoader.loadClass(java.lang.String) (ClassLoader.java:312)
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai:   at androidx.media3.exoplayer.video.VideoFrameReleaseHelper$VSyncSampler androidx.media3.exoplayer.video.VideoFrameReleaseHelper$VSyncSampler.access$000(android.content.Context) (VideoFrameReleaseHelper.java:467)
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.video.VideoFrameReleaseHelper.onStarted() (VideoFrameReleaseHelper.java:163)
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.video.VideoFrameReleaseControl.onStarted() (VideoFrameReleaseControl.java:241)
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.video.MediaCodecVideoRenderer.onStarted() (MediaCodecVideoRenderer.java:1121)
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.BaseRenderer.start() (BaseRenderer.java:159)
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.RendererHolder.start() (RendererHolder.java:437)
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.ExoPlayerImplInternal.startRenderers() (ExoPlayerImplInternal.java:1232)
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai:   at void androidx.media3.exoplayer.ExoPlayerImplInternal.doSomeWork() (ExoPlayerImplInternal.java:1431)
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai:   at boolean androidx.media3.exoplayer.ExoPlayerImplInternal.handleMessage(android.os.Message) (ExoPlayerImplInternal.java:711)
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai:   at void android.os.Handler.dispatchMessage(android.os.Message) (Handler.java:102)
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai:   at void android.os.Looper.loop() (Looper.java:193)
02-04 22:23:52.271 10052  6748  6777 I edia3.demo.mai:   at void android.os.HandlerThread.run() (HandlerThread.java:65)

On TCL TV with OMX.realtek.video.decoder related crash was never reproducible but VsyncDiff issue still clearly present

02-07 18:31:37.063  1000   383   821 W VideoClient: ignore error diff vSyncDiff=108143 average=0
02-07 18:31:37.659  1000   383   821 W VideoClient: ignore error diff vSyncDiff=122738 average=0
02-07 18:31:37.659  1000   383   821 W VideoClient: ignore error diff vSyncDiff=67000 average=49741
02-07 18:31:37.775  1000   383   821 W VideoClient: ignore error diff vSyncDiff=115864 average=0
02-07 18:31:37.889  1000   383   821 W VideoClient: ignore error diff vSyncDiff=114049 average=0
02-07 18:31:37.997  1000   383   821 W VideoClient: ignore error diff vSyncDiff=108064 average=0
02-07 18:31:38.129  1000   383   821 W VideoClient: ignore error diff vSyncDiff=131228 average=0
02-07 18:31:38.129  1000   383   821 W VideoClient: ignore error diff vSyncDiff=67000 average=49741
02-07 18:31:38.292  1000   383   821 W VideoClient: ignore error diff vSyncDiff=163061 average=0
02-07 18:31:38.292  1000   383   821 W VideoClient: ignore error diff vSyncDiff=1116000 average=49741
02-07 18:31:38.396  1000   383   821 W VideoClient: ignore error diff vSyncDiff=104640 average=0
02-07 18:31:38.499  1000   383   821 W VideoClient: ignore error diff vSyncDiff=102953 average=0
02-07 18:31:38.499  1000   383   821 W VideoClient: ignore error diff vSyncDiff=59000 average=49741
02-07 18:31:38.600  1000   383   821 W VideoClient: ignore error diff vSyncDiff=101209 average=0
02-07 18:31:38.724  1000   383   821 W VideoClient: ignore error diff vSyncDiff=123566 average=0
02-07 18:31:38.724  1000   383   821 W VideoClient: ignore error diff vSyncDiff=75000 average=49741
02-07 18:31:38.834  1000   383   821 W VideoClient: ignore error diff vSyncDiff=109806 average=0
02-07 18:31:38.955  1000   383   821 W VideoClient: ignore error diff vSyncDiff=121082 average=0
02-07 18:31:38.955  1000   383   821 W VideoClient: ignore error diff vSyncDiff=67000 average=49741
02-07 18:31:39.066  1000   383   821 W VideoClient: ignore error diff vSyncDiff=111465 average=0
02-07 18:31:39.173  1000   383   821 W VideoClient: ignore error diff vSyncDiff=106579 average=0
02-07 18:31:39.174  1000   383   821 W VideoClient: ignore error diff vSyncDiff=67000 average=49741

If that's the case a Vsync alghoritm might be enhanced to fallback for 24Hz or 30Hz at any cost. So far MX Player is the only player that sustains such framerate with this video and doesn't use SW codec for that.

Another issue might be in non-integer padding that bottlenecks the codec. That's something I need to test later on resolutions dividable by 16. What I know for sure is that the codec is capable to run 864p100 streams just fine on TCL TV