
The mouse should have been here.
I also have this problem on video recordings. Started when I added extra monitors. I have 3 monitors, 2 of which are 125% DPI scaling, and the other one is 100%. I suspect the DPI scaling is throwing it off?
I don't have any delay set up, but I think that's probably not related to this issue? I think the settings you mention for delay are to do with screenshots, not video recording...
I don't have any delay set up, but I think that's probably not related to this issue? I think the settings you mention for delay are to do with screenshots, not video recording...
Yes my bad, post deleted.
I've just realised there is another closed issue for this which details a fix... look here: #1329
I can confirm that the method described in #1329 solved my issue.
Can we see a fix for this implemented in ShareX itself
All that is required from ShareX is to automatically adding a new REG_SZ value under HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers that sets ~ HIGHDPIAWARE for the Documents\ShareX\Tools\ffmpeg.exe path when ShareX detects non-100% DPI scaling being used (or just always add the registry key -- it really wouldn't matter anyway on non-DPI scaling monitors).
This bug have had tickets created for it time and time again over the last four years, so it feels that it's time that ShareX automatically implements the necessary fix for the ffmpeg.exe file it otherwise automatically downloads and makes use of.
Most helpful comment
I can confirm that the method described in #1329 solved my issue.
Can we see a fix for this implemented in ShareX itself
All that is required from ShareX is to automatically adding a new REG_SZ value under
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layersthat sets~ HIGHDPIAWAREfor theDocuments\ShareX\Tools\ffmpeg.exepath when ShareX detects non-100% DPI scaling being used (or just always add the registry key -- it really wouldn't matter anyway on non-DPI scaling monitors).This bug have had tickets created for it time and time again over the last four years, so it feels that it's time that ShareX automatically implements the necessary fix for the
ffmpeg.exefile it otherwise automatically downloads and makes use of.