Recherche avancée

Sur d’autres sites (5737)

• FFmpeg : why we need to create temp files during conversion

  29 mars 2019, par Awais fiaz

  I have been studying about ffmpeg, its properties and its usage. I have started using a pre-made PHP based script which creates temp files during conversion. I am trying to figure out what it actually does in this given command. Why is this command creating temp files during conversion and what is the purpose of it ?

  /usr/bin/ffmpeg -y -i /var/www/html/conversion_server/files/conversion_queue/15270581986ece98.mp4 -f mp4  -vcodec libx264 -preset superfast -r 23.97598565277  -maxrate 320000 -g 60 -crf 29 -profile:v baseline  -s 426x240 -aspect 1.77  -acodec libfdk_aac -ab 320k -ar 44100  /var/www/html/conversion_server/files/videos/2018/05/23/15270581986ece98/15270581986ece98-240.mp4 2> /var/www/html/conversion_server/files/temp/1527058199834e4.tmp

  Any help regarding this would be really appreciated.

• Adding audio to mp4 using ffmpeg at certain offset gives output file #0 does not contain any stream

  18 mai 2018, par Armand

  I am attempting to add audio to a MP4 file using ffmpeg at a specific time, eventually I also want the audio to only play until a certain point, so if you can help with that also that would be great, otherwise if you can just assist me in figuring out what is causing this error.

  The arguments I use

  -y "E:\Documents\Content Bar/Photo Booth\PhotosDrop\2018-05-15 14-01-16OUT.mp4" -itsoffset  -i "E:\Downloads\wetransfer-250b26\05 Call of Love.mp3" -map 0:0 -map 1:0 -c:v copy -shortest "E:\Documents\Content Bar\Photo Booth\PhotosDrop\2018-05-15 14-01-16OUTOUT.mp4"

  This results in the following error :

  ffmpeg version N-81646-gc19da0c Copyright (c) 2000-2016 the FFmpeg developers
  
    built with gcc 5.4.0 (GCC)
  
    configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-dxva2 --enable-libmfx --enable-nvenc --enable-avisynth --enable-bzlib --enable-libebur128 --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-libopenh264 --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-lzma --enable-decklink --enable-zlib
  
    libavutil      55. 29.100 / 55. 29.100
  
    libavcodec     57. 55.101 / 57. 55.101
  
    libavformat    57. 48.103 / 57. 48.103
  
    libavdevice    57.  0.102 / 57.  0.102
  
    libavfilter     6. 62.100 /  6. 62.100
  
    libswscale      4.  1.100 /  4.  1.100
  
    libswresample   2.  1.100 /  2.  1.100
  
    libpostproc    54.  0.100 / 54.  0.100
  
  Output #0, mp4, to 'E:\Documents\Content Bar/Photo Booth\PhotosDrop\2018-05-15 14-01-16OUT.mp4':
  
  Output file #0 does not contain any stream

• configure : error out on unsupported MSVC versions

  15 mai 2018, par Rostislav Pehlivanov

  configure : error out on unsupported MSVC versions
  The FATE tests for MSVC versions older than 2013 are untested in FATE
  
  and apparently are no longer supported.
  This commit makes the configure process error out in case an older version
  
  is used, and suggests to use a supported version of MSVC to compile.
  This also changes the documentation to reflect this.
  As discussed on IRC :
  2018-05-12 19:45:16     jamrial then again, most of those were for old msvc, and i think we're not supporting versions older than 2013 (first one c99 compliant) anymore
  
  2018-05-12 19:45:43     +JEEB   yea, I think 2013 update 2 is needed
  22:53 <@atomnuker> nevcairiel : which commit broke/unsupported support for msvc 2013 ?
  
  23:23 <@atomnuker> okay, it was JEEB
  
  23:25 <+JEEB> which was for 2012 and older
  
  23:25 <+JEEB> and IIRC we no longer test those in FATE so that was my assumption
  
  23:26 <+JEEB> 2013 is when MS got trolled enough to actually update their C part
  
  23:26 <+JEEB> aand actually advertised FFmpeg support
  
  23:26 <+JEEB> (although it was semi-failing until VS2013 update 1 or 2)
  Signed-off-by : Rostislav Pehlivanov <atomnuker@gmail.com>
  

  • [DH] configure
  • [DH] doc/platform.texi