Opened 3 years ago
Last modified 12 months ago
#9473 new defect
gdigrab screen captures are interrupted by secure desktop pop-ups
Reported by: | leopold84 | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | ffmpeg |
Version: | git-master | Keywords: | gdigrab |
Cc: | leopold84 | Blocked By: | |
Blocking: | Reproduced by developer: | no | |
Analyzed by developer: | no |
Description (last modified by )
Summary of the bug:
If you start screen capture with gdigrab and any secure desktop pop-up will appear (UAC or anything else), capture immediately stops.
How to reproduce:
- Start screen capture using gdigrab device as input
ffmpeg -f gdigrab -framerate 30 -i desktop output.mkv
- Launch any program as administrator or make a secure desktop to appear any other way
- Once returned to the normal desktop, you will see that capture has stopped with the error similar to this one
Failed to capture image (error 5)trate= 2.2kbits/s speed=0.54x desktop: I/O error
Expect result:
If it's not possible to capture secure desktop with gdigrab, it at least shouldn't interrupt the recording (i.e. back screen can be captured while secure desktop is present).
Attachments (1)
Change History (6)
by , 3 years ago
Attachment: | ffmpeg-20211024-181600.log added |
---|
comment:1 by , 3 years ago
Description: | modified (diff) |
---|
follow-up: 4 comment:3 by , 3 years ago
Priority: | important → normal |
---|
This is not a regression, so decreasing priority.
Have you tried running ffmpeg with elevated privileges?
This looks like an enhancement request for an option which enables capturing black frames when BitBlt fails. BitBlt can fail also for locked screen, no display, etc.
comment:4 by , 3 years ago
Replying to Marton Balint:
This is not a regression, so decreasing priority.
Have you tried running ffmpeg with elevated privileges?
This looks like an enhancement request for an option which enables capturing black frames when BitBlt fails. BitBlt can fail also for locked screen, no display, etc.
Running ffmpeg from elevated Command Prompt was the first thing I tried, this doesn't help.
However, I think you might be right regarding the cause of this problem because capture fails with the same error after UAC pop-up and after screen lock.
comment:5 by , 12 months ago
+1, would be great to have the option to continue capture with a blank screen when this happens
Report