Opened 8 years ago

Last modified 7 years ago

#4027 new defect

Gdi capture window title, then I close the window, ffmpeg send don't automatically stop. Version 2.3 will stop the capture.

Reported by: 0011411 Owned by:
Priority: normal Component: avformat
Version: 2.4.2 Keywords:
Cc: Blocked By:
Blocking: Reproduced by developer: yes
Analyzed by developer: yes


I use the command is:ffmpeg.exe -f gdigrab -framerate 24 -i title="" -f dshow -i audio=virtual-audio-capturer-sm -b 2000k -pix_fmt yuv420p -tune zerolatency -preset ultrafast -acodec libmp3lame -ab 64k -async 1 -ar 22050 -f mpegts udp://

I found the problem in the file ffmpeg-2.4.2\libavdevice\gdigrab.c,at static int gdigrab_read_packet(AVFormatContext *s1, AVPacket *pkt);

This function calls in ffmpeg-2.4.2\libavformat

the dbgview is show error:
[gdigrab @ 02aa7d40] Failed to capture image (error 8)
title=screen_broadcast test: Input/output error
frame= 133 fps= 24 q=2.0 size= 661kB time=00:00:05.46 bitrate= 991.6kbits

Attachments (1)

ww.bmp (1.3 MB ) - added by 0011411 8 years ago.

Download all attachments as: .zip

Change History (5)

by 0011411, 8 years ago

Attachment: ww.bmp added

comment:1 by Roger Pack, 7 years ago

full uncut command line and console output of failing [2.4] and succeeding [2.3] please?

in reply to:  1 comment:2 by 0011411, 7 years ago

Replying to rogerdpack:

full uncut command line and console output of failing [2.4] and succeeding [2.3] please?

Yes. What I use is full version ( failing [2.4] and succeeding [2.3] ).

Last edited 7 years ago by 0011411 (previous) (diff)

comment:3 by Roger Pack, 7 years ago

git bisect to determine the offending commit possible? Barring that you could use gdb on an ffmpeg_g.exe file and have it break on the failure line, then trace it out to see what's happening maybe?

comment:4 by Roger Pack, 7 years ago

Cc: added

no feedback from OP, recommend just closing this...

Note: See TracTickets for help on using tickets.