Romain Vimont
Romain Vimont
Could you please test with scrcpy v2.0, which uses an older SDL version?
OK, I can't explain why Ctrl+c does not work as expected on your machine. Scrcpy explicitly catches Ctrl+c on Windows: https://github.com/Genymobile/scrcpy/blob/bbfac9ae1fba08a045557abe9612703ace8a3890/app/src/scrcpy.c#L149 Maybe a cmd.exe configuration or something?
Interesting. I don't know why. I re-tested, for me it works as expected, I have `Recording complete to mp4 file: file.mp4` at the end when I Ctrl+c.
It you run ``` scrcpy -Vverbose --no-window --record=file.mp4 ``` then Ctrl+c, what's the full output?
Thank you. I guess this is the same with the Windows release (instead of the chocolatey package)? Something probably intercepts Ctrl+c at the system level and kills the process. Any...
Is it powershell or cmd?
> cmd What's your terminal? When I run cmd.exe, it does not look like this at all. Try with `open_a_terminal_here.bat` or Win+r, `cmd.exe`.
It looks like this: [](https://upload.wikimedia.org/wikipedia/commons/b/b3/Command_Prompt_on_Windows_10_RTM.png)
Non only, this terminal is also "limited" (it cannot be resized for example), but above all it probably correctly sends Ctrl+c to the running process.
OK, I don't know Windows very well, but IMO the behavior of Ctrl+c is definitely handled differently in your "terminal" app (whichever it is). EDIT: I guess your app is...