[FFmpeg-trac] #3718(undetermined:new): ffmpeg does not correctly read input text file.
FFmpeg
trac at avcodec.org
Thu Jun 12 22:13:30 CEST 2014
#3718: ffmpeg does not correctly read input text file.
-------------------------------------+-------------------------------------
Reporter: Maxwell175 | 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:
How to reproduce:
{{{
> ffmpeg -f concat -i t
mp.txt -c copy output.wav
ffmpeg version N-60592-gfd982f2 Copyright (c) 2000-2014 the FFmpeg
developers
built on Feb 13 2014 22:01:02 with gcc 4.8.2 (GCC)
configuration: --enable-gpl --enable-version3 --disable-w32threads
--enable-avisynth --enable-bzlib --enable-fontconfi
g --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-
libbluray --enable-libcaca --enable-libfreetyp
e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame
--enable-libopencore-amrnb --enable-libopenco
re-amrwb --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-
libschroedinger --enable-libsoxr --enable-libsp
eex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-
libvo-aacenc --enable-libvo-amrwbenc --enable-li
bvorbis --enable-libvpx --enable-libwavpack --enable-libx264 --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.100 / 55. 9.100
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
[concat @ 003b36e0] Line 1: unknown keyword 'file'
tmp.txt: Invalid data found when processing input
}}}
This is the Windows Zeranoe Build downloaded from here:
http://ffmpeg.zeranoe.com/builds/win32/static/ffmpeg-20140612-git-
3a1c895-win32-static.7z
The file is written from a self-made Visual Basic program using the method
described here: http://msdn.microsoft.com/en-
us/library/ms128035(v=vs.110).aspx. As you can see under the Remarks
section, it uses the UTF-8 encoding.
Turns out, that method also writes 3 extra chars to the file, ef bb bf. It
seems like this throws off FFMPEG and it gives the error above.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/3718>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list