November 2021 - FFmpeg-trac - lists.ffmpeg.org

#9518(avfilter:new): scale_vulkan and gblur_vulkan filters trigger segfault on invocation.
by FFmpeg 20 Nov '21

20 Nov '21

#9518: scale_vulkan and gblur_vulkan filters trigger segfault on invocation. -------------------------------------+------------------------------------- Reporter: Dennis E. | Type: defect Mungai | Status: new | Priority: normal Component: avfilter | Version: | unspecified Keywords: vulkan | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- '''Summary of the bug:''' I'm running FFmpeg's latest git tip from master, and encountered a segfault when running any command that invokes either {{{scale_vulkan}}} or {{{gblur_vulkan}}}. I'm yet to track down the exact commit that breaks these filters, so I'll update the ticket with that info when that's done. Here is what gdb reports: {{{ gdb --args /home/brainiarc7/ffmpeg_sources/ffmpeg/ffmpeg_g -init_hw_device cuda=cuda:0 -filter_hw_device cuda -i feeds.mp4 -filter_complex "[0:v]hwupload=extra_hw_frames=16:derive_device=vulkan,scale_vulkan=w=1920:h=1080,hwupload=derive_device=cuda[s0]" -map "[s0]" -c:v:0 h264_nvenc -map "0:a" -c:a copy -f mpegts -y scale_vulkan_test.ts GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2 Copyright (C) 2020 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /home/brainiarc7/ffmpeg_sources/ffmpeg/ffmpeg_g... (gdb) run Starting program: /home/brainiarc7/ffmpeg_sources/ffmpeg/ffmpeg_g -init_hw_device cuda=cuda:0 -filter_hw_device cuda -i feeds.mp4 -filter_complex \[0:v\]hwupload=extra_hw_frames=16:derive_device=vulkan,scale_vulkan=w=1920:h=1080,hwupload=derive_device=cuda\[s0\] -map \[s0\] -c:v:0 h264_nvenc -map 0:a -c:a copy -f mpegts -y scale_vulkan_test.ts [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". ffmpeg version N-104617-g405685dec7 Copyright (c) 2000-2021 the FFmpeg developers built with gcc 9 (Ubuntu 9.3.0-17ubuntu1~20.04) configuration: --pkg-config-flags=--static --enable-static --disable- shared --prefix=/home/brainiarc7 --bindir=/home/brainiarc7/bin --enable- cuda-nvcc --enable-cuvid --enable-libnpp --extra- cflags=-I/usr/local/cuda/include/ --extra-ldflags=-L/usr/local/cuda/lib64/ --enable-nvenc --enable-libass --enable-debug --enable-gpl --cpu=native --enable-libfdk-aac --enable-libx264 --enable-libx265 --enable-openssl --enable-librtmp --enable-libzvbi --enable-version3 --enable-opencl --enable-pic --enable-librav1e --enable-libglslang --enable-vulkan --enable-libsrt --enable-avisynth --enable-libsvtav1 --enable-libvpx --enable-libplacebo --enable-librav1e --nvccflags='-gencode arch=compute_75,code=sm_75 -O2' --extra-libs='-lpthread -lm -lz -ldl' --enable-nonfree libavutil 57. 9.100 / 57. 9.100 libavcodec 59. 13.100 / 59. 13.100 libavformat 59. 9.101 / 59. 9.101 libavdevice 59. 0.101 / 59. 0.101 libavfilter 8. 17.100 / 8. 17.100 libswscale 6. 1.100 / 6. 1.100 libswresample 4. 0.100 / 4. 0.100 libpostproc 56. 0.100 / 56. 0.100 [New Thread 0x7fffe5973000 (LWP 2443713)] [New Thread 0x7fffe5172000 (LWP 2443714)] [New Thread 0x7fffe1fff000 (LWP 2443715)] Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'feeds.mp4': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2avc1mp41 encoder : Lavf59.5.100 Duration: 01:00:02.13, start: 0.000000, bitrate: 13533 kb/s Stream #0:0[0x1](und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(progressive), 1920x1080 [SAR 1:1 DAR 16:9], Closed Captions, 13144 kb/s, 29.97 fps, 29.97 tbr, 30k tbn (default) Metadata: handler_name : VideoHandler vendor_id : [0][0][0][0] Stream #0:1[0x2](eng): Audio: ac3 (ac-3 / 0x332D6361), 48000 Hz, 5.1(side), fltp, 384 kb/s (default) Metadata: handler_name : SoundHandler vendor_id : [0][0][0][0] Side data: audio service type: main Thread 1 "ffmpeg_g" received signal SIGSEGV, Segmentation fault. 0x000055555596da4c in ff_vk_free_buf (s=s@entry=0x55555884a080, buf=buf@entry=0x55555884a8f0) at ./libavutil/vulkan.c:356 356 vk->DeviceWaitIdle(s->hwctx->act_dev); }}} And for the gblur_vulkan filter which also triggers a segfault in a similar fashion: {{{ gdb --args /home/brainiarc7/ffmpeg_sources/ffmpeg/ffmpeg_g -init_hw_device cuda=cuda:0 -filter_hw_device cuda -i feeds.mp4 -filter_complex "[0:v]hwupload=extra_hw_frames=16:derive_device=vulkan,gblur_vulkan,hwupload=derive_device=cuda[s0]" -map "[s0]" -c:v:0 h264_nvenc -map "0:a" -c:a copy -f mpegts -y scale_vulkan_test.ts GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2 Copyright (C) 2020 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /home/brainiarc7/ffmpeg_sources/ffmpeg/ffmpeg_g... (gdb) run Starting program: /home/brainiarc7/ffmpeg_sources/ffmpeg/ffmpeg_g -init_hw_device cuda=cuda:0 -filter_hw_device cuda -i feeds.mp4 -filter_complex \[0:v\]hwupload=extra_hw_frames=16:derive_device=vulkan,gblur_vulkan,hwupload=derive_device=cuda\[s0\] -map \[s0\] -c:v:0 h264_nvenc -map 0:a -c:a copy -f mpegts -y scale_vulkan_test.ts [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". ffmpeg version N-104617-g405685dec7 Copyright (c) 2000-2021 the FFmpeg developers built with gcc 9 (Ubuntu 9.3.0-17ubuntu1~20.04) configuration: --pkg-config-flags=--static --enable-static --disable- shared --prefix=/home/brainiarc7 --bindir=/home/brainiarc7/bin --enable- cuda-nvcc --enable-cuvid --enable-libnpp --extra- cflags=-I/usr/local/cuda/include/ --extra-ldflags=-L/usr/local/cuda/lib64/ --enable-nvenc --enable-libass --enable-debug --enable-gpl --cpu=native --enable-libfdk-aac --enable-libx264 --enable-libx265 --enable-openssl --enable-librtmp --enable-libzvbi --enable-version3 --enable-opencl --enable-pic --enable-librav1e --enable-libglslang --enable-vulkan --enable-libsrt --enable-avisynth --enable-libsvtav1 --enable-libvpx --enable-libplacebo --enable-librav1e --nvccflags='-gencode arch=compute_75,code=sm_75 -O2' --extra-libs='-lpthread -lm -lz -ldl' --enable-nonfree libavutil 57. 9.100 / 57. 9.100 libavcodec 59. 13.100 / 59. 13.100 libavformat 59. 9.101 / 59. 9.101 libavdevice 59. 0.101 / 59. 0.101 libavfilter 8. 17.100 / 8. 17.100 libswscale 6. 1.100 / 6. 1.100 libswresample 4. 0.100 / 4. 0.100 libpostproc 56. 0.100 / 56. 0.100 [New Thread 0x7fffe5973000 (LWP 2448642)] [New Thread 0x7fffe5172000 (LWP 2448643)] [New Thread 0x7fffe1fff000 (LWP 2448644)] Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'feeds.mp4': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2avc1mp41 encoder : Lavf59.5.100 Duration: 01:00:02.13, start: 0.000000, bitrate: 13533 kb/s Stream #0:0[0x1](und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(progressive), 1920x1080 [SAR 1:1 DAR 16:9], Closed Captions, 13144 kb/s, 29.97 fps, 29.97 tbr, 30k tbn (default) Metadata: handler_name : VideoHandler vendor_id : [0][0][0][0] Stream #0:1[0x2](eng): Audio: ac3 (ac-3 / 0x332D6361), 48000 Hz, 5.1(side), fltp, 384 kb/s (default) Metadata: handler_name : SoundHandler vendor_id : [0][0][0][0] Side data: audio service type: main Thread 1 "ffmpeg_g" received signal SIGSEGV, Segmentation fault. 0x000055555596da4c in ff_vk_free_buf (s=s@entry=0x55555884a080, buf=buf@entry=0x55555884a8f0) at ./libavutil/vulkan.c:356 356 vk->DeviceWaitIdle(s->hwctx->act_dev); }}} The other Vulkan-based filters (as tested) are unaffected. Warm regards, Dennis. -- Ticket URL: <https://trac.ffmpeg.org/ticket/9518> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 3

#9509(ffmpeg:new): Video unplayable in non-FFmpeg based players if it's past a certain length
by FFmpeg 20 Nov '21

20 Nov '21

#9509: Video unplayable in non-FFmpeg based players if it's past a certain length --------------------------------+--------------------------------------- Reporter: Balrog | Type: defect Status: new | Priority: normal Component: ffmpeg | Version: unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------+--------------------------------------- Summary of the bug: Trying to turn a MP3 file into a video with a single frame, issue I'm facing is that there's a limit to how long the video can be, if it's 553 seconds long it can be played on MPC-HC with K-lite's codec pack, if it's 554 seconds long then it can't be played with MPC-HC and can only be played on MPV (which I believe uses FFmpeg). I have tried a manner of modifications to the image and audio file no no avail. Can reproduce it on multiple different files, the 553/554 seconds seems to be the only consistent factor. How to reproduce: {{{ % ffmpeg -y -i 1.png -i 1.mp3 -c:a copy -t 554 result.mp4 2021-11-10-git-44c65c6cc0-full_build-www.gyan.dev (also tested on ffmpeg-20200807-fab00b0) }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/9509> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#9519(documentation:new): Inconsistent Documentation for avformat_new_stream
by FFmpeg 20 Nov '21

20 Nov '21

#9519: Inconsistent Documentation for avformat_new_stream -------------------------------------+------------------------------------- Reporter: Philip Mann | Type: defect Status: new | Priority: minor Component: | Version: documentation | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- In https://ffmpeg.org/doxygen/4.1/group__lavf__core.html#gadcb0fd3e507d9b58fe7…, the documentation for avformat_new_stream says about the AVCodec parameter: "If non-NULL, the AVCodecContext corresponding to the new stream will be initialized to use this codec. This is needed for e.g. codec-specific defaults to be set, so codec should be provided if it is known." However, the datatype of the 2nd parameter is AVCodec, not AVCodecContext. This seems to be a mistake in the documentation. Also, in the detailed description for https://ffmpeg.org/doxygen/4.1/group__lavf__encoding.html, it says "Unless the format is of the AVFMT_NOSTREAMS type, at least one stream must be created with the avformat_new_stream() function. The caller should fill the stream codec parameters information, such as the codec type, id and other parameters (e.g. width / height, the pixel or sample format, etc.) as known. The stream timebase should be set to the timebase that the caller desires to use for this stream (note that the timebase actually used by the muxer can be different, as will be described later)." This doesn't seem to make sense because the 2nd parameter to the function is just the AVCodec, not the AVCodecContext. it's unclear from the documentation what passing the codec to avformat_new_stream() really does. -- Ticket URL: <https://trac.ffmpeg.org/ticket/9519> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

Re: [FFmpeg-trac] #2802(avformat:reopened): memory leak in avformat_find_stream_info
by FFmpeg 18 Nov '21

18 Nov '21

#2802: memory leak in avformat_find_stream_info --------------------------------------+------------------------------------ Reporter: sean tearney | Owner: (none) Type: defect | Status: reopened Priority: normal | Component: avformat Version: 4.2.4 | Resolution: Keywords: leak | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | --------------------------------------+------------------------------------ Comment (by mkver): 1. Can you also test newer versions? Namely versions which contain bae8844e35147f92e612a9e0b44e939a293e5bc9 (i.e. 4.3 or higher)? Because when I look at the code of version 4.2, there is a memleak in case stat() failed [https://github.com/FFmpeg/FFmpeg/blob/release/4.2/libavformat/img2dec.c#L472 here]. 2. If it is a different issue than the one just mentioned, you will have to provide a small sample program (and sample) to reproduce the issue. -- Ticket URL: <https://trac.ffmpeg.org/ticket/2802#comment:8> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 0

#9506(undetermined:new): TrueHD 6ch fails to be parsed
by FFmpeg 16 Nov '21

16 Nov '21

#9506: TrueHD 6ch fails to be parsed -------------------------------------+------------------------------------- Reporter: eugenesv | Type: defect Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: TrueHD | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: somewhere between ffmpeg-2021-09-22-git-447cf53774-essentials_build and ffmpeg-2021-09-30-git-3ee4502753-essentials_build a bug was introduced that prevents conversion on 5.1 channel TrueHD files (2 channel files work fine) with the following error: ---- {{{ [truehd @ 000002b45a68f700] Assignment of matrix channel 0 to invalid output channel -22 is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. [truehd @ 000002b45a68f700] If you want to help, upload a sample of this file to https://streams.videolan.org/upload/ and contact the ffmpeg-devel mailing list. (ffmpeg-devel(a)ffmpeg.org) [truehd @ 000002b45a68f700] No restart header present in substream 0. [truehd @ 000002b45a68f700] No samples to output. }}} ---- How to reproduce: {{{ ffmpeg version 2021-09-30-git-3ee4502753-essentials_build-www.gyan.dev Copyright (c) 2000-2021 the FFmpeg developers % ffmpeg.exe -i in6ch.thd }}} (again, this works with ffmpeg-2021-09-22-git-447cf53774-essentials_build) -- Ticket URL: <https://trac.ffmpeg.org/ticket/9506> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 7

#5860(undetermined:new): "PES packet size mismatch", "Could not find codec parameters for stream 0" for TS stream that mplayer can play
by FFmpeg 15 Nov '21

15 Nov '21

#5860: "PES packet size mismatch", "Could not find codec parameters for stream 0" for TS stream that mplayer can play -------------------------------------+------------------------------------- Reporter: jik | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- I am trying to convert a ts stream produced by my TV tuner into an MP4 file: ffmpeg -i sample-video.ts sample-video.mp4 It is reporting "PES packet size mismatch" and "Could not find codec parameters for stream 0 (Unknown: none): unknown codec Consider increasing the value for the 'analyzeduration' and 'probesize' options". The video plays fine with mplayer and encodes fine with mencoder. Other videos recorded from the tuner do not have this problem. This discussion -- http://ffmpeg.gusari.org/viewtopic.php?f=11&t=853 -- suggests that it is appropriate for me to report this problem to you because you may be able to debug it and improve ffmpeg to make it go away in the future. -- Ticket URL: <https://trac.ffmpeg.org/ticket/5860> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 8

#9481(undetermined:new): VA-API + QSV H264 => MPEG2 transcode PSNR dropped by 25%
by FFmpeg 15 Nov '21

15 Nov '21

#9481: VA-API + QSV H264 => MPEG2 transcode PSNR dropped by 25% -------------------------------------+------------------------------------- Reporter: eero-t | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Between following FFmpeg commits: * 2021-09-22 a487635b85: avcodec/dynamic_hdr10_plus: check size before using it * 2021-09-23 6e26015a6b: avformat/astenc: Simplify writing padding PSNR for following transcode operation: {{{ $ ffmpeg -hwaccel vaapi -vaapi_device /dev/dri/renderD128 -hwaccel_output_format vaapi -i 720x480p_30.00_4mb_h264_cabac_180s.264 -c:v mpeg2_vaapi -b:v 2000K -compression_level 4 -an -vframes 4800 -y 0039_SD03MP2_1.0.mpg }}} Has dropped by 25%, as measured by: {{{ $ ffmpeg -i 720x480p_30.00_4mb_h264_cabac_180s.264 -i 0039_SD03MP2_1.0.mpg -an -vframes 2399 -filter_complex psnr -f null - }}} (I'm using fewer frames in PSNR check than for transcode, because there were odd results if all frames are used for PSNR calculation.) Between same commits, PSNR for similar transcode done using QSV: {{{ffmpeg -hwaccel qsv -qsv_device /dev/dri/renderD128 -c:v h264_qsv -i 720x480p_30.00_4mb_h264_cabac_180s.264 -c:v mpeg2_qsv -b:v 2000K -compression_level 4 -an -vframes 4800 -y 0039_SD03MP2_1.0.mpg}}} also dropped to same value, but the drop for QSV transcode PSNR was smaller because it had dropped from the original VA-API PSNR value by 7% already earlier, between these FFmpeg commits: * 2021-03-14 1af4885014: avcodec: add a mention about get_encode_buffer in the old encode API doxy * 2021-03-15 63344337f9: libavformat/hls: Reset options after open_url_keepalive() fails (I did not pay attention to that earlier/smaller QSV PSNR drop because there was at the same time marginal (<1%) perf increase, and updates in underlying drm-tip kernel & MediaSDK components.) See also #9377. Now results of both VA-API and QSV transcode operations give same (low) PSNR as using MediaSDK tool to do same transcode has been giving: {{{sample_multi_transcode -i::h264 720x480p_30.00_4mb_h264_cabac_180s.264 -o::mpeg2 0039_SD03MP2_1.0.mpg -b 2000 -u 4 -n 4800 -async 4 -hw}}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/9481> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 6

#9305(ffplay:new): pause on ffplay not work ok with webcams.
by FFmpeg 14 Nov '21

14 Nov '21

#9305: pause on ffplay not work ok with webcams. -------------------------------------+------------------------------------- Reporter: MRbi | Type: defect Status: new | Priority: important Component: ffplay | Version: 4.3.2 Keywords: webcam | Blocked By: pause | Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: when use a webcam as input on ffplay pause works ok but un-pause leave the video freezed. How to reproduce: Just play any webcam as input on ffplay, press space bar to pause then press again the spacebar for play again, and video not play again. -- Ticket URL: <https://trac.ffmpeg.org/ticket/9305> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#9508(ffmpeg:new): Split into multiple chunks of 4 seconds from a continuos stream creates almost infinite chunks after some hours
by FFmpeg 12 Nov '21

12 Nov '21

#9508: Split into multiple chunks of 4 seconds from a continuos stream creates almost infinite chunks after some hours ----------------------------------+------------------------------------- Reporter: jvilches | Type: defect Status: new | Priority: important Component: ffmpeg | Version: 4.2.4 Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+------------------------------------- Split into multiple chunks of 4 seconds from a continuos stream creates almost infinite chunks after some hours Summary of the bug: How to reproduce: {{{ % ffmpeg -loglevel error -threads 0.5 -stimeout 5000000 -rtsp_transport tcp -i rtsp://rtsp-server-1:8900/22de326b-2f8e-42c5-904c-d30263072d60 -strftime 1 -c:v copy -c:a copy -f hls -hls_flags delete_segments -hls_time 4 -start_number 0 -hls_allow_cache 0 -hls_list_size 32 -hls_segment_filename %Y-%m-%d_%H-%M-%S.ts playlist.m3u8 }}} Currently we have a process recording continuously from a rtsp stream, we are splitting the input into 4 seconds chunks with a total of 32 chunks. After some hours the process stops rotating the chunks and creates an "infinite" file that consumes all the remaining space of the hard disk. -- Ticket URL: <https://trac.ffmpeg.org/ticket/9508> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 0

#6628(ffmpeg:new): Random access indicator bit
by FFmpeg 10 Nov '21

10 Nov '21

#6628: Random access indicator bit -------------------------------------+------------------------------------- Reporter: fliston | Type: defect Status: new | Priority: important Component: ffmpeg | Version: git- Keywords: nvenc, | master cuda, nvidia, ffmpeg, | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: I'm trying to stream using ffmpeg to a STB, with no success. From the STB software support i got this answer: {{{ 4.1.5.1 Random_access_indicator For H.264/AVC Bitstreams, the following applies: Encoding: The random_access_indicator bit shall be set whenever an H.264/AVC RAP occurs in video streams (see H.264/AVC RAP definition in Clauses 3.1 and 5.5.5). Decoding: The random_access_indicator bit may be ignored by the IRD. It can be beneficially utilized together with the elementary_stream_priority indicator to identify RAP. 3.1 H.264/AVC RAP: access unit with AU delimiter in an H.264/AVC Bitstream at which an IRD can begin decoding video successfully. This access unit shall include exactly one Sequence Parameter Set (that is active) with VUI and the Picture Parameter Set that is required for decoding the associated picture. The SPS shall also precede any SEI NAL units in this access unit. This access unit must contain an IDR picture or an I picture }}} I cant't figure out how to set that bit up! With working streams my STB shows: {{{ dec[2][base] :: set_video_track() : -1 -> 0 [H264] dec[2][base] :: set_audio_track() : -1 -> 0 [AAC] [eng] }}} But with my stream {{{ dec[1][base] :: set_video_track() : -1 -> -1 [] dec[1][base] :: set_audio_track() : -1 -> 0 [AAC] [spa] }}} How to reproduce: {{{ ffmpeg -nostdin -loglevel info -ss 10 -hwaccel_device 0 -hwaccel cuvid -c:v h264_cuvid -y -re -i udp://239.255.0.21:1111?pkt_size=1316\&buffer_size=409600\&fifo_size=1000000\&overrun_nonfatal=1 -movflags isml+frag_keyframe -f ismv -threads 0 -c:a libfdk_aac -ac 2 -b:a 64k -map 0:v -filter:v:0 scale_npp=w=1920:h=1080 -c:v:0 h264_nvenc -bf 2 -b:v:0 2000k -bsf:v h264_mp4toannexb -map 0:a:0 http://XXX/XXX/XX/Streams(video) ffmpeg version N-87132-g1dc33c1 Copyright (c) 2000-2017 the FFmpeg developers built with gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.4) 20160609 configuration: --prefix=/usr/local/ffmpeg_build --extra- cflags='-I/usr/local/ffmpeg_build/include -I/usr/local/cuda/include/' --disable-yasm --extra-ldflags='-L/usr/local/ffmpeg_build/lib -L/usr/local/cuda/lib64/' --bindir=/usr/local/bin --extra-libs=-ldl --enable-nvenc --enable-cuda --enable-libnpp --enable-cuvid --enable-gpl --enable-libx264 --enable-libfdk-aac --enable-nonfree --enable-version3 libavutil 55. 74.100 / 55. 74.100 libavcodec 57.104.100 / 57.104.100 libavformat 57. 79.100 / 57. 79.100 libavdevice 57. 8.100 / 57. 8.100 libavfilter 6.101.100 / 6.101.100 libswscale 4. 7.103 / 4. 7.103 libswresample 2. 8.100 / 2. 8.100 libpostproc 54. 6.100 / 54. 6.100 }}} I'm using last nvidia drivers, and encoding with h264_nvenc. There are no problems reproducing on the STB with the udp. Any ideas? -- Ticket URL: <https://trac.ffmpeg.org/ticket/6628> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 5