[Bug] Captured window does not match the pre-selected area on high resolution screens with multiple different sizes

[DevTKSS]

Describe the bug A clear and concise description of what the bug is. since I upgraded my hardware set to High resolution + 2 x ~32" Monitors + left one existing smaller Monitor ~22" the recording of one whole monitor screen does not longer work at all (I dont even get a recording at all which I could save or work with) or choosing a area recording, the resulting recording does not match the area I choosen (way smaller part of it)

To Reproduce Steps to reproduce the behavior:

1. Go to "Record"
2. Click on 'capture area'
3. Select what you want to capture on the high resolution monitor
4. See that the captured area you get in the end is not at all matching the previously selected area

Expected behavior A clear and concise description of what you expected to happen.

Should get a capture of the area I selected

Screenshots If applicable, add screenshots to help explain your problem.

actual recording via your app: what I do get:

what Area you should be seeing:

Desktop (please complete the following information):

• OS: Windows 11 Pro

Graphic Card: Nvidia GeForce RTX4070 Ti

Monitors used: 2x large: 2560x1440 (Gawfolk) Small screen: 1920x1080 (Samsung from about 2014, which I had 2 of in my previous working setup) 59Hz

Additional context Add any other context about the problem here.

Until fixed, this app is sadly not longer usable for me! Please fix it, its such a great tool!

[fz0000]

Dup of #1352 ?

Not sure what’s causing it, but you could try the new recorder UI or just delete the old Settings.xaml to reset the settings.

[DevTKSS]

@fz0000 how to try this new recorder UI? I think I am using the new one already. and I even reinstalled it... should have deleted everything isnt it? and to the other report, I can no asian languages, but the image looks familiar. I mean, of course you can just close all issues, but fixing them would also be an option ;) I checked out your src but I dont think I will install the old net7 workloads 😆 I am fine with .NET9

[fz0000]

I ran into this issue before, but I can't seem to reproduce it now. Not sure whether it's caused by something in the old settings or only occurs when a new monitor is added.

You could click the X button to delete the old settings files first:

Then relaunch the app to try recording again.

Another suggestion is to try different recorder UIs and capture modes in the recorder settings (though I'm not sure if it'll work) :

[DevTKSS]

@fz0000 🤔 so I have had the DirecX settings activated and the storage section has a total difference path then yours👀 The Ethernet is currently broken here and GH mobile isnt able to upload photos 😅 I did install via ms store and the local path is: C:\Programm Files\WindowsApps\33823Nicke.ScreenToGif_2.41.5.0_x64__99xjgbc30gqtw\Settings.xaml

I can not remove this, its disabled grey. I do have the FFmpeg downloaded, does this influence somehow? Not sure for what this was again. I mostly doing gif and very few times mp4 I think...

[DevTKSS]

@fz0000 jup checked right now. Its the directx causing this👍 but this other one you suggested is so bad graphics thats nothing I could use🫣 does this maybe help you fix it?

Don't know how you record that, but... In Uno apps this is using SkiaRenderer which is really great rendering engine I think. Maybe this could be an alternative? But I don't know if thats just a renderer thats displaying the app UI or also for recording usable😅

[fz0000]

@DevTKSS DirectX gets the data from GPU directly, while BitBlt copies the data stored in the memory which represents a final image that can be displayed on the screen. That's why BitBlt is much slower but offers better compatibility.

A discrepancy between the GPU’s output and the displayed image usually indicates additional processing in the display pipeline that managed by the OS. Then the situation becomes complicated. You may try the following actions, including but not limited to:

• Change your system display settings to see if any setting can work: orientation, resolution, scaling (DPI), screen position, etc. (There is a known issue when using DirectX in vertical orientation)
• Verify the monitor connection, avoid using signal converters (e.g., HDMI→VGA) if possible.
• ...

If none of them works, you may have to try some other tools😅

[DevTKSS]

@fz1000 The old rendering engine output is quality of censored screen thats why its not usable.

All my screens are landscape orientation so should be okay?

The old monitor I use as third screen for e.g. screen recording application or e-mail app is hdmi to display port, the new ones are dp-dp each. Your app runned without problems when having just the old screens but I think its understandable that at some point in time we do upgrade our hardware😅

I had tryed before connecting a laptop to the three monitors but that was indeed causing issues, while the current one did not except from your app...

Do you have any idea where this is breaking so maybe if we get network connection here again (glass fiber had been cutted off from builders that were meant to add new ones) I could send it with vs2022 debugger and maybe nsight dev tools over it to Maybe find the culprit that is cutting off the screen when using this engine? Maybe I could even set a break point around there where you might know that its entering the bugged code part🤔 just idea as you tell you can not repro...

[NickeManarin]

@DevTKSS Can you open the Feedback tool, then click on Preview, take a screenshot of the "Monitors" section and paste here?

I need to check the DPI of each screen. Could be an issue of mixed DPIs.

[DevTKSS]

@NickeManarin hey there, so I send you the form from the app itself, here you can find the screenshot additionally:

[DevTKSS]

@NickeManarin do you have any state update for this bug? would like to record gifs again, but could not use this app because of that bug and I would not know of a realistic equivalent app I could use meanwhile... the old renderer is defintly not usable for me...

[DevTKSS]

@NickeManarin @fz0000 state update from my side: Unfortunatly, the recording is still not possible and needed to be fixed 🙁

Currently used Version of ScreenToGif: 2.42.1

Current Result

Equally result when using Record Monitor or Record only Window:

Expected Result

This is a Screenshot of the Area should we be seeing compared to the Currently returned result:

Editor Settings Comparison with System Settings

Opened ScreenToGif Editor after recording - Settings Register card:

Which Measurements (Abmessungen) are matching the expected measurements, reduced by the task bar hight, because I recorded the VS2026 application 👍

[!NOTE] The Scaling 125% doesn't change anything for the behavior of ScreenToGif and is just meant to adjust the size of the recorded screen for video purposes with obs Application so the YouTube Viewer on smaller Devices doesnt have to use Zoom & High resolution all the time, to see what I am showing off

Additional Information

Bug search Window Position of all Windows for next opening might be showing a part of the problem of recognization of recording the screen:

while the Current Position of all Windows view is showing up the expected results. Clicking on Move all Windows to Primary Monitor obviously changes nothing, because everything should be fine from this

Resetting Position of all Windows for next opening looked first as if it would solve the problem, but after restarting the application, re-recording with same settings, does still reproduce the issue

on reviewing this Bug search Window on this register card does show the messed up position again 🫤:

Screenshots of Application Settings

[!NOTE] Questions to the Extras:

1. Does the Version choosen for FFmpeg matter for this feature? I am using the default Setting of v5 right now, but v7 seems to be available
2. Do/should I install Gifski to enhance anything in this or for what is this used?

[!TIP] For the German Translation in this Pane from Native German speaking person side, I would suggest improving the last Line in this from currently: All diejenigen, die mich und meine Arbeit mit Rückmeldungen und Spenden unterstützen to: Und an all diejenigen... While the current wording is generally correct, if you would read it line by line, its a bit too much of just a bullet list you are naming while there are no bullets infront of it and the last line does more read like a non-bullet point sentence at first sight 👍

[DevTKSS]

Additional Note after trying with software side disconnected small screen ( -> only the 2 large screens) After selection of application and recording, we are greeted with NO recorded content at all!

(Equal Result for Only Window Recording Mode, to Monitor Recording Mode + hardware de-plugged!)