#5612 closed defect (needs_more_info)
Capture card with H264 output pin crash
Reported by: | Ruben Reis | Owned by: | |
---|---|---|---|
Priority: | important | Component: | undetermined |
Version: | git-master | Keywords: | h264 dshow crash |
Cc: | rogerdpack@gmail.com | Blocked By: | |
Blocking: | Reproduced by developer: | no | |
Analyzed by developer: | no |
Description
Hi! I'm trying to record and stream video from an AVerMedia LGP Lite capture card that has an HDMI input.
Unfortunately ffmpeg just crashes when I run the command without additional information.
ffmpeg started on 2016-06-03 at 22:27:56 Report written to "ffmpeg-20160603-222756.log" Command line: ffmpeg -loglevel verbose -report -f dshow -vcodec h264 -s 1920x1080 -i "video=AVerMedia C835 Capture" "C:\\Users\\Ruben\\Desktop\\140.mp4" ffmpeg version N-80129-ga1953d4 Copyright (c) 2000-2016 the FFmpeg developers built with gcc 5.3.0 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-nvenc --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmfx --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-lzma --enable-decklink --enable-zlib libavutil 55. 24.100 / 55. 24.100 libavcodec 57. 43.100 / 57. 43.100 libavformat 57. 37.101 / 57. 37.101 libavdevice 57. 0.101 / 57. 0.101 libavfilter 6. 46.100 / 6. 46.100 libswscale 4. 1.100 / 4. 1.100 libswresample 2. 0.101 / 2. 0.101 libpostproc 54. 0.100 / 54. 0.100 Splitting the commandline. Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument 'verbose'. Reading option '-report' ... matched as option 'report' (generate a report) with argument '1'. Reading option '-f' ... matched as option 'f' (force format) with argument 'dshow'. Reading option '-vcodec' ... matched as option 'vcodec' (force video codec ('copy' to copy stream)) with argument 'h264'. Reading option '-s' ... matched as option 's' (set frame size (WxH or abbreviation)) with argument '1920x1080'. Reading option '-i' ... matched as input file with argument 'video=AVerMedia C835 Capture'. Reading option 'C:\Users\Ruben\Desktop\140.mp4' ... matched as output file. Finished splitting the commandline. Parsing a group of options: global . Applying option loglevel (set logging level) with argument verbose. Applying option report (generate a report) with argument 1. Successfully parsed a group of options. Parsing a group of options: input file video=AVerMedia C835 Capture. Applying option f (force format) with argument dshow. Applying option vcodec (force video codec ('copy' to copy stream)) with argument h264. Applying option s (set frame size (WxH or abbreviation)) with argument 1920x1080. Successfully parsed a group of options. Opening an input file: video=AVerMedia C835 Capture.
I'm using the FFmpeg git-a1953d4 32-bit Static
Same problem on ffplay
The windows Event Log:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2016-06-03T21:20:56.024380400Z" /> <EventRecordID>20661</EventRecordID> <Channel>Application</Channel> <Computer>Desktop</Computer> <Security /> </System> - <EventData> <Data>ffmpeg.exe</Data> <Data>0.0.0.0</Data> <Data>029e9058</Data> <Data>ffmpeg.exe</Data> <Data>0.0.0.0</Data> <Data>029e9058</Data> <Data>c0000005</Data> <Data>00028fac</Data> <Data>2688</Data> <Data>01d1bdddd0d1b1fb</Data> <Data>C:\Users\Ruben\Desktop\ffmpeg.exe</Data> <Data>C:\Users\Ruben\Desktop\ffmpeg.exe</Data> <Data>efc1add1-ea3c-40f8-83b7-ec92b95c7c12</Data> <Data /> <Data /> </EventData> </Event>
Notes:
-I checked and no other apps are using the device
-The device works well with it's own software and other capture programs
-I'm using 16Gb RAM, Windows 10 and a Intel i7 5820K
Change History (9)
follow-up: 3 comment:1 by , 9 years ago
Analyzed by developer: | unset |
---|---|
Component: | ffmpeg → undetermined |
Keywords: | crash added; avermedia removed |
comment:2 by , 9 years ago
Keywords: | dshow added |
---|
comment:3 by , 9 years ago
Replying to cehoyos:
Without a backtrace, disassembly and register dump, there won't be much we can do...
How can I get that info? I didn't find any tip about that...
comment:5 by , 9 years ago
Resolution: | → needs_more_info |
---|---|
Status: | new → closed |
Assuming no FFmpeg developer owns an AVerMedia LGP Lite capture card, there is absolutely nothing we can do without a backtrace, disassembly and register dump.
comment:6 by , 9 years ago
Cc: | added |
---|
does it crash, is that it?
also an output from -loglevel verbose please
follow-up: 8 comment:7 by , 9 years ago
I can provide an ffmpeg with debug symbols (ffmpeg_g.exe) if you'd like to run that, as well, leave a comment here..
comment:8 by , 9 years ago
Replying to rogerdpack:
I can provide an ffmpeg with debug symbols (ffmpeg_g.exe) if you'd like to run that, as well, leave a comment here..
Sure ;)
comment:9 by , 9 years ago
OK see https://sourceforge.net/projects/ffmpegwindowsbi/files/ffmpeg_g.exe/download
You'll want to run it in a windows version of gdb (32 bit) then after it crashes, run "thread apply all backtrace" or just "backtrace"
These "might" work:
https://sourceforge.net/projects/mingw-w64/files/External%20binary%20packages%20(Win64%20hosted)/gdb/
but typically if you install any mingw gcc.exe it will come with a gdb.exe as well, GL!
Without a backtrace, disassembly and register dump, there won't be much we can do...