
Recherche avancée
Autres articles (26)
-
Les formats acceptés
28 janvier 2010, parLes commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
ffmpeg -codecs ffmpeg -formats
Les format videos acceptés en entrée
Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
Les formats vidéos de sortie possibles
Dans un premier temps on (...) -
Supporting all media types
13 avril 2011, parUnlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)
-
Submit bugs and patches
13 avril 2011Unfortunately a software is never perfect.
If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
You may also (...)
Sur d’autres sites (4915)
-
lavfi/spp : add "quality" option in runtime change path
10 janvier 2020, par Jun Zhaolavfi/spp : add "quality" option in runtime change path
it's stranage to use option "level" in runtime change path but used
"quality" in option, add "quality" in runtime change path, it's more
intuitive and keep the "level" for compatibility.Reviewe-by : Michael Niedermayer <michael@niedermayer.cc>
Signed-off-by : Jun Zhao <barryjzhao@tencent.com> -
Concatenating on Windows throws "Invalid data found when processing input" while it works on Mac and Linux
15 février 2020, par miguelmorinI need to run a command with a nightly build of FFMPEG to report a bug on the
concat
protocol. I found it difficult to compile from source with libx264 support on Linux, and I want to spare my Mac computer, so I use the nightly build on Windows from Zeranoe.I call this command to concatenate the files :
ffmpeg -safe 0 concat -i files_to_combine -vcodec libx264 show.mp4
where
files_to_combine
is :file ./short_DSC_0013.MOV
file ./short_DSC_0014.MOV
file ./short_DSC_0015.MOV
file ./short_DSC_0016.MOV
file ./short_DSC_0017.MOV
file ./short_DSC_0018.MOV
file ./short_DSC_0019.MOVI call this command from the directory containing the video files and
files_to_combine
.On Windows with a nightly build, I get the error :
files_to_combine : Invalid data found when processing input
I changed
file ./DSC_0013.MOV
to these options, all with the same error :file 'short_DSC_0013.MOV'
file '.\short_DSC_0013.MOV'
file 'F:\short_DSC_0013.MOV'How can I debug this error, or what is the syntax for concatenating on Windows with a nightly build ?
Update with log-level 48
I ran the same command with
-v 48
and got :F :\brain squids>C :\Users\migue\Desktop\ffmpeg-20200211-f15007a-win64-static\bin\ffmpeg.exe -v 48 -i files_to_combine -vcodec libx264 show.mp4 ffmpeg version git-2020-02-11-f15007a Copyright (c) 2000-2020 the FFmpeg developers built with gcc 9.2.1 (GCC) 20200122 configuration : —enable-gpl —enable-version3 —enable-sdl2 —enable-fontconfig —enable-gnutls —enable-iconv —enable-libass —enable-libdav1d —enable-libbluray —enable-libfreetype —enable-libmp3lame —enable-libopencore-amrnb —enable-libopencore-amrwb —enable-libopenjpeg —enable-libopus —enable-libshine —enable-libsnappy —enable-libsoxr —enable-libtheora —enable-libtwolame —enable-libvpx —enable-libwavpack —enable-libwebp —enable-libx264 —enable-libx265 —enable-libxml2 —enable-libzimg —enable-lzma —enable-zlib —enable-gmp —enable-libvidstab —enable-libvorbis —enable-libvo-amrwbenc —enable-libmysofa —enable-libspeex —enable-libxvid —enable-libaom —enable-libmfx —enable-ffnvcodec —enable-cuvid —enable-d3d11va —enable-nvenc —enable-nvdec —enable-dxva2 —enable-avisynth —enable-libopenmpt —enable-amf libavutil 56. 39.100 / 56. 39.100 libavcodec 58. 68.102 / 58. 68.102 libavformat 58. 38.100 / 58. 38.100 libavdevice 58. 9.103 / 58. 9.103 libavfilter 7. 75.100 / 7. 75.100 libswscale 5. 6.100 / 5. 6.100 libswresample 3. 6.100 / 3. 6.100 libpostproc 55. 6.100 / 55. 6.100 Splitting the commandline. Reading option ’-v’ ... matched as option ’v’ (set logging level) with argument ’48’. Reading option ’-i’ ... matched as input url with argument ’files_to_combine’. Reading option ’-vcodec’ ... matched as option ’vcodec’ (force video codec (’copy’ to copy stream)) with argument ’libx264’. Reading option ’show.mp4’ ... matched as output url. Finished splitting the commandline. Parsing a group of options : global . Applying option v (set logging level) with argument 48. Successfully parsed a group of options. Parsing a group of options : input url files_to_combine. Successfully parsed a group of options. Opening an input file : files_to_combine. [NULL @ 0000021c781784c0] Opening ’files_to_combine’ for reading [file @ 0000021c78179580] Setting default whitelist ’file,crypto,data’ [AVIOContext @ 0000021c781817c0] Statistics : 182 bytes read, 0 seeks files_to_combine : Invalid data found when processing input
The contents of
files_to_combine
is :file ’short_DSC_0013.MOV’ file ’short_DSC_0014.MOV’ file ’short_DSC_0015.MOV’ file ’short_DSC_0016.MOV’ file ’short_DSC_0017.MOV’ file ’short_DSC_0018.MOV’ file ’short_DSC_0019.MOV’
Update because of wrong command
I had mistyped the command. The right command has a
-f
in front ofconcat
, which I found because the accepted answer was able to make the command work in a similar environment :ffmpeg -safe 0 -f concat -i files_to_combine -vcodec libx264 show.mp4
-
libavcodec/libx264 : fix reference frame computation based on level
16 avril 2020, par Josh Brewsterlibavcodec/libx264 : fix reference frame computation based on level
The current implementation allows passing levels to libavcodec as
integers (such as "31" instead of "3.1").However, in this case, the maximum reference frame value per level was
ignored because libavcodec converted the string to 310 instead of 31.Since libx264 has correctly parsed the level to int
(x4->params.i_level_idc), we should rely on this value instead of
attempting to parse the level string on our own.Signed-off-by : Josh Brewster <josh.brewster@protonmail.com>
Signed-off-by : Josh de Kock <josh@itanimul.li>