Unintended behavior about windows-timelapse-toolkit HOT 5 CLOSED

That's interesting! Thanks for reporting!

There was a PR years ago that addressed a similar issue:

• #6

My guess is that Windows released some new feature related to the screen scaling that isn't supported by the 6-yo screenCapture.exe.

Before that PR, I used to recommend users to use Windows10_DPI_FIX.exe to fix issues related to screen scaling, but I'm not sure if this would work nowadays.

Unfortunately, I'm not using Windows anymore. Let's leave this issue open in the hope someone can come up with an idea to solve it 🙏

P.S. I once started rewriting windows-timelapse-toolkit using https://github.com/jangxx/node-win-desktop-duplication for capturing the screen. This should be a good starting point; I know it handles the screen scaling correctly due to the usage of Windows' Desktop Duplication API.

from windows-timelapse-toolkit.

Ah, I just noticed one thing: I haven't made a release after #6 was merged.

Could you confirm if you are using v1.1.0 or the main branch of a clone of this repository?

If you're using v1.1.0, that might be the reason of the issue, and you should try downloading master and running it instead. If it works, I'll update the Readme.

from windows-timelapse-toolkit.

Downloaded the master, everything works as expected! Cheers (and congrats on this handy little tool I really appreciate it)! 🥳

from windows-timelapse-toolkit.

Yep, using v1.1.0; got it from the releases section.

Onto downloading the master!

from windows-timelapse-toolkit.

Awesome, thank you for confirming!
I'll update the readme and get a new release out right away.

from windows-timelapse-toolkit.