Opened 6 months ago

Closed 5 months ago

#10703 closed defect (fixed)

ffmpeg 6.1 and master error opening media

Reported by: Jay-HeyGen Owned by:
Priority: important Component: ffmpeg
Version: git-master Keywords: 6.1 master audio ffmpeg
Cc: Jay-HeyGen Blocked By:
Blocking: Reproduced by developer: yes
Analyzed by developer: yes

Description

Summary of the bug:
How to reproduce:

ffmpeg -i test.mp3 out.mp3

I use ffmpeg 5.1.2 and older version can process the media, but ffmpeg 6.1 and master version didn't work well.
Platform:

  • Ubuntu 22.04: ffmpeg 4.2.7 -> work well
  • macOS 11.7.2: ffmpeg 5.1.2 -> work well
  • Ubuntu 22.04: ffmpeg 6.1 -> can't process

configuration:

--enable-gpl --enable-version3 --enable-static --disable-debug 
--disable-ffplay --disable-indev=sndio --disable-outdev=sndio 
--cc=gcc --enable-fontconfig --enable-frei0r --enable-gnutls 
--enable-gmp --enable-libgme --enable-gray --enable-libaom 
--enable-libfribidi --enable-libass --enable-libvmaf 
--enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb 
--enable-libopencore-amrwb --enable-libopenjpeg --enable-librubberband 
--enable-libsoxr --enable-libspeex --enable-libsrt --enable-libvorbis 
--enable-libopus --enable-libtheora --enable-libvidstab --enable-libvo-amrwbenc 
--enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 
--enable-libxml2 --enable-libdav1d --enable-libxvid --enable-libzvbi --enable-libzimg

error info:

[in#0 @ 0x6fd5800] Error opening input: Invalid data found when processing input
Error opening input file test.mp3.
Error opening input files: Invalid data found when processing input

Attachments (1)

test.mp3 (1.3 MB ) - added by Jay-HeyGen 6 months ago.
this media file can be processed with ffmpeg 5.1.2 and older versions, can't be processed with master version.

Download all attachments as: .zip

Change History (3)

by Jay-HeyGen, 6 months ago

Attachment: test.mp3 added

this media file can be processed with ffmpeg 5.1.2 and older versions, can't be processed with master version.

comment:1 by Frank Plowman, 6 months ago

Analyzed by developer: set
Reproduced by developer: set

This issue is caused by the sample file being mis-identified as a VVC bitstream. I have posted a patch on the mailing list to make the VVC probing more conservative and resolve the issue. If you require a workaround in the meantime, you can disable the VVC demuxer with --disable-demuxer=vvc.

comment:2 by quinkblack, 5 months ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.