4k resolution is offset

[JeFawk]

Same problem like ShareX has (which is why i'm looking for alternatives)

Change from .zip to .webm only to see.
output.webm.zip

[maartenwiedenhof]

This makes it unusable on 4k displays. I have not found a workaround.

[potterness]

I can third this. I just upgraded to 4K. Such a shame as this was a nifty little program for me that did its job with very little fuss, but I'll have to find some other webm recorder.

[potterness]

I tried tinkering a bit and it seems the root of the problem may be related to how Windows (10) automatically changes the Display > Scale And Layout > "Change the size of text, apps and other items" setting when you switch to 4K resolution. It bumps up the size of a lot of apps to 150% of the original size, which seems to cause WebmCam to record the wrong origin. When I change this setting to 100%, WebmCam works fine running at 4K.

Of course this isn't a long term solution because I can't even see anything at the 100% setting, haha.

[JeFawk]

I started using Lightshot, not supporting 4k makes ShareX useless and I will not take any compromise for just some screenshot features.

[potterness]

Thanks for the suggestions @JeFawk . I checked out Lightshot but I need more WEBM rather than stills, so I decided to revisit ShareX after forgetting about it for 6 years and lo and behold - ShareX seems to work fine with 4K Webm recordings after you change the Task Settings > Screen Recorder > Screen Recording Options to ffmpeg and then change the video codec to VP9(WebM).

They must have updated it to work at some point since you've last used it, it seems! Works out for me :)

[JeFawk]

Thanks for the suggestions @JeFawk . I checked out Lightshot but I need more WEBM rather than stills, so I decided to revisit ShareX after forgetting about it for 6 years and lo and behold - ShareX seems to work fine with 4K Webm recordings after you change the Task Settings > Screen Recorder > Screen Recording Options to ffmpeg and then change the video codec to VP9(WebM).

They must have updated it to work at some point since you've last used it, it seems! Works out for me :)

Thanks for the workaround!