Weird data in onnewBitrate
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 15/100
- Issue 类型
- 缺陷
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
调研方向
Start from the BitrateAdapter wiring in onNewBitrate and adapter.adaptBitrate, then find where BitrateChecker computes the reported bitrate and whether it reads any throughput or dropped-packet signal. Reproduce by streaming while throttling the network with Network Link Conditioner (1 Mbit/s with 10% loss, then 100% loss) and logging the values passed to onNewBitrate. Done means the reported bitrate drops under these conditions, or the maintainer confirms the expected behaviour.
由索引模型根据 Issue 内容生成。
描述
Hi.
I'm trying to make sure my app is working well in bad network conditions. I'm using a BitrateAdapter connected in onNewBitrate, like the example (calling adapter.adaptBitrate from onNewBitrate).
I'm using an XCode tool from Apple, called Network Link Conditioner, where I can simulate different types of connections. When switching to a "bad network" profile that limits to 1mbit/s and 10% packetloss, webbrowsing becomes really slow and switching to a "100% loss" profile it stops completely. But in both those situations, onNewBitrate keeps reporting a "good" bitrate and doesn't seem to care that the network is bad.
The backend I'm connecting to does stop receiving packets when the limiting profiles are active, so the limiter is working, it just doesn't seem like BitrateChecker actually detects the lack of throughput. I also get no dropped packets reported from the streamer.
I'm thinking perhaps I'm missing something in the setup, but since onNewBitrate reports the "wrong" values, I don't really know what I could do differently.
- 主要语言
- Kotlin
- 星标
- 3k
- 派生
- 946
- 平均合并
- 4 天 6 小时
- 30 天内合并 PR
- 9
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
pedroSG94/RootEncoder 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 74/100
pedroSG94/RootEncoder#2213 ·
维护者通常 2 天内回复
-
难度 4/5 3-5 天 新手友好度 48/100
pedroSG94/RootEncoder#2207 · 1 个 reaction ·
维护者通常 2 天内回复
-
难度 4/5 3-5 天 新手友好度 35/100
pedroSG94/RootEncoder#2203 ·
维护者通常 2 天内回复
-
难度 4/5 3-5 天 新手友好度 45/100
pedroSG94/RootEncoder#2192 · 2 条评论 ·
维护者通常 2 天内回复
-
难度 4/5 3-5 天 新手友好度 35/100
pedroSG94/RootEncoder#2177 · 44 条评论 ·
维护者通常 2 天内回复
查看 pedroSG94/RootEncoder 的全部 Issue
相似的 Issue
-
Dev
难度 2/5 1-3 小时 新手友好度 62/100
ankidroid/Anki-Android#22555 ·
维护者通常 1 天内回复
-
enhancement good first issue help wanted
难度 2/5 1-3 小时 新手友好度 78/100
-
core: RAC_LLM_OPTIONS_DEFAULT.min_p disagrees with the IDL's annotated default可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭bug core p3
难度 2/5 1-3 小时 新手友好度 70/100
RunanywhereAI/runanywhere-sdks#1083 ·
维护者通常 5 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
area: detector eco: java help wanted lane: free-agent roadmap size: S type: parser
难度 2/5 1-3 小时 新手友好度 62/100
arminazimi/evergreen#355 ·
维护者通常 1 天内回复