linkedin / linkedin/LiTr

Increasing Frame Rate?

Open
#264 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
663
Forks
92
PR merge metrics
No merged PRs in 30d

Description

@izzytwosheds
This library has saved me a significant amount of time. I was on the verge of diving deep into the wormhole of implementing the MediaCodec from scratch, so I truly appreciate your assistance.

I have a query that might seem unusual, but I'm hopeful you might have a solution or at least guide me in the right direction.

Here are the scenarios I'm looking at:

**Input:** 1920x1080 resolution at 30fps, h264 (video/avc)
**Output:** 1280x720 resolution at 120fps, h264 (video/avc)

**Input:** 1920x1080 resolution at 60fps, h264 (video/avc)
**Output:** 1280x720 resolution at 120fps, h264 (video/avc)

I understand the frames required for 120fps don't actually exist in the input. However, is there a way to auto-multiply or duplicate the existing frames to achieve this?

Separately, I also have this scenario which I believe is achievable. I'll be working on it over the next few days:

**Input:** 1920x1080 resolution at 30fps, 40-second video, h264 (video/avc)
**Output:** 1280x720 resolution at 120fps, 10-second video, h264 (video/avc)

For the latter scenario, I assume that by simply setting (MediaFormat.KEY_FRAME_RATE, 120) I can get the desired result. But I'm still not certain about how to approach the first two scenarios mentioned above.

Thanks once again for all your help!

Best regards,
Joe

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the library's MediaCodec and MediaFormat handling, focusing on how KEY_FRAME_RATE is applied to transcoding. Compare that behavior with the requested frame-duplication cases and the proposed 30-to-120fps duration change. Done means establishing whether these scenarios are supported and identifying the required scope for a safe implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.