-
-
Notifications
You must be signed in to change notification settings - Fork 10.7k
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
Keyboard combinations for volume buttons conflict with Mac shortcuts #300
Comments
Mwarf. I changed them from Ctrl+ I chose Ctrl+ |
For VLC on Mac, the keyboard shortcuts for changing the volume are Command-Up and Command-Down. |
@numbermaniac Thank you for the info. If you look at all the shortcuts for scrcpy, would you say that Ctrl should always be replaced by Command on MacOS? Or just for the volume? |
Other shortcuts works well on my mac except the volume. |
Yes, those two shortcuts are also built-in on Mac so they should be best kept as Control. Other shortcuts, though not conflicting with anything, might be confusing if changed to Command: Command-P usually means Print, Command-S usually means Save, Command-F for Find, and Command-B is sometimes used for Bold text. As xinx1n said, it would probably be best to just replace Ctrl with Command for the volume buttons. |
Could you test the |
Do I need to go through the full client and server building instructions for this? Is there a pre-built server I can use? |
@numbermaniac It should work with the prebuilt server from v1.4: https://github.com/Genymobile/scrcpy/blob/macos_volume/BUILD.md#prebuilt-server |
sry,I just get my macbook now. |
scrcpy --help
says that Control-Up and Control-Down are the commands for activating the volume buttons on the phone. However, these are unusable on Mac by default, because these keyboard shortcuts show you all open windows (control-up), and all the windows for the current application (control-down).This means that scrcpy doesn't receive these keyboard shortcuts, therefore not simulating the volume button presses on the connected phone.
The text was updated successfully, but these errors were encountered: