-
-
Notifications
You must be signed in to change notification settings - Fork 11k
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
Black borders displayed; CTRL+X / double clicking is ignored. #548
Comments
Nevermind... I realized the black bars on the left and right side are there on the phone (the test video's AR did not match my phone's display)... and since my phone's AR does not match my desktop's display, I end up with additional black bars at the top and bottom... -- I can fix this with cropping if I need to. Please disregard. |
hello, did you manage to get the black borders out for use with the full screen? |
If the device screen and the computer screen don't have the same aspect ratio, either:
Scrcpy always preserve aspect ratio, so 3 is not possible. You could crop bottom and top (or left and right) for the capture so that the aspect ratio is the same. Otherwise, you get black borders. |
I am mirroring the secondary screen of a j8 on my pc with scrcpy and it looks complete, can't I do that? |
I try to do the same as I do on the samsung j8, which is to simulate a secondary screen of 1280x720 213 dpi, this way if I run scrcpy --display, it opens with the entire screen occupied but when doing it on my main smartphone when executing scrcpy --display I get a black screen |
How can I do the second option? |
my screen is 720x1600 |
Running the following command to launch the 64-bit build linked from
readme.md
on master:The window is rendered as full screen, always on top, but there is black bars around all four edges of what's displayed. Double clicking on any of them or pressing CTRL+X is ignored. There's no way to stretch the video to fit the screen AFAICT. -- Perhaps this is a documentation bug? Not sure.
The text was updated successfully, but these errors were encountered: