"First Frame Freeze" on Video Rendering in Media3

[amit12kumardish]

Version

Media3 main branch

More version details

Media3 version: "1.5.1"

Devices that reproduce the issue

firetv

Devices that do not reproduce the issue

No response

Reproducible in the demo app?

Not tested

Reproduction steps

issue seen on the start of playback

Expected result

On start of the playback, video playback should be smooth

Actual result

Playback starts with first frame freeze for few millis and then it plays.

Media

Is there any specific configuration or optimization in Media3 that can help prevent the first frame freeze issue? Are there any known issues with the player initialization process or buffering that could cause this?

Bug Report

• You will email the zip file produced by adb bugreport to [email protected] after filing this issue.

[amit12kumardish]

Issue #2134

[amit12kumardish]

2025-02-13 10:08:37.614 7350-7350 EventLogger renderedFirstFrame [eventTime=583.96, mediaPos=0.00, window=0, period=0, Surface(name=null)/@0x7be9e5c] 2025-02-13 10:08:37.633 7350-7350 EventLogger rendererReady [eventTime=583.98, mediaPos=0.00, window=0, period=0, rendererIndex=0, video, true] 2025-02-13 10:08:39.231 7350-7350 EventLogger state [eventTime=585.58, mediaPos=0.01, window=0, period=0, READY] 2025-02-13 10:08:39.232 7350-7350 EventLogger isPlaying [eventTime=585.58, mediaPos=0.01, window=0, period=0, true]

see the above logs:
first frame rendered at 10:08:37 and player started playing at 10:08:39 , so there is ~2 seconds freeze of first frame , why?

any recomended solution?

[amit12kumardish]

One observation:

If i enable Tunneling, first frame freeze is fixed, but VST is high.

val trackSelector = DefaultTrackSelector(context).apply { val parameters = buildUponParameters() .setTunnelingEnabled(true) // causing vst to increase .build() setParameters(parameters) }

why this behaviour

[microkatz]

@amit12kumardish

Hi! Would you be able to share a full bug report and also the test content? If you can't share the bug report or the test content publicly, please send them to [email protected] with the subject Issue #2138. Please also update this issue to indicate you've done this.

Also were you able to reproduce this in the demo application?