Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Can't record my screen with Screen Studio when AeroSpace is enabled #451

Closed
emiliosheinz opened this issue Aug 24, 2024 · 0 comments
Closed

Comments

@emiliosheinz
Copy link

emiliosheinz commented Aug 24, 2024

First of all, thank you for building such a great tool. I'm really enjoying it.

My setup has 3 monitor (the MacBook's built-in and two external Dell ones). When AeroSpace is enabled and I try to start a recording on a specific screen with Screen Studio, the overlays that Screen Studio should be showing individually on each screen become all cluttered in a single one which makes it impossible to start the recording.

Screenshot 2024-08-24 at 19 52 47

Disabling AeroSpace solves the issue but it is not ideal since I want to record the screen with it on.

Additionally, I've tried the following on my config but it doesn't work.

[[on-window-detected]]
if.app-id = 'com.timpler.screenstudio'
check-further-callbacks = true
run = 'layout floating'

Based on that, I believe this could be related to (1) How AeroSpace manages screens and workspaces or (2) Aerospace interfering in the way the overlays are being rendered.

AeroSpace version

❯ aerospace --version
aerospace CLI client version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201
AeroSpace.app server version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201

Let me know if I van provide any additional information.

Edit 1:

Further investigating it, it looks like what is happening is that AeroSpace is moving all the overlays to the focused screen which is making them cover each other.

Repository owner locked and limited conversation to collaborators Jan 18, 2025
@nikitabobko nikitabobko converted this issue into discussion #993 Jan 18, 2025

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant