screen share resolution is not work
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- audio-video-rtc
Research direction
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.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- Dart
- Stars
- 421
- Forks
- 260
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 11
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from livekit/client-sdk-flutter
-
`jwtPayload.roomConfiguration` returns null fields for tokens from LiveKit server SDKsPossibly taken @RaphaelFakhri claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
livekit/client-sdk-flutter#1243 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 57/100
livekit/client-sdk-flutter#1245 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
livekit/client-sdk-flutter#1227 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
livekit/client-sdk-flutter#1221 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
livekit/client-sdk-flutter#1219 · 1 reaction ·
Maintainers usually reply within 1 day
All issues in livekit/client-sdk-flutter
Similar issues
-
Missing workoutsOpenenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
InlitX/GymMane#237 · 1 comment ·
Maintainers usually reply within 5 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Abhinivesh2729/Thinai#41 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
0niel/university-app#617 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
linagora/tmail-flutter#5010 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day