Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Fills and Dropped Frames Under Restricted Bandwidth (3 Mbps)

オープン
  • 何か問題がありますか？
#2,177 コメント 44 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 2 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
35/100
issue の種類
バグ
明瞭さ
説明が足りない
活発さ
静か
技術スタック
android, kotlin
領域
audio-video-rtc, mobile-dev

調査の方向性

The issue names no source files, tests, or entry points to start from. First compare the reported v2.7.0 and v2.8.0 cases using the requested encoder configuration, bitrate/resolution settings, and logs across the listed devices and bandwidth conditions. Done means narrowing down the cause of the fills, dropped frames, and audio/video interruptions, or establishing a reliable recommended configuration.

索引モデルが issue の本文から書いたものです。

説明

Hello,
We recently updated RootEncoder from v2.7.0 to v2.8.0 and have been testing streaming across different Samsung device models.
Note : It is happening when adding filters.
Below are our observations:

  1. Without bandwidth restriction
    Streaming works fine on most devices.
    On Samsung S22, we are observing fills and dropped frames.
    When streaming continuously for more than one hour, the S22 device also gets heated.
    We are observing these issues even when the network connection is stable.
    On Samsung A17, & Samsung M56 we have not observed these issues.
  2. With bandwidth restricted to 3 Mbps
    With the bandwidth restricted to 3 Mbps, we are observing fills and dropped frames.
    We also noticed that audio and video are missed/interrupted at certain points during the stream. When checking the stream in MediaLive, we are seeing audio and video alerts.
    We also tested the same 3 Mbps restricted bandwidth scenario with RootEncoder v2.7.0, and we observed similar behavior, including the audio alerts.
    So, the audio/video issue under the 3 Mbps bandwidth restriction does not appear to be specific to v2.8.0.
  3. Devices tested
    Samsung S22 – Occur fills and dropped frames with and without restriction; device heating during long streaming
    Samsung S24 – Samsung A17 – Without restriction working fine.
    Samsung M56 – Occur fills and dropped frames with 3 Mbps bandwidth restriction
    Questions
    Could you please help us understand:
    Why are we seeing fills and dropped frames on some Samsung models, particularly the S22, even when the network is stable?
    With bandwidth restricted to 3 Mbps, why are we seeing fills/dropped frames and audio/video interruptions?
    Since we also see similar audio alerts with v2.7.0 under the same 3 Mbps restriction, could this be related to the encoder, bitrate, network handling, or device behavior rather than the v2.8.0 upgrade?
    Is there any recommended configuration or approach in RootEncoder to handle these scenarios more reliably?
    Please let us know if you need any additional logs, encoder configuration, bitrate/resolution settings, or other details from our side.
    Thank you.
主要言語
Kotlin
スター
3k
フォーク
946
平均マージ
4日 6時間
マージ済み PR（30日）
9

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

pedroSG94/RootEncoder のほかの issue

pedroSG94/RootEncoder の issue をすべて見る

似ている issue

Kotlin の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。