-
Due to macOS, GPU, monitor connection type, in some cases the cursor "burns in" and can't be controlled. Make sure monitors are directly connected using HDMI or Thunderbolt.
-
The issue started acting intermittently in screen flow 9 and I was told by you all that it was a bug. The same thing happens with 10. I can randomly open SF up and the warning isn't there.
-
Brandon Craft Please test in ScreenFlow 10.0.2
-
-
I get this same message using Screenflow 10.0.3 on a MacBook Pro running MacOS 11.5.1. Since it's a laptop this can't be a monitor connection issue.
-
Philip Roybal I am not experiencing the issue with the most recent update. The issue I was having is that my MBP would take the permission away each time I restarted. This no longer happens.
-
Philip Roybal Generally that message means macOS is preventing the cursor from being captured independently. That's info ScreenFlow gets from the OS and hardware. If you're seeing this message we'd need complete details on your hardware including all monitors and how attached and what you're trying to capture.
Philip Roybal said:
Since it's a laptop this can't be a monitor connection issue.It can be depending on other details.
-
CraigS Thanks for the reply. The hardware is a 15" MacBook Pro (2017) with no external monitors or peripherals attached. I was creating a demo video for part of the https://www.maialearning.com website by clicking through various screens.
Oddly enough, when I just now checked Screenflow I don't see the problem and am able to scale/hide the cursor. Could this be some sort of permissions issue somewhere?
-
Brandon Craft Thanks, Brandon. Was it taking away the Screen Recording permission or something else? In my case it would copy the screen but wouldn't let me hide/scale the cursor.
-
Philip Roybal If I'm not mistaken, it was the input monitoring permission that kept "resetting" on the earlier 10.?? version of SF. The two most recent updates have fixed this.
-
-
Philip Roybal said:
Oddly enough, when I just now checked Screenflow I don't see the problem and am able to scale/hide the cursor. Could this be some sort of permissions issue somewhere?Quite possibly. Perhaps just a momentary gremlin. See if it happens again and if so grab a screenshot of the warning.
-
Philip Roybal said:
In my case it would copy the screen but wouldn't let me hide/scale the cursor.That should work when using only an internal monitor of a laptop or iMac (unless a program is doing something to take control of that). Generally, some external monitors and how they interface with macOS cause that issue. So do be on the lookout if that happens again. Permissions issues though have been a bit "odd" in Big Sur though.
-
Brandon Craft said:
it was the input monitoring permissionYes, we've been tweaking.
-
Same issue here on v10.0.3 regardless of screen and connection used. I tried adding ScreenFlow to Input Monitoring, but that didn't make a difference. If anyone finds a fix, please post.
-
Eddie Smith said:
regardless of screen and connection usedWe need more details if you would like help troubleshooting. There are some configurations in which macOS won't give ScreenFlow independent control of the mouse and ScreenFlow will give you a warning message when that happens. We can't troubleshoot general statements. It must be a setup we can reproduce.
-
CraigS Is it possible to provide what those configurations are? If so, I think it would be helpful to have a hyperlink to see what needs to be changed when that message appears in the Configure Recording window.
-
Eddie Smith We need your system config in order to determine if there's an issue. We may not know every variant in which the OS prevents ScreenFlow from having cursor control. Docks and hubs can be a problem. Display Link and Sidecar can be a problem. Monitors with USB inputs (rare but they exist) might be a problem. The only way to examine is for you to provide use with your configuration because there may be other combinations.
-
-
Same issue here CraigS
Macbook Pro (13-inch 2020) running macOS Big Sur w/ a BenQ PD2700U attached running ScreenFlow 10.0.3.
Getting this:
Even though permissions look fine:
-
Kyle Weeks said:
BenQ PD2700U attachedHow it is attached is significant. Please describe exactly in such a way we can attach a similar monitor.
The information about the mouse cursor comes from operating system information. It is the operating system, how the monitor is attached, third party software and drivers that result in that message. Generally OS is making such limitations. We can only evaluate the accuracy of the message with complete configuration.-
CraigS It's attached w/ an HDMI -> USB-C cable
-
Kyle Weeks said:
It's attached w/ an HDMI -> USB-C cableDirectly or through a hub or dock?
Have you updated to macOS 11.5.1? (please do so if you haven't).
Something like this cable?
Are you using DisplayLink?
Do you have ManyCam installed? -
CraigS Directly–no hub/dongle/dock.
But the issue resolved itself when I upgraded to 11.5.1. Thanks for the tip!
-
-
Kyle Weeks said:
the issue resolved itself when I upgraded to 11.5.1. Thanks for the tip!Thanks for reporting and confirming.
-
CraigS ... Are there issues with mouse cursors being monitored while screen recording (with ScreenFlow), while I am streaming at the same time with OBS? That may be the issue that I am having. It seems that when I am using OBS to stream and I'm recording at the same time, I get the notification in screenflow that the mouse cursor will not be adjustable in your screen recording.
-
Brandon Craft said:
at the same time with OBS? That may be the issue that I am having.OBS screen capture or other aspects might impact access to the cursor. If you quit OBS and reboot (to release resources) can ScreenFlow 10.0.3 then capture and adjust the mouse cursor? Make sure you're on macOS 11.5.2 if you're on Big Sur
-
CraigS Yeah. I definitely think it is OBS conflicting with access to the cursor. Once I was done streaming last night, I closed OBS, and jumped straight back into ScreenFlow with a new recording and I no longer got the warning, even without restarting. I'm going to investigate further to see if I can disable some settings in OBS to make it work. Not a deal-breaker if it doesn't. However, this leads me to another question though... just curious. If I need to post elsewhere, I can definitely do that...
I can add a callout action in ScreenFlow and that will still "track" the mouse cursor, whether cursor monitoring was working or not. I'm not looking for a technical answer, but it seems if ScreenFlow could track that, then I wonder why we can't replace that tracked area with a different cursor. I know the clicking isn't monitored, but I mainly use the input tracking to change my cursor to a larger .png for easier viewing.
This has been my workaround by the way when input monitoring cannot be monitored. I'll add a callout and apply it to the mouse cursor, slightly change the settings to the callout (make the cursor area slightly brighter than the background, up the size just a hair), just so the viewer can still see what I am pointing at on the screen. I am a college math instructor so my screen recordings rely heavily on the mouse cursor as I am pointing out things and obviously writing things down.
It may be a long shot, but sometime in a future update, the callout action could have an option to replace the tracked mouse cursor area with an image as well... ;)
Thanks for responding.
-