Capture OnFrame Callback very slow on Win11 23H2 about windows.ui.composition-win32-samples HOT 7 CLOSED

Verified. If the shared content changing, then have no issue.

from windows.ui.composition-win32-samples.

Are things changing on screen? There have been improvements recently to cut down on sending frames where there are no changes from the previous frame.

from windows.ui.composition-win32-samples.

@robmikh Does there have any doc about this improvement? I will verify this with QA. Because I doubt this point at first, but I not find any release note about this improvement

from windows.ui.composition-win32-samples.

We don't have anything documenting this improvement at the moment.

I have heard something similar from another group, but it was in their automated tests where the screen wasn't updating frequently. Moving the mouse around or capturing an application that constantly presents a swap chain made the FrameArrived event fire more frequently. I would not be surprised if this is similar but let me know if not.

from windows.ui.composition-win32-samples.

btw, the improvment is quite bad.. at least callback 1 fps....

from windows.ui.composition-win32-samples.

We'll take that feedback into consideration, but eliminating unneeded rendering work has been a consistent request from our partners.

What's your scenario where maintaining a minimum capture rate is needed?

I'm closing this issue but feel free to add more information that we can take into consideration in the future.

from windows.ui.composition-win32-samples.

I need know that capturer still alive and working. If you think callback too much, and waste memory, just give me the callback, with empty frame, or with specific error/return code.
And most basiclly, it's really need to have a doc for such change, I search again and again in the existing MSDN.....

from windows.ui.composition-win32-samples.