April 2015 - FFmpeg-trac - lists.ffmpeg.org

#3399(undetermined:new): Scaling MP4 Video results in bad output MP4
by FFmpeg 25 Oct '24

25 Oct '24

#3399: Scaling MP4 Video results in bad output MP4 --------------------------------------+---------------------------------- Reporter: mressler | Type: defect Status: new | Priority: normal Component: undetermined | Version: 2.1.3 Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------------+---------------------------------- Summary of the bug: Attempting to scale an MP4/H264 1920x1080 source video to 1024:-1 (also Mp4/H264) results in odd playback in different players. VLC shows green box artifacts, QuickTime and MPlayer both show jerky/slow playback. How to reproduce: (Grab source from: https://www.dropbox.com/s/thy8zxbvx1ygqru/VID_20130619_161750_449.mp4) {{{ % ffmpeg -i VID_20130619_161750_449.mp4 -vf "scale=1024:-1" VID_scaled.mp4 }}} VID_scaled.mp4 ends up with green artifacts in VLC and doesn't play appropriately in QuickTime or MPlayer. Interestingly, if I clip the video first via: {{{ % ffmpeg -i VID_20130619_161750_449.mp4 -ss 18 -t 15 -c:v copy -c:a copy clip2.mp4 }}} And then run the scale command: {{{ % ffmpeg -i clip2.mp4 -vf "scale=1024:-1" VID_clip_scaled.mp4 }}} The resulting video plays fine in VLC, QuickTime, and MPlayer. -- Ticket URL: <https://trac.ffmpeg.org/ticket/3399> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 13

#4161(undetermined:new): MPEG2 PS sample: wrong aspect ratio
by FFmpeg 11 Sep '24

11 Sep '24

#4161: MPEG2 PS sample: wrong aspect ratio -------------------------------------+------------------------------------- Reporter: | Type: defect Underground78 | Priority: normal Status: new | Version: git- Component: | master undetermined | Blocked By: Keywords: | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- '''Summary of the bug:''' This [http://www.datafilehost.com/d/95fa5281 sample] is detected as 4:3 by FFmpeg although it apparently should be 16:9. WinDVD plays it with the expected aspect ratio of 16:9 and MediaInfo also reports it to be 16:9. '''How to reproduce:''' {{{ > ffmpeg -i "VR_MOVIE_GuyMartinsSpitfireBcast169 qsf lappyAspectNoChnge_extract.mpg" ffmpeg version N-68211-g4a0b1d9 Copyright (c) 2000-2014 the FFmpeg developers built on Dec 4 2014 22:02:36 with gcc 4.9.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --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-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable- libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable- libvidstab --enable-libvo-aacenc --enable-libvo-amrwbenc --enable- libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable- libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable- decklink --enable-zlib libavutil 54. 15.100 / 54. 15.100 libavcodec 56. 14.100 / 56. 14.100 libavformat 56. 15.102 / 56. 15.102 libavdevice 56. 3.100 / 56. 3.100 libavfilter 5. 2.103 / 5. 2.103 libswscale 3. 1.101 / 3. 1.101 libswresample 1. 1.100 / 1. 1.100 libpostproc 53. 3.100 / 53. 3.100 Input #0, mpeg, from 'VR_MOVIE_GuyMartinsSpitfireBcast169 qsf lappyAspectNoChnge_extract.mpg': Duration: 00:00:09.02, start: 0.200000, bitrate: 9119 kb/s Stream #0:0[0x1e0]: Video: mpeg2video (Main), yuv420p(tv), 720x576 [SAR 16:15 DAR 4:3], max. 9263 kb/s, 25 fps, 25 tbr, 90k tbn, 50 tbc Stream #0:1[0x80]: Audio: ac3, 48000 Hz, stereo, fltp, 384 kb/s At least one output file must be specified }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/4161> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 6

#3626(undetermined:new): add 'extern "C"' to headers
by FFmpeg 12 Jul '24

12 Jul '24

#3626: add 'extern "C"' to headers -------------------------------------+------------------------------------- Reporter: spraff | Type: defect Status: new | Priority: wish Component: | Version: undetermined | unspecified Keywords: headers | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Your policy at the moment is to require applications to add 'extern "C"' to their C++ source files: http://trac.ffmpeg.org/wiki/Including%20FFmpeg%20headers%20in%20a%20C%2B%2B… This is silly and annoying. It is the header file's job to present its interface consistently to applications. decklink_enc.h does this, the other headers should too. -- Ticket URL: <https://trac.ffmpeg.org/ticket/3626> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 6

#3674(avcodec:new): Just audio without video in windows decoder
by FFmpeg 11 Jul '24

11 Jul '24

#3674: Just audio without video in windows decoder -------------------------------------+------------------------------------- Reporter: mfz | Type: defect Status: new | Priority: normal Component: avcodec | Version: Keywords: h264, | unspecified height, audio, windows media | Blocked By: player, internet explorer | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: I have a screen recorded video with frame rate 15, video codec H.264 (MP4) and AAC as audio. The target via FFmpeg should contain frame rate 25, height of 720 pixel and the codecs without change. After encoding, the file is playable in VLC player, Chrome browser (HTML5 video tag) and Firefox. In Windows Media player I just get the audio played (no video to see) and in Internet Explorer 11, I get an error ("Unknown source.") How to reproduce: {{{ % ffmpeg -i input_file.mp4 -vf "scale='(trunc((out_h*a)/2)*2):(min(720, in_h))'" output_file.mp4 VERSION: N-63439-g96470ca N-63439-g96470ca }}} Strange is: If I encode the video with a height of 718 or 722 (or any other height I tried), the video is playable anywhere - without problems. Test video file for input (short, length of 1 second): http://www.datafilehost.com/d/1ca920ac -- Ticket URL: <https://trac.ffmpeg.org/ticket/3674> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 6

#4478(avformat:new): PlayStation 2 movie files not supported (.pss)
by FFmpeg 08 Jul '24

08 Jul '24

#4478: PlayStation 2 movie files not supported (.pss) -------------------------------------+------------------------------------- Reporter: Melchior | Type: Status: new | enhancement Component: avformat | Priority: normal Keywords: PlayStation | Version: 2, PS2, .pss | unspecified Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- I decided to dig out 2 of my Sony PlayStation 2 games: - Suikoden 3 - Suikoden 4 and extract the Movie (Opening/Closing) I found some str.bin files as well but all the movie files are .pss I get FFmpeg builds from and use them with http://ffmpeg.zeranoe.com/builds/ http://avanti.arrozcru.com/ OS used on: DesktopPC -- Windows XP Professional x64 LaptopPC -- Windows 7 Ultimate x64 these files I could barely extract the Video.. but the audio was not getting even seen never-mind getting extracted.. -- Ticket URL: <https://trac.ffmpeg.org/ticket/4478> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 30

#3386(undetermined:new): [H264] [Regression] illegal short term buffer state detected
by FFmpeg 19 Jun '24

19 Jun '24

#3386: [H264] [Regression] illegal short term buffer state detected -------------------------------------+------------------------------------- Reporter: | Type: defect Underground78 | Priority: normal Status: new | Version: git- Component: | master undetermined | Blocked By: Keywords: | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- '''Summary of the bug:''' A regression in H264 decoding was apparently introduced about 3 months ago. It leads to artifacts appearing during playback with "illegal short term buffer state detected" errors being reported in the log. '''How to reproduce:''' Try [http://stfcc.org/misc/bbc2.sample.ts this sample] in ffplay for example. {{{ >ffplay.exe bbc2.sample.ts ffplay version N-60646-gd601106 Copyright (c) 2003-2014 the FFmpeg developers built on Feb 15 2014 03:11:41 with gcc 4.8.2 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libcaca --enable-libfreetype --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable- librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo- aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-zlib libavutil 52. 63.101 / 52. 63.101 libavcodec 55. 52.101 / 55. 52.101 libavformat 55. 32.101 / 55. 32.101 libavdevice 55. 9.101 / 55. 9.101 libavfilter 4. 1.102 / 4. 1.102 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 [NULL @ 04011580] start time is not set in estimate_timings_from_pts [mpegts @ 0400d160] PES packet size mismatch Last message repeated 1 times Input #0, mpegts, from 'bbc2.sample.ts': Duration: 00:00:47.48, start: 0.200000, bitrate: 8424 kb/s Program 1 Stream #0:0[0x157c]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p(tv , bt709), 1440x1080 [SAR 4:3 DAR 16:9], 23.75 fps, 25 tbr, 90k tbn, 50 tbc Stream #0:1[0x157d](eng): Audio: ac3 ([6][0][0][0] / 0x0006), 48000 Hz, ster eo, fltp, 192 kb/s Stream #0:2[0x157f](eng): Subtitle: dvb_teletext ([6][0][0][0] / 0x0006) Stream #0:3[0x1580](eng): Subtitle: dvb_subtitle ([6][0][0][0] / 0x0006) No codec could be found with id 94215 [h264 @ 054c1980] illegal short term buffer state detected }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/3386> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 6

#4078(ffmpeg:new): Specify audio bitrate per-channel
by FFmpeg 15 Apr '24

15 Apr '24

#4078: Specify audio bitrate per-channel ----------------------------------+--------------------------------------- Reporter: Haravikk | Type: enhancement Status: new | Priority: normal Component: ffmpeg | Version: unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+--------------------------------------- Fairly self-explanatory, but currently we can specify audio bit-rate for the entire stream, but this requires us to calculate the total bitrate from the number of input channels ourselves. This is fine for single files, but for batch-encoding a mixture of stereo and surround-sound content it's not as ideal, or even for encoding a file that contains multiple audio-streams. To accommodate these use-cases I'd like to request an alternative syntax for specifying audio channels with a per-channel bit-rate so that I can instead just specify say 64k per channel for AAC, with ffmpeg automatically using a total of 128k for stereo or 384k for 5.1 etc. I'm not sure what the best way to do this would be. I suppose one option would be to have a new parameter -bc for "bits per channel", so I could specify something like ffmpeg -i "$INFILE" -acodec aac -bc:a 64k "$OUTFILE" An alternative would be allowing some kind of suffix to the -b option such as: ffmpeg -i "$INFILE" -acodec aac -b:a 64k/c "$OUTFILE" -- Ticket URL: <https://trac.ffmpeg.org/ticket/4078> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 4

#4209(undetermined:new): GPS coordinates location and other iOS metadata in MOV are not copied to output MP4
by FFmpeg 10 Apr '24

10 Apr '24

#4209: GPS coordinates location and other iOS metadata in MOV are not copied to output MP4 -------------------------------------+------------------------------------- Reporter: elmimmo | 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: Certain metadata in MOV files recorded with iOS devices, such as GPS location, is lost when converting to MP4. **ffmpeg** does state in its log that the output file will contain such metadata, but such is not the case as identified with **ffprobe** and **exiftool**. Some of the metadata present in the input MOV that is missing in the output MP4, according to **ffprobe**: - make ("Apple") - encoder - location (GPS latitude/longitude/altitude coordinates) - model (the iPhone/iPad/iPod model) **exiftool** identifies some more: - camera identifier ("Back" or "Front") - Software Version (iOS version) This happens irrespective of input video/audio being transcoded or just repackaged. How to reproduce: {{{ % ffmpeg -i INPUT.mov -map_metadata 0 -c copy OUTPUT.mp4 ffmpeg version 2.5.2 Copyright (c) 2000-2014 the FFmpeg developers built on Dec 26 2014 21:55:58 with Apple LLVM version 4.2 (clang-425.0.28) (based on LLVM 3.2svn) configuration: --prefix=/usr/local/Cellar/ffmpeg/2.5.2 --enable-shared --enable-pthreads --enable-gpl --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable- libx264 --enable-libmp3lame --enable-libxvid --enable-libvo-aacenc --enable-vda libavutil 54. 15.100 / 54. 15.100 libavcodec 56. 13.100 / 56. 13.100 libavformat 56. 15.102 / 56. 15.102 libavdevice 56. 3.100 / 56. 3.100 libavfilter 5. 2.103 / 5. 2.103 libavresample 2. 1. 0 / 2. 1. 0 libswscale 3. 1.101 / 3. 1.101 libswresample 1. 1.100 / 1. 1.100 libpostproc 53. 3.100 / 53. 3.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'INPUT.mov': Metadata: major_brand : qt minor_version : 0 compatible_brands: qt creation_time : 2014-12-26 20:54:22 model : iPhone 4 model-spa : iPhone 4 encoder : 7.1.1 encoder-spa : 7.1.1 date : 2014-12-26T21:54:22+0100 date-spa : 2014-12-26T21:54:22+0100 location : +41.4082+002.1852+027.119/ location-spa : +41.4082+002.1852+027.119/ make : Apple make-spa : Apple Duration: 00:00:01.07, start: 0.000000, bitrate: 11694 kb/s Stream #0:0(und): Video: h264 (Baseline) (avc1 / 0x31637661), yuv420p(tv, bt709), 1280x720, 11890 kb/s, 24 fps, 24 tbr, 600 tbn, 1200 tbc (default) Metadata: rotate : 90 creation_time : 2014-12-26 20:54:22 handler_name : Core Media Data Handler encoder : H.264 Side data: displaymatrix: rotation of -90.00 degrees Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, mono, fltp, 62 kb/s (default) Metadata: creation_time : 2014-12-26 20:54:22 handler_name : Core Media Data Handler Output #0, mp4, to 'OUTPUT.mp4': Metadata: major_brand : qt minor_version : 0 compatible_brands: qt creation_time : 2014-12-26 20:54:22 model : iPhone 4 model-spa : iPhone 4 make-spa : Apple encoder : Lavf56.15.102 date : 2014-12-26T21:54:22+0100 date-spa : 2014-12-26T21:54:22+0100 location : +41.4082+002.1852+027.119/ location-spa : +41.4082+002.1852+027.119/ make : Apple Stream #0:0(und): Video: h264 ([33][0][0][0] / 0x0021), yuv420p, 1280x720, q=2-31, 11890 kb/s, 24 fps, 19200 tbn, 600 tbc (default) Metadata: rotate : 90 creation_time : 2014-12-26 20:54:22 handler_name : Core Media Data Handler encoder : H.264 Side data: displaymatrix: rotation of -90.00 degrees Stream #0:1(und): Audio: aac ([64][0][0][0] / 0x0040), 44100 Hz, mono, 62 kb/s (default) Metadata: creation_time : 2014-12-26 20:54:22 handler_name : Core Media Data Handler Stream mapping: Stream #0:0 -> #0:0 (copy) Stream #0:1 -> #0:1 (copy) Press [q] to stop, [?] for help frame= 25 fps=0.0 q=-1.0 Lsize= 1522kB time=00:00:01.06 bitrate=11673.4kbits/s video:1512kB audio:8kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.123020% }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/4209> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 27

#3798(ffprobe:new): ffprobe indentifies 16:9 display aspect ratio as 0:1
by FFmpeg 24 Jan '24

24 Jan '24

#3798: ffprobe indentifies 16:9 display aspect ratio as 0:1 -------------------------------------+------------------------------------- Reporter: miguelapg | Type: defect Status: new | Priority: important Component: ffprobe | Version: git- Keywords: aspect | master ratio | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: ffprobe indentifies wrongly 16:9 display aspect ratio as 0:1 in this movie "pompeii-tlr2_h1080p.mov". (Uploaded to "incoming" folder in your FTP server: upload.ffmpeg.org) How to reproduce: {{{ ffprobe -v quiet -print_format json -show_format -show_streams "pompeii- tlr2_h1080p.mov" >"myResults.json" ffprobe version Latest version: git-a613257 (2014-07-23) 64-Bit ffprobe output in Json format is attached to this ticket. Called: "myResults.json". }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/3798> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 8

#4131(avfilter:new): aresample=async=1000:first_pts=0 produced out-of-sync audio with Non-monotonous DTS in output stream warnings
by FFmpeg 18 Dec '23

18 Dec '23

#4131: aresample=async=1000:first_pts=0 produced out-of-sync audio with Non- monotonous DTS in output stream warnings ------------------------------------+-------------------------------------- Reporter: mikaraento | 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: How to reproduce: {{{ $ FFREPORT=1 ffmpeg -y -i broken_audio.ts -af aresample=async=1000:first_pts=0 broken_audio.mp4 ffmpeg version N-67656-g9a69cd6 Copyright (c) 2000-2014 the FFmpeg developers built on Nov 15 2014 14:05:16 with Apple LLVM version 6.0 (clang-600.0.54) (based on LLVM 3.5svn) }}} attaching log from FFREPORT and the input file -- Ticket URL: <https://trac.ffmpeg.org/ticket/4131> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 9