Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When the Android client uses H264 encoding, the video resolution is lower than the published resolution, causing a green screen problem. #2712

Open
boolw opened this issue May 10, 2024 · 3 comments

Comments

@boolw
Copy link

boolw commented May 10, 2024

Describe the bug
When making a video call using LiveKit Example.apk, set the video encoding to H264 and the publishing resolution to 720x1280. When the actual video resolution is lower than this value, a green screen phenomenon will appear at the bottom part of the video.

Server

  • livekit-server version 1.6.0

Client

  • LiveKit Example
  • Android

Steps to reproduce

  1. Open LiveKit Example.
  2. Set the video encoding to H264 and the publishing resolution to 720x1280.
  3. Publish a video stream with an actual resolution lower than 720x1280.
  4. Observe the video display on the receiving end.

Expected behavior
The video should display normally regardless of whether the actual resolution is lower than the set publishing resolution.

actual behavior
When the actual resolution of the video is lower than 720x1280, a green screen appears on the bottom part of the video.

Screenshots
photo_2024-05-10_16-08-33

@cnderrauber
Copy link
Contributor

Did you enable simulcast? The server will not touch video data if simulcast is disabled, you can check the encoding frame is correct when publisher encoder scales down the resolution, or the subscriber render frame has issue.

@boolw
Copy link
Author

boolw commented May 22, 2024

I just tried it. There is a green screen when simulcast is turned on or off. I adjusted the resolution from 1280720 to 640480 and the green screen still appears. The phone with the problem is: HONOR 9x

@cnderrauber
Copy link
Contributor

It sounds like a device encoder issue, are you using hardware encoder or software?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants