Opened 12 years ago
Closed 12 years ago
#2567 closed defect (fixed)
FFmpeg fails to autodetect a valid wavpack file
Reported by: | ahthovaikied | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | avformat |
Version: | git-master | Keywords: | wavpack |
Cc: | Blocked By: | ||
Blocking: | Reproduced by developer: | yes | |
Analyzed by developer: | yes |
Description
FFprobe fails to process a specific standard and valid WavPack file I have.
$ ffprobe -loglevel debug problem_file.wv ffprobe version 1.2.1 Copyright (c) 2007-2013 the FFmpeg developers built on May 12 2013 18:12:31 with gcc 4.6 (Ubuntu/Linaro 4.6.3-1ubuntu5) configuration: --enable-gpl --enable-version3 --enable-nonfree --enable-x11grab --disable-encoder=vorbis --disable-encoder=aac --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libfaac --enable-libfdk-aac --enable-librtmp --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxvid --enable-libopus --disable-runtime-cpudetect --disable-ffserver --disable-debug --cpu=corei7 libavutil 52. 18.100 / 52. 18.100 libavcodec 54. 92.100 / 54. 92.100 libavformat 54. 63.104 / 54. 63.104 libavdevice 54. 3.103 / 54. 3.103 libavfilter 3. 42.103 / 3. 42.103 libswscale 2. 2.100 / 2. 2.100 libswresample 0. 17.102 / 0. 17.102 libpostproc 52. 2.100 / 52. 2.100 [AVIOContext @ 0x3677600] Statistics: 1048576 bytes read, 0 seeks problem_file.wv: Invalid data found when processing input
The file is a classic 16bits/44.1KHz WavPack file encoded with WavPack 4.60.1.
It can be successfully decoded by WavPack and the checksums match:
$ wvunpack -m problem_file.wv WVUNPACK Hybrid Lossless Audio Decompressor Linux Version 4.60.1 Copyright (c) 1998 - 2009 Conifer Software. All Rights Reserved. original md5: 23c4a0ec7272a0ed13b9c4d88d2c7151 unpacked md5: 23c4a0ec7272a0ed13b9c4d88d2c7151 restored problem_file.wav in 1.78 secs (lossless, 24.43%)
I tried with ffmpeg:
- 1.2.1
- from git today (version.sh outputs N-53047-ge751481).
I'm on Ubuntu 12.04 64bits, the configure options I use for the custom build can be found above.
I have uploaded the file here (its 33M big): problem_file.wv.
Change History (8)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
To confirm the file is valid, the soxi utility (from SoX) correctly analyses the file:
$ soxi problem_file.wv Input File : 'problem_file.wv' Channels : 2 Sample Rate : 44100 Precision : 16-bit Duration : 00:04:13.08 = 11160828 samples = 18981 CDDA sectors File Size : 33.7M Bit Rate : 1.07M Sample Encoding: 16-bit WavPack
comment:3 by , 12 years ago
Version: | unspecified → git-master |
---|
comment:4 by , 12 years ago
Component: | FFprobe → avcodec |
---|---|
Keywords: | ffprobe removed |
Priority: | normal → wish |
Reproduced by developer: | set |
Status: | new → open |
Summary: | ffprobe fails to process a valid wavpack file → FFmpeg fails to process a valid wavpack file |
Type: | defect → enhancement |
$ ffmpeg -i problem_file.wv ffmpeg version N-53023-gf9db2fc Copyright (c) 2000-2013 the FFmpeg developers built on May 13 2013 16:36:16 with gcc 4.7 (SUSE Linux) configuration: --enable-gpl --disable-indev=jack --enable-libx264 libavutil 52. 31.100 / 52. 31.100 libavcodec 55. 9.100 / 55. 9.100 libavformat 55. 7.100 / 55. 7.100 libavdevice 55. 0.100 / 55. 0.100 libavfilter 3. 65.100 / 3. 65.100 libswscale 2. 3.100 / 2. 3.100 libswresample 0. 17.102 / 0. 17.102 libpostproc 52. 3.100 / 52. 3.100 problem_file.wv: Invalid data found when processing input
comment:5 by , 12 years ago
I forgot to add that ffprobe can process all my other WavPack files perfectly fine.
follow-up: 7 comment:6 by , 12 years ago
Analyzed by developer: | set |
---|---|
Component: | avcodec → avformat |
Priority: | wish → normal |
Summary: | FFmpeg fails to process a valid wavpack file → FFmpeg fails to autodetect a valid wavpack file |
Type: | enhancement → defect |
The probe function for flic and the wavpack probe function both trigger for this file, possible patch on mailing list.
comment:7 by , 12 years ago
Replying to cehoyos:
The probe function for flic and the wavpack probe function both trigger for this file, possible patch on mailing list.
Confirmed. I tried to apply the patch and it fixes my problem.
How can I know when the patch is applied on git-master?
Thanks :)
comment:8 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | open → closed |
Should be fixed, thank you for the sample!
I have also uploaded the truncated file on upload.ffmpeg.org.