#10315 closed defect (fixed)
B frames as references are not supported on gtx 1650 mobile using hevc
Reported by: | Pranshu Tanwar | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | undetermined |
Version: | unspecified | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Reproduced by developer: | no | |
Analyzed by developer: | no |
Description
Summary of the bug:
on a recent update of ffmpeg (i use arch btw) my hevc_nvenc started giving me this error, it used to work fine before this.
How to reproduce:
must have my gpu (gtx 1650) or a similar one
▶ ffmpeg -hwaccel cuda -i VID_20230407_200259.mp4 -c:v hevc_nvenc VID_new.mp4 ffmpeg version n6.0 Copyright (c) 2000-2023 the FFmpeg developers built with gcc 12.2.1 (GCC) 20230201 configuration: --prefix=/usr --disable-debug --disable-static --disable-stripping --enable-amf --enable-avisynth --enable-cuda-llvm --enable-lto --enable-fontconfig --enable-gmp --enable-gnutls --enable-gpl --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libdav1d --enable-libdrm --enable-libfreetype --enable-libfribidi --enable-libgsm --enable-libiec61883 --enable-libjack --enable-libjxl --enable-libmfx --enable-libmodplug --enable-libmp3lame --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librav1e --enable-librsvg --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libsvtav1 --enable-libtheora --enable-libv4l2 --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxcb --enable-libxml2 --enable-libxvid --enable-libzimg --enable-nvdec --enable-nvenc --enable-opencl --enable-opengl --enable-shared --enable-version3 --enable-vulkan libavutil 58. 2.100 / 58. 2.100 libavcodec 60. 3.100 / 60. 3.100 libavformat 60. 3.100 / 60. 3.100 libavdevice 60. 1.100 / 60. 1.100 libavfilter 9. 3.100 / 9. 3.100 libswscale 7. 1.100 / 7. 1.100 libswresample 4. 10.100 / 4. 10.100 libpostproc 57. 1.100 / 57. 1.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'VID_20230407_200259.mp4': Metadata: major_brand : mp42 minor_version : 0 compatible_brands: isommp42 creation_time : 2023-04-07T17:03:37.000000Z location : +41.1137+029.0157/ location-eng : +41.1137+029.0157/ com.android.version: 10 Duration: 00:00:19.13, start: 0.000000, bitrate: 42224 kb/s Stream #0:0[0x1](eng): Video: hevc (Main) (hvc1 / 0x31637668), yuvj420p(pc, smpte170m), 3840x2160, 41960 kb/s, SAR 1:1 DAR 16:9, 29.80 fps, 30 tbr, 90k tbn (default) Metadata: creation_time : 2023-04-07T17:03:37.000000Z handler_name : VideoHandle vendor_id : [0][0][0][0] Side data: displaymatrix: rotation of -90.00 degrees Stream #0:1[0x2](eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 95 kb/s (default) Metadata: creation_time : 2023-04-07T17:03:37.000000Z handler_name : SoundHandle vendor_id : [0][0][0][0] Stream mapping: Stream #0:0 -> #0:0 (hevc (native) -> hevc (hevc_nvenc)) Stream #0:1 -> #0:1 (aac (native) -> aac (native)) Press [q] to stop, [?] for help [hevc_nvenc @ 0x5653e40a7300] B frames as references are not supported [hevc_nvenc @ 0x5653e40a7300] Provided device doesn't support required NVENC features [1] 1587625 segmentation fault (core dumped) ffmpeg -hwaccel cuda -i VID_20230407_200259.mp4 -c:v hevc_nvenc VID_new.mp4
Change History (9)
comment:1 by , 18 months ago
follow-up: 3 comment:2 by , 18 months ago
comment:3 by , 18 months ago
Replying to nyanmisaka:
Fixed in http://git.videolan.org/?p=ffmpeg.git;a=commit;h=7a8560cb22dd9f5c54df71af3fef26db9a2a28b0
Yes, I meant that commit.
comment:4 by , 18 months ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Please try master. We only support master.
comment:6 by , 17 months ago
Replying to Pranshu Tanwar:
problem still persists after driver updates
No, you need to try this, our official binaries: https://github.com/BtbN/FFmpeg-Builds/releases/tag/latest
comment:8 by , 16 months ago
Latest binaries from ffmpeg official builds work. will use them until arch updates
comment:9 by , 16 months ago
Resolution: | invalid → fixed |
---|
That is because of fix in 9a245bdf5d7860b8bc5e5c21a105a075925b719a
That means it is a bug in the driver.