#11542: gdigrab sometimes fails to capture specific windows on some machines
-------------------------------------+-------------------------------------
Reporter: malaawar | Owner: (none)
Type: defect | Status: new
Priority: important | Component: ffmpeg
Version: git-master | Resolution:
Keywords: gdigrab | Blocked By:
Windows |
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Comment (by malaawar):
Replying to [comment:8 MasterQuestionable]:
> ͏ Log content of interest:
> [[
> Opening an input file: title=RecordingTest
[C:\Users\rache\Downloads\RecordingTest.blend] - Blender 4.2.
> [gdigrab] Found window RecordingTest
[C:\Users\rache\Downloads\RecordingTest.blend] - Blender 4.2, capturing
1920x1102x32 at (0,0)
> [gdigrab] Probe buffer size limit of 5000000 bytes reached
> [gdigrab] Stream !#0: not enough frames to estimate rate; consider
increasing probesize
> Input !#0, gdigrab, from 'title=RecordingTest
[C:\Users\rache\Downloads\RecordingTest.blend] - Blender 4.2':
> ͏ Duration: N/A, start: 1744083649.965406, bitrate: 2029190 kb/s
> ͏ Stream !#0:0, 1, 1/1000000: Video: bmp, bgra, 1920x1102, 2029190
kb/s, 29.97 fps, 1000k tbr, 1000k tbn
> ]]
> ͏ Probably the "title" failed to match? (try "hwnd"?)
> ͏ https://ffmpeg.org/ffmpeg-devices.html#gdigrab
> ͏ https://ffmpeg.org/ffmpeg.html#Video-Options
> ͏ .
> ͏ And "-framerate" is not properly applied. (misused as output
option)
>
> ͏ Interpreted command:
> ͏ `ffmpeg -f gdigrab -i "title=RecordingTest
[C:\Users\rache\Downloads\RecordingTest.blend] - Blender 4.2" -framerate
30 -c:v libx264 -preset ultrafast -b:v 500k -s 1280x720 -pix_fmt yuv420p
"out0.mkv"`
>
> ͏ Likely not permissions issue.
> ͏ But the recording target matching.
> ͏ (either somehow multiple "title" matched; or the matched "title"
changed meanwhile)
>
> ͏ Is recording "desktop" always working normally?
Recording "desktop" does work normally. And you're right the title does
change so i tested out "hwnd" and fixed the -framerate to be -r, while it
did not record the full screen, this time it just ended up recording a
still frame of the application. I could see the mouse cursor moving around
the still frame but nothing else was changing.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/11542#comment:10>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac
To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".
