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

#6725(undetermined:new): wrong timecode for dpx
by FFmpeg 07 May '21

07 May '21

#6725: wrong timecode for dpx -------------------------------------+------------------------------------- Reporter: shekh | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- In the case when framerate is embedded in dpx the timestamps are still calculated from default framerate "25". Example test.01.dpx r_frame_rate=15/1 time_base=1/25 One of these is wrong. How to reproduce: {{{ ffprobe.exe -i "test.01.dpx" -show_streams }}} {{{ ffprobe version N-87353-g183fd30 Copyright (c) 2007-2017 the FFmpeg developers built with gcc 7.2.0 (GCC) configuration: --enable-gpl --enable-version3 --enable-cuda --enable- cuvid --enable-d3d11va --enable-dxva2 --enable-libmfx --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-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopus --enable-librtmp --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-libxml2 --enable- libzimg --enable-lzma --enable-zlib libavutil 55. 76.100 / 55. 76.100 libavcodec 57.106.101 / 57.106.101 libavformat 57. 82.101 / 57. 82.101 libavdevice 57. 8.101 / 57. 8.101 libavfilter 6.105.100 / 6.105.100 libswscale 4. 7.103 / 4. 7.103 libswresample 2. 8.100 / 2. 8.100 libpostproc 54. 6.100 / 54. 6.100 [dpx_pipe @ 000000000045a8e0] Stream #0: not enough frames to estimate rate; consider increasing probesize Input #0, dpx_pipe, from 'test.01.dpx': Duration: N/A, bitrate: N/A Stream #0:0: Video: dpx, gbrp10le, 2048x1556, 15 tbr, 25 tbn, 15 tbc }}} {{{ [STREAM] index=0 codec_name=dpx codec_long_name=DPX (Digital Picture Exchange) image profile=unknown codec_type=video codec_time_base=0/1 codec_tag_string=[0][0][0][0] codec_tag=0x0000 width=2048 height=1556 coded_width=2048 coded_height=1556 has_b_frames=0 sample_aspect_ratio=0:1 display_aspect_ratio=0:1 pix_fmt=gbrp10le level=-99 color_range=unknown color_space=unknown color_transfer=unknown color_primaries=unknown chroma_location=unspecified field_order=unknown timecode=N/A refs=1 id=N/A r_frame_rate=15/1 avg_frame_rate=0/0 time_base=1/25 start_pts=N/A start_time=N/A duration_ts=N/A duration=N/A bit_rate=N/A max_bit_rate=N/A bits_per_raw_sample=10 nb_frames=N/A nb_read_frames=N/A nb_read_packets=N/A DISPOSITION:default=0 DISPOSITION:dub=0 DISPOSITION:original=0 DISPOSITION:comment=0 DISPOSITION:lyrics=0 DISPOSITION:karaoke=0 DISPOSITION:forced=0 DISPOSITION:hearing_impaired=0 DISPOSITION:visual_impaired=0 DISPOSITION:clean_effects=0 DISPOSITION:attached_pic=0 DISPOSITION:timed_thumbnails=0 [/STREAM] }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/6725> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 6

#9220(ffmpeg:new): IPCM Not detected and decoded accordingly by FFMpeg
by FFmpeg 07 May '21

07 May '21

#9220: IPCM Not detected and decoded accordingly by FFMpeg -------------------------------------+------------------------------------- Reporter: FranceBB | Type: defect Status: new | Priority: normal Component: ffmpeg | Version: Keywords: pcm_s24be, | unspecified ipcm, IPCM, Sony IPCM | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: IPCM audio files muxed in MP4 are not correctly detected as pcm_s24be and decoded accordingly. How to reproduce: {{{ ffmpeg.exe -i %1 -acodec pcm_s24le -ar 48000 -ac 2 -y out1.wav }}} Expected behavior: decode IPCM and encode a PCM signed 24-bit little- endian file muxed in .wav Actual behavior: Error - Decoder (codec none) not found for input stream #0:1 Full log: {{{ Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'Z:\IPCM_Sample.MP4': Metadata: major_brand : XAVC minor_version : 17440767 compatible_brands: XAVCmp42iso2 creation_time : 2021-05-04T04:54:00.000000Z Duration: 00:00:10.08, start: 0.000000, bitrate: 80002 kb/s Stream #0:0(und): Video: h264 (High 4:2:2) (avc1 / 0x31637661), yuv422p10le(pc), 1920x1080 [SAR 1:1 DAR 16:9], 46772 kb/s, 50 fps, 50 tbr, 50k tbn, 100 tbc (default) Metadata: creation_time : 2021-05-04T04:54:00.000000Z handler_name : Video Media Handler vendor_id : [0][0][0][0] encoder : AVC Coding Stream #0:1(und): Audio: none (ipcm / 0x6D637069), 48000 Hz, stereo (default) Metadata: creation_time : 2021-05-04T04:54:00.000000Z handler_name : Sound Media Handler vendor_id : [0][0][0][0] Stream #0:2(und): Data: none (rtmd / 0x646D7472), 4505 kb/s (default) Metadata: creation_time : 2021-05-04T04:54:00.000000Z handler_name : Timed Metadata Media Handler timecode : 01:24:55:10 Stream mapping: Stream #0:1 -> #0:0 (? (?) -> pcm_s24le (native)) Decoder (codec none) not found for input stream #0:1 }}} ffmpeg version N-100846-g488e65037b built on 27/01/2021 01:53 AM UTC+01:00 same behavior occurs on: ffmpeg version 2021-05-05-git-7c451b609c built on 05/05/2021 12:29 PM UTC+01:00 Actual workaround: manually setting the decoder to pcm_s24be PCM signed 24-bit big-endian makes it possible to decode the file correctly. This: {{{ ffmpeg.exe -c:a pcm_s24be -i %1 -acodec pcm_s24le -ar 48000 -ac 2 -y out1.wav }}} works just fine: {{{ Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'Z:\IPCM_Sample.MP4': Metadata: major_brand : XAVC minor_version : 17440767 compatible_brands: XAVCmp42iso2 creation_time : 2021-05-04T04:54:00.000000Z Duration: 00:00:10.08, start: 0.000000, bitrate: 80002 kb/s Stream #0:0(und): Video: h264 (High 4:2:2) (avc1 / 0x31637661), yuv422p10le(pc), 1920x1080 [SAR 1:1 DAR 16:9], 46772 kb/s, 50 fps, 50 tbr, 50k tbn, 100 tbc (default) Metadata: creation_time : 2021-05-04T04:54:00.000000Z handler_name : Video Media Handler vendor_id : [0][0][0][0] encoder : AVC Coding Stream #0:1(und): Audio: pcm_s24be (ipcm / 0x6D637069), 48000 Hz, stereo, s32 (24 bit), 2304 kb/s (default) Metadata: creation_time : 2021-05-04T04:54:00.000000Z handler_name : Sound Media Handler vendor_id : [0][0][0][0] Stream #0:2(und): Data: none (rtmd / 0x646D7472), 4505 kb/s (default) Metadata: creation_time : 2021-05-04T04:54:00.000000Z handler_name : Timed Metadata Media Handler timecode : 01:24:55:10 Stream mapping: Stream #0:1 -> #0:0 (pcm_s24be (native) -> pcm_s24le (native)) Press [q] to stop, [?] for help Output #0, wav, to 'out1.wav': Metadata: major_brand : XAVC minor_version : 17440767 compatible_brands: XAVCmp42iso2 ISFT : Lavf58.65.101 Stream #0:0(und): Audio: pcm_s24le ([1][0][0][0] / 0x0001), 48000 Hz, stereo, s32 (24 bit), 2304 kb/s (default) Metadata: creation_time : 2021-05-04T04:54:00.000000Z handler_name : Sound Media Handler vendor_id : [0][0][0][0] encoder : Lavc58.119.100 pcm_s24le size= 2835kB time=00:00:10.06 bitrate=2306.5kbits/s speed= 196x video:0kB audio:2835kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.003514% }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/9220> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 5

#9216(documentation:new): Outdated Windows build instructions
by FFmpeg 05 May '21

05 May '21

#9216: Outdated Windows build instructions -------------------------------------+------------------------------------- Reporter: pekkavaa | Type: defect Status: new | Priority: minor Component: | Version: git- documentation | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- The build instructions at https://www.ffmpeg.org/platform.html#toc- Microsoft-Visual-C_002b_002b-or-Intel-C_002b_002b-Compiler-for-Windows tells us this: >To set up a proper environment in MSYS2, you need to run msys_shell.bat from the Visual Studio or Intel Compiler command prompt. But in the latest MSYS2 version you actually need to use a special parameter to pass the PATH variable to the shell: {{{ msys2_shell.cmd -use-full-path }}} Without the flag cl.exe won't be found and running ./configure fails. -- Ticket URL: <https://trac.ffmpeg.org/ticket/9216> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 0

#9200(ffmpeg:new): drawtext issue when apply hindi language font file or other language font file
by FFmpeg 04 May '21

04 May '21

#9200: drawtext issue when apply hindi language font file or other language font file -------------------------------------+------------------------------------- Reporter: jaydip | Type: defect nathani | Status: new | Priority: critical Component: ffmpeg | Version: git- | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- We are trying to use ffmpeg drawtext to support hindi fonts. but some characters are not rendering properly. Used Hindi Language Font file :-https://fonts.google.com/specimen/Khula {{{ ffmpeg -i myvideo.mp4 -i image.png -filter_complex [0:v][1:v]overlay=5:5,drawtext=text=hindi.txt:fontfile=Khula- Regular.ttf:fontcolor=orange@1.0:fontsize=30:x=30:y=200 -c:a copy output.mp4 }}} Input string :- जिन्दगी सिर्फ हकीक़त है हकीक़त समझो, But output renders as [[Image(https://drive.google.com/file/d/1ZjZQB4Hq0Xxfrjjp1EC60e3tHhmw353X/vie…]] -- Ticket URL: <https://trac.ffmpeg.org/ticket/9200> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 17

#9212(avfilter:new): Force rgb color
by FFmpeg 03 May '21

03 May '21

#9212: Force rgb color -------------------------------------+------------------------------------- Reporter: Jefferson | Type: Villasan Josol | enhancement Status: new | Priority: critical Component: avfilter | Version: git- | master Keywords: yuv2rgb | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Hello I just want to ask one question. If the codec does not support rgb, is there a command to forcefully use RGB??? The codec I want to use is '''mpeg2video''' -- Ticket URL: <https://trac.ffmpeg.org/ticket/9212> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 2

#9144(avformat:new): ffmetadata has inconsistent escaping
by FFmpeg 03 May '21

03 May '21

#9144: ffmetadata has inconsistent escaping -------------------------------------+------------------------------------- Reporter: | Type: defect federicocarboni | Status: new | Priority: normal Component: avformat | Version: git- Keywords: | master metadata,ffmetadata | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- {{{ ;FFMETADATA1 key=value\\ key2=value }}} The backslash here is used to escape itself, not the following newline character. Yet the ffmetadata demuxer will read a key with value 'value\\\nkey2=value'. This behavior can also be observed by creating an ffmeta file with ffmpeg and probing it with ffprobe. {{{ # Double backslash for terminal escaping $ ffmpeg -metadata key=value\\ any.ffmeta ... Output #0, ffmetadata, to 'any.ffmeta': Metadata: key : value\ encoder : Lavf58.45.100 $ ffprobe any.ffmeta ... Input #0, ffmetadata, from 's.ffmeta': Metadata: key : value\ : encoder=Lavf58.45.100 # The encoder metadata property is gone. ... }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/9144> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#9214(avformat:new): ffmetadata decoding handles lines ending with backslashes incorrectly
by FFmpeg 03 May '21

03 May '21

#9214: ffmetadata decoding handles lines ending with backslashes incorrectly -------------------------------------+------------------------------------- Reporter: Michael | Type: defect Lelli | Status: new | Priority: normal Component: avformat | Version: | unspecified Keywords: ffmetadata | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: In ffmetadata files, if a line ends with an escaped backslash the next line return is also escaped when it should not be. This only happens when using Unix newlines (\n). Using Windows newlines (\r\n) does not show this issue. How to reproduce: Create this ffmpeg tag file with Unix newlines: {{{ ;FFMETADATA1 test1=qwer\\ test2=asdf }}} Write, then read the metadata from a file: {{{ ffmpeg -y -i in.mp4 -i meta.txt -map_metadata 1 -movflags use_metadata_tags -codec copy -f mp4 out.mp4 ffmpeg -i out.mp4 -f ffmetadata - }}} Expected results (and results with Windows newlines): {{{ ;FFMETADATA1 ... test1=qwer\\ test2=asdf }}} Actual results: {{{ ;FFMETADATA1 ... test1=qwer\\\ test2\=asdf }}} Version: {{{ ffmpeg version 2021-05-02-git-5541cffa17-full_build-www.gyan.dev Copyright (c) 2000-2021 the FFmpeg developers built with gcc 10.2.0 (Rev6, Built by MSYS2 project) configuration: --enable-gpl --enable-version3 --enable-static --disable- w32threads --disable-autodetect --enable-fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-lzma --enable- libsnappy --enable-zlib --enable-librist --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-libbluray --enable-libcaca --enable-sdl2 --enable-libdav1d --enable-libzvbi --enable-librav1e --enable-libsvtav1 --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-libaom --enable-libopenjpeg --enable-libvpx --enable-libass --enable-frei0r --enable-libfreetype --enable-libfribidi --enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf --enable-cuda-llvm --enable-cuvid --enable-ffnvcodec --enable-nvdec --enable-nvenc --enable-d3d11va --enable-dxva2 --enable-libmfx --enable- libglslang --enable-vulkan --enable-opencl --enable-libcdio --enable- libgme --enable-libmodplug --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libshine --enable-libtheora --enable- libtwolame --enable-libvo-amrwbenc --enable-libilbc --enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable- libvorbis --enable-ladspa --enable-libbs2b --enable-libflite --enable- libmysofa --enable-librubberband --enable-libsoxr --enable-chromaprint }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/9214> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#9211(ffmpeg:new): MPEG2 decoder timebase resets cause FFmpeg to lock up during concat or the output video stutter
by FFmpeg 03 May '21

03 May '21

#9211: MPEG2 decoder timebase resets cause FFmpeg to lock up during concat or the output video stutter -------------------------------------+------------------------------------- Reporter: nab622 | Type: defect Status: new | Priority: normal Component: ffmpeg | Version: 4.3.2 Keywords: MPEG2 | Blocked By: timebase discontinuity | Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- I believe this is the same thing that is reported here: https://ffmpeg.org/pipermail/ffmpeg-devel/2018-March/226706.html In many MPEG2 (DVD) videos, the timebase resets during playback. FFmpeg gets confused by this, and behaves unpredictably. Most notably, during a "-i concat:VTS_01_1.VOB|VTS_01_2.VOB|VTS_01_3.VOB" operation, some videos will cause FFmpeg to get stuck in an infinite loop, generating thousands of "NON-MONOTONOUS DTS" and "Buffer underflow" messages per second. If I instead chunk the video up so the timebase resets are separate inputs (Using dvd2concat), FFmpeg will work, but the output video will stutter at every join between the inputs, sometimes for several seconds, which is unacceptable. I have tried -fflags +genpts, but it did not fix the problem. Is there any way arbitrary timebase resets can be properly handled? It seems to be part of the MPEG2 standard, and the link at the top of this issue has code attached that claims to handle it. Even if it can just be added as an optional switch, that would mean the world to anyone processing DVD videos. -- Ticket URL: <https://trac.ffmpeg.org/ticket/9211> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 3

#9208(undetermined:new): Should I always set dropout_transition very high number like 10000 when using amix filter
by FFmpeg 02 May '21

02 May '21

#9208: Should I always set dropout_transition very high number like 10000 when using amix filter -------------------------------------+------------------------------------- Reporter: kvsico | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: I want to mix many audio files with different duration, but the volume of mix.mp3 increased like issue[0], then I solved this problem by adding `dropout_transition=10000`[1], the whole command is `ffmpeg -y -i a.mp3 -i b.mp3 -filter_complex "[0]volume=1[a0];[a0]adelay=0|0[a00];[1]volume=1[a1];[a1]adelay=5000|5000[a11];[a00][a11]amix=inputs=2:dropout_transition=10000,volume=2[aaa]" -map "[aaa]" mix.mp3 ` . I don't know much about amxi filter and googled less search result about it, does `dropout_transition=10000` have potential problems? Should use amerge filter instead, or use newly added `sum` option[2] [0]:https://stackoverflow.com/questions/35509147/ffmpeg-amix-filter- volume-issue-with-inputs-of-different-duration [1]:https://www.reddit.com/r/ffmpeg/comments/d63fki/preventing_amixs_volume_… [2]:http://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=57651493923ea4bc764… [9]:https://stackoverflow.com/questions/62367391/ffmpeg-amix-filter- always-does-volume-normalization-how-to-prevent-it-and-wha -- Ticket URL: <https://trac.ffmpeg.org/ticket/9208> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 2

#9198(undetermined:new): Westwood AUD decoding incorrect.
by FFmpeg 01 May '21

01 May '21

#9198: Westwood AUD decoding incorrect. -------------------------------------+------------------------------------- Reporter: Aidan | Type: defect Richmond | Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: Decoding IMA ADPCM encoded .aud files from C&C and Red Alert is incorrect. Sound is distorted compared to game output and has burst of noise at the end. How to reproduce: {{{ % ffmpeg -i westwood_sample.aud westwood_sample.wav ffmpeg -v 9 -loglevel 99 -i /d/westwood_sample.aud /d/westwood_sample.wav ffmpeg version N-102008-gf7c3484b26 Copyright (c) 2000-2021 the FFmpeg developers built with gcc 10.2.0 (Rev10, Built by MSYS2 project) configuration: --enable-x86asm --enable-asm --disable-shared --enable- static --enable-sdl2 --prefix=../installed libavutil 56. 73.100 / 56. 73.100 libavcodec 58.136.101 / 58.136.101 libavformat 58. 78.100 / 58. 78.100 libavdevice 58. 14.100 / 58. 14.100 libavfilter 7.111.100 / 7.111.100 libswscale 5. 10.100 / 5. 10.100 libswresample 3. 10.100 / 3. 10.100 Splitting the commandline. Reading option '-v' ... matched as option 'v' (set logging level) with argument '9'. Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument '99'. Reading option '-i' ... matched as input url with argument 'D:/westwood_sample.aud'. Reading option 'D:/westwood_sample.wav' ... matched as output url. Finished splitting the commandline. Parsing a group of options: global . Applying option v (set logging level) with argument 9. Successfully parsed a group of options. Parsing a group of options: input url D:/westwood_sample.aud. Successfully parsed a group of options. Opening an input file: D:/westwood_sample.aud. [NULL @ 00000217ecdf8280] Opening 'D:/westwood_sample.aud' for reading [file @ 00000217ecdf9940] Setting default whitelist 'file,crypto,data' Probing wsaud score:50 size:2048 [wsaud @ 00000217ecdf8280] Format wsaud probed with size=2048 and score=50 [wsaud @ 00000217ecdf8280] Before avformat_find_stream_info() pos: 12 bytes read:9668 seeks:0 nb_streams:1 [wsaud @ 00000217ecdf8280] Estimating duration from bitrate, this may be inaccurate [wsaud @ 00000217ecdf8280] stream 0: start_time: NOPTS duration: 0.875828 [wsaud @ 00000217ecdf8280] format: start_time: NOPTS duration: 0.875828 (estimate from bit rate) bitrate=88 kb/s [wsaud @ 00000217ecdf8280] After avformat_find_stream_info() pos: 9668 bytes read:9668 seeks:0 frames:19 Input #0, wsaud, from 'D:/westwood_sample.aud': Duration: 00:00:00.88, bitrate: 88 kb/s Stream #0:0, 19, 1/22050: Audio: adpcm_ima_ws, 22050 Hz, mono, s16, 88 kb/s Successfully opened the file. Parsing a group of options: output url D:/westwood_sample.wav. Successfully parsed a group of options. Opening an output file: D:/westwood_sample.wav. File 'D:/westwood_sample.wav' already exists. Overwrite? [y/N] y [file @ 00000217ecdfafc0] Setting default whitelist 'file,crypto,data' Successfully opened the file. Stream mapping: Stream #0:0 -> #0:0 (adpcm_ima_ws (native) -> pcm_s16le (native)) Press [q] to stop, [?] for help cur_dts is invalid st:0 (0) [init:0 i_done:0 finish:0] (this is harmless if it occurs once at the start per stream) detected 4 logical cores [graph_0_in_0_0 @ 00000217ecdfd740] Setting 'time_base' to value '1/22050' [graph_0_in_0_0 @ 00000217ecdfd740] Setting 'sample_rate' to value '22050' [graph_0_in_0_0 @ 00000217ecdfd740] Setting 'sample_fmt' to value 's16' [graph_0_in_0_0 @ 00000217ecdfd740] Setting 'channel_layout' to value '0x4' [graph_0_in_0_0 @ 00000217ecdfd740] tb:1/22050 samplefmt:s16 samplerate:22050 chlayout:0x4 [format_out_0_0 @ 00000217ecdfed00] Setting 'sample_fmts' to value 's16' [AVFilterGraph @ 00000217ece02200] query_formats: 4 queried, 9 merged, 0 already done, 0 delayed Output #0, wav, to 'D:/westwood_sample.wav': Metadata: ISFT : Lavf58.78.100 Stream #0:0, 0, 1/22050: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 22050 Hz, mono, s16, 352 kb/s Metadata: encoder : Lavc58.136.101 pcm_s16le D:/westwood_sample.aud: I/O errorbitrate= 366.2kbits/s speed=2.32e+04x [out_0_0 @ 00000217ecdfeb40] EOF on sink link out_0_0:default. No more output streams to write to, finishing. size= 37kB time=00:00:00.86 bitrate= 353.5kbits/s speed= 253x video:0kB audio:37kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.205177% Input file #0 (D:/westwood_sample.aud): Input stream #0:0 (audio): 19 packets read (9504 bytes); 19 frames decoded (19008 samples); Total: 19 packets (9504 bytes) demuxed Output file #0 (D:/westwood_sample.wav): Output stream #0:0 (audio): 19 frames encoded (19008 samples); 19 packets muxed (38016 bytes); Total: 19 packets (38016 bytes) muxed 19 frames successfully decoded, 0 decoding errors [AVIOContext @ 00000217ece53000] Statistics: 0 seeks, 1 writeouts [AVIOContext @ 00000217ecdf9c40] Statistics: 9668 bytes read, 0 seeks }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/9198> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 3