Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

screen share resolution is not work

未关闭
#416 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
dart, flutter

调研方向

Start by reading the screen-share track creation and publishing code, especially LocalVideoTrack.createScreenShareTrack and the handling of ScreenShareCaptureOptions; the issue does not name source files or tests. Compare the requested 1280×720 dimensions and frame-rate constraints with the constraints passed to getDisplayMedia on Windows and macOS. Done means screen sharing uses the requested resolution on both platforms; first confirm the behavior and relevant code paths with maintainers.

由索引模型根据 Issue 内容生成。

描述

localVideoTrackFuture = LocalVideoTrack.createScreenShareTrack(
      ScreenShareCaptureOptions(
        params: VideoParameters(
          dimensions: VideoDimensions(1280, 720),
          encoding: const VideoEncoding(
            maxBitrate: 2500 * 1000,
            maxFramerate: 15,
          ),
        ),
        sourceId: sourceId,
        maxFrameRate: 30.0,
      ),
    );

var localVideo = await localVideoTrackFuture!;
        var a = await plasoRoom.room.localParticipant!.publishVideoTrack(
          localVideo,
          publishOptions: const VideoPublishOptions(
            simulcast: false,
            videoCodec: "VP8", //"VP8"
          ),
        );

in the above code, I set the screen resolution to 1280x720, and when call "rtc.navigator.mediaDevices.getDisplayMedia(constraints);" the constraints is

{audio: false, video: {width: 1280, height: 720, frameRate: 15, deviceId: {exact: 724049430}, mandatory: {frameRate: 30.0}}}

both windows and macos has such problem, but the resulotion is correct in chrome ,maybe it is a bug of flutter_webrtc, as all experts are here , so I put it here first

主要语言
Dart
星标
421
派生
260
平均合并
2 天 5 小时
30 天内合并 PR
17

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

livekit/client-sdk-flutter 的其他 Issue

查看 livekit/client-sdk-flutter 的全部 Issue

相似的 Issue

更多 Dart Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。