June 2023 - FFmpeg-trac - lists.ffmpeg.org

#10398(ffmpeg:new): -filter_complex stats only on last file when mutiple mappings exist.
by FFmpeg 03 Jun '23

03 Jun '23

#10398: -filter_complex stats only on last file when mutiple mappings exist. -------------------------------------+------------------------------------- Reporter: Justin | Type: defect Status: new | Priority: normal Component: ffmpeg | Version: Keywords: | unspecified filter_complex | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: How to reproduce: ffmpeg -hwaccel cuda -c:v hevc -i "inputhevcfile.mp4" -filter_complex "[0:v]trim=start=30:duration=30,setpts=PTS- STARTPTS[v0];[0:a]atrim=start=30:duration=30,asetpts=PTS- STARTPTS[a0];[0:v]trim=start=90:duration=40,setpts=PTS- STARTPTS[v1];[0:a]atrim=start=90:duration=40,asetpts=PTS- STARTPTS[a1];[0:v]trim=start=140:duration=30,setpts=PTS- STARTPTS[v2];[0:a]atrim=start=140:duration=30,asetpts=PTS- STARTPTS[a2];[0:v]trim=start=200:duration=40,setpts=PTS- STARTPTS[v3];[0:a]atrim=start=200:duration=40,asetpts=PTS-STARTPTS[a3]" -map "[v0]" -map "[a0]" -c:v hevc_nvenc -threads 1 -b:v 15862K -maxrate 27025K -bufsize 28200K output1.mp4 -map "[v1]" -map "[a1]" -c:v hevc_nvenc -threads 1 -b:v 15862K -maxrate 27025K -bufsize 28200K output2.mp4 -map "[v2]" -map "[a2]" -c:v hevc_nvenc -threads 1 -b:v 15862K -maxrate 27025K -bufsize 28200K output3.mp4 -map "[v3]" -map "[a3]" -c:v hevc_nvenc -threads 1 -b:v 15862K -maxrate 27025K -bufsize 28200K output4.mp4 ONLY when processing the 4th output i get below stats - frame= 1785 fps= 19 q=44.0 q=34.0 q=45.0 q=40.0 size= 62720kB time=00:00:39.93 bitrate=12865.6kbits/s speed=0.433x first 3 files dont show any stats info (would be good to see current frame when encoding before first file if cutpoint < 0 seconds and current frame between end of a cut point and start of the next point). The Source file is from a go pro 9 filmed @ 4K. Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. -- Ticket URL: <https://trac.ffmpeg.org/ticket/10398> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 0

#10396(avfilter:new): Fieldmatch filter does not support high bit depth?
by FFmpeg 02 Jun '23

02 Jun '23

#10396: Fieldmatch filter does not support high bit depth? ----------------------------------+-------------------------------------- Reporter: nicol | Type: defect Status: new | Priority: normal Component: avfilter | Version: git-master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+-------------------------------------- Summary of the bug: When I check the fmt from a high bit depth video using the fieldmatch filter and inverse telecine using the showinfo filter, it drops to 8 bits. the detelecine filter does not drop in bit depth. The fieldmatch filter code seems to support high bit depth. https://github.com/FFmpeg/FFmpeg/blob/master/libavfilter/vf_fieldmatch.c#L9… How to reproduce: {{{ % ffmpeg -f lavfi -i testsrc2=s=1920x1080:d=1:r=24000/1001,format=yuv422p10le,telecine,fieldmatch,showinfo -vframes 1 -f null - n: 0 pts: 0 pts_time:0 duration: 1 duration_time:0.0333667 fmt:yuv422p sar:1/1 s:1920x1080 i:P iskey:1 type:I checksum:E811F934 plane_checksum:[8D4631F3 B13FDB26 00E0EC0C] mean:[127 127 126] stdev:[56.0 79.8 84.3] > fmt:yuv422p ffmpeg -f lavfi -i testsrc2=s=1920x1080:d=1:r=24000/1001,format=yuv422p10le,telecine,detelecine,showinfo -vframes 1 -f null - n: 0 pts: 0 pts_time:0 duration: 1 duration_time:0.0417083 fmt:yuv422p10le sar:1/1 s:1920x1080 i:P iskey:1 type:I checksum:61799E58 plane_checksum:[72E5ED53 5569CC33 BFE1E4B4] mean:[506 508 504] stdev:[223.8 319.2 337.1] > fmt:yuv422p10le ffmpeg version N-110972-gbaa9fccf8d-20230601 built on ... btbn Auto-Build 2023-06-01 12:47 }}} Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. -- Ticket URL: <https://trac.ffmpeg.org/ticket/10396> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#10394(undetermined:new): nlmeans_vulkan green frame
by FFmpeg 01 Jun '23

01 Jun '23

#10394: nlmeans_vulkan green frame -------------------------------------+------------------------------------- Reporter: Jacky | Type: defect Koning | Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: using nlmeans_vulkan replaces the first frame with a green frame and also does not seem to do any nlmeans stuff at all. Playing around with the variables does not change the output in any way. (Tested with other files.) How to reproduce: First I created a testsrc file {{{ ffmpeg -f lavfi -i testsrc=duration=10:size=1280x720:rate=30 -c:v av1_nvenc -preset p7 -pix_fmt p010le -cq 20 testsrc.mp4 }}} Then I took the minimum command to get nlmeans_vulkan to work. {{{ ffmpeg -init_hw_device vulkan=vk:0 -filter_hw_device vk -i testsrc.mp4 -vf "hwupload,nlmeans_vulkan,hwdownload,format=yuv420p10le" -y -c:v av1_nvenc -cq 20 nlmeans.mp4 }}} ffmpeg version 2023-05-31-git-baa9fccf8d-full_build-www.gyan.dev testsrc.mp4 https://drive.google.com/file/d/1k9s9nhFvzkjB9tqgNWLjyH3oPqIlD6Vz/view?usp=… nlmeans.mp4 https://drive.google.com/file/d/1xgDZlKt2z5Z_W2CdrDTCEDYsGRyMhsHl/view?usp=… -- Ticket URL: <https://trac.ffmpeg.org/ticket/10394> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 0