Changes between Version 1 and Version 2 of Ticket #9766
- Timestamp:
- May 5, 2022, 7:00:36 AM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #9766 – Description
v1 v2 2 2 How to reproduce: 3 3 {{{ 4 % ffmpeg.exe -init_hw_device qsv:hw,child_device_type=d3d11va -hwaccel qsv -c:v h264_qsv -hwaccel_output_format qsv -i rtsp://user:password@172.16.1.105/axis-media/media.amp -f null - 4 using ffmpeg version: ffmpeg version 5.0.1-full_build from (https://www.gyan.dev/ffmpeg/builds/) built on 2022-04-07. (Windows version) 5 5 6 ffmpeg version: ffmpeg version 5.0.1-full_build from (https://www.gyan.dev/ffmpeg/builds/) built on 2022-04-07. (Windows version) 6 ffmpeg.exe -init_hw_device qsv:hw,child_device_type=d3d11va -hwaccel qsv -c:v h264_qsv -hwaccel_output_format qsv -i rtsp://user:password@172.16.1.105/axis-media/media.amp -f null - 7 }}} 7 8 8 9 Running on Windows 10 with an Intel GPU (Intel UHD Graphics 620, but I suspect this problem isn't related to the exact hardware version - it also reproduced on another machine). The RTSP stream comes from a camera. It looks like it has a pixel format of 720x576, pix_fmt: yuvj420p. If there is a way to capture this stream such that someone else can reproduce the error, please let me know. I suspect the reproduction of this problem requires a genuine RTSP server. … … 15 16 16 17 ''The RTSP stream decodes successfully without any hardware acceleration.'' That is, with a command line of "ffmpeg.exe -i rtsp://user:password@172.16.1.105/axis-media/media.amp -f null -". It also is correctly displayed in VLC. I tried many different combinations of command line parameters (for example just with -hwaccel qsv -c:v h264_qsv) and none were successful. 17 18 }}}19 18 20 19 My commentary/analysis:
