-
-
Notifications
You must be signed in to change notification settings - Fork 94
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
Issue with loading times and "slow" behavior, using only one screen on Mac OS #1041
Comments
Thank you! I have still not encountered this issue myself, but there are some people reporting it. Please check out this to ensure the output screen capture is not active if you are not using it: Let me know if that helps! |
@BillyDaBones when this happens, can you please check what is the CPU usage on the machine? This morning, i restarted the computer, and now this issue doesn't happen anymore. |
That's the first thing I checked, and I forgot to include it in the first post. If I'm reading it correctly (Im more windows friendly) |
Ph, this makes sense. I had this enabled initially, then disabled it but never rebooted. I'm gonna try to reproduce the error on Windows 10. I'll report my results here in a few minutes. |
Weird. I turned on "Output Show", and althought i saw an increase in CPU usage, it didn't go to 100%. |
First off, thanks for a fantastic app that is so well fleshed out. Looking forward to the future of it. This is my first time trying it.
Describe the bug
General "slow" behavior with animations and or clicking items, for example, switching to the "edit" tab, takes a couple of milliseconds longer. Selecting any items from the Media menu also takes longer to load and appear on the screen. This only occurs with no displays connected. However, it occurs throughout the application when I connect an external display and switch the output in the FreeShow settings. The bug is definitely noticeable but not a critical problem for my workflow.
Reproducing
I have an M3 Pro Mac with Sequoia 15.0, with no displays connected. I suspect this is primarily a mismanagement of performance and Apple doing Apple MacOS things with weird behavior.
Version (Optional)
The text was updated successfully, but these errors were encountered: