Version
Media3 pre-release (alpha, beta or RC not in this list)
More version details
Media3 version 1.10.0-alpha01
Devices that reproduce the issue
Any Device
Devices that do not reproduce the issue
None
Reproducible in the demo app?
Not tested
Reproduction steps
Description:
I am encountering an issue where EditedMediaItem.Builder.setFrameRate() correctly limits the output frame rate for standard playback, but fails to do so when a SpeedChangingEffect is added to the effects pipeline.
To reproduce, simply play/Transcode an EditedMediaItem and setEffects with videoEffects using SpeedChangingEffect
Expected result
Expected Behavior:
The setFrameRate() configuration should take precedence and cap the output stream regardless of whether the speed is changed via the Builder API or the Effects pipeline.
Actual result
Observed Behavior:
When using .setFrameRate(30) without a speed effect (or using setSpeed() on the builder), the output is correctly capped at 30fps.
When adding a SpeedChangingEffect to the effects list, the .setFrameRate(30) constraint appears to be ignored or overridden, resulting in inconsistent frame pacing or a higher-than-expected output frame rate.
Media
Not applicable
Bug Report
Version
Media3 pre-release (alpha, beta or RC not in this list)
More version details
Media3 version 1.10.0-alpha01
Devices that reproduce the issue
Any Device
Devices that do not reproduce the issue
None
Reproducible in the demo app?
Not tested
Reproduction steps
Description:
I am encountering an issue where EditedMediaItem.Builder.setFrameRate() correctly limits the output frame rate for standard playback, but fails to do so when a SpeedChangingEffect is added to the effects pipeline.
To reproduce, simply play/Transcode an EditedMediaItem and setEffects with videoEffects using SpeedChangingEffect
Expected result
Expected Behavior:
The setFrameRate() configuration should take precedence and cap the output stream regardless of whether the speed is changed via the Builder API or the Effects pipeline.
Actual result
Observed Behavior:
When using .setFrameRate(30) without a speed effect (or using setSpeed() on the builder), the output is correctly capped at 30fps.
When adding a SpeedChangingEffect to the effects list, the .setFrameRate(30) constraint appears to be ignored or overridden, resulting in inconsistent frame pacing or a higher-than-expected output frame rate.
Media
Not applicable
Bug Report
adb bugreportto android-media-github@google.com after filing this issue.