Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Streaming FPS and recording FPS

Open
  • Is something wrong?
#1,974 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
Over a week
Newbie friendliness
18/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
android, kotlin
Domain
audio-video-rtc, mobile-dev

Research direction

The report concerns frame rate drift on a real Pixel 8 Pro when prepareVideo is called with fps 60, so the entry point is the video encoding path in the library's Kotlin sources, not the sample app's call site. Reproduce with the onFps callback and compare the requested rate against the rate the encoder actually delivers, then check the recording output. Done would mean a clear explanation of the capped frame rate, ideally with a fix or a documented limit, confirmed on a device.

Written by the indexing model from the issue text.

Description

When I set the fps to 60

genericStream.prepareVideo(
                    width = streamWidth,
                    height = streamHeight,
                    bitrate = streamBitrateBps,
                    fps = 60,
                    iFrameInterval = KEY_FRAME_INTERVAL_SECONDS,
                    rotation = STREAMING_ROTATION,
                    recordWidth = recordWidth,
                    recordHeight = recordHeight,
                    recordBitrate = recordBitrateBps
                )

However in onFps callback the streaming fps keep changing, from 25-32, never 60.

For recording I checked the file, it is around 27 fps

phone is Google Pixel 8 Pro Real device

Dominant language
Kotlin
Stars
3k
Forks
946
Avg merge
3d 22h
Merged PRs (30d)
10

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from pedroSG94/RootEncoder

All issues in pedroSG94/RootEncoder

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.