[FFmpeg-trac] #9413(avdevice:new): Feature request: WindowsGraphicsCapture API
FFmpeg
trac at avcodec.org
Mon Sep 12 13:56:22 EEST 2022
#9413: Feature request: WindowsGraphicsCapture API
-------------------------------------+------------------------------------
Reporter: MB SOFT | Owner: (none)
Type: enhancement | Status: new
Priority: wish | Component: avdevice
Version: git-master | Resolution:
Keywords: gdigrab | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+------------------------------------
Description changed by MB SOFT:
Old description:
> Feature request: could you please add WindowsGraphicsCapture API as a
> method to capture a window? this would allow to capture any graphics in
> the window
>
> https://blogs.windows.com/windowsdeveloper/2019/09/16/new-ways-to-do-
> screen-capture/
>
> https://docs.microsoft.com/en-
> us/windows/win32/api/windows.graphics.capture.interop/nf-windows-
> graphics-capture-interop-igraphicscaptureiteminterop-createforwindow
New description:
This is a feature request.
Could you please modify Gdigrab to use WindowsGraphicsCapture API?
[https://blogs.windows.com/windowsdeveloper/2019/09/16/new-ways-to-do-
screen-capture/]
Advantages:
1) capture any window (including hardware accelerated window)
2) capture any graphics in the window (including transparent childs)
3) capture window outside the visible area
4) minimal cpu load even with high res and rates
Ex: here [https://github.com/mmozeiko/wcap] there are free sources of
the tool wcap that use windows graphics capture api. compared to gdigrab
it has 3 times less cpu load.
Could someone use that code and adapt gdigrab?
[https://github.com/mmozeiko/wcap/blob/main/wcap_capture.c]
--
--
Ticket URL: <https://trac.ffmpeg.org/ticket/9413#comment:11>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list