Recherche avancée

Sur d’autres sites (5366)

• cmdutils : replace usages of "#ifdef __MINGW32__" with "#ifdef _WIN32" because MSVC...

  17 mai 2014, par John Peebles

  cmdutils : replace usages of "#ifdef __MINGW32__" with "#ifdef _WIN32" because MSVC only defines _WIN32
  With the previous patch, this should fix ticket #3580 as well.
  Signed-off-by : John Peebles <johnpeeb@gmail.com>
  

  • [DH] cmdutils.h
  • [DH] ffplay.c

• [Turmux][ffmpeg] encounter "can't open stat file" when use "-pass"

  15 février 2020, par Jackal Zhao

  I installed ffmpeg in turmux, in my home directory, ran :

  ffmpeg -y -i /sdcard/FFMPEG/in.mp4 -c:v libx264 -b:v 2600k -pass 2 -c:a copy /sdcard/FFMPEG/out3.mp4

  the error bumps :

  ratecontrol_init: can't open stats file

  if I enter /sdcard/FFMEPG folder first, then run
  ffmpeg -y -i /sdcard/FFMPEG/in.mp4 -c:v libx264 -b:v 2600k -pass 2 -c:a copy /sdcard/FFMPEG/out3.mp4
  the task will run successfully.

  then I went back to turmux home directory, ran
  ffmpeg -y -i /sdcard/FFMPEG/in.mp4 -c:v libx264 -b:v 2600k -pass 2 -c:a copy /sdcard/FFMPEG/out3.mp4
  , error still happens.

  so I then added -strict -2 -passlogfile /tmp/mydummy and ran ran
  ffmpeg -y -i /sdcard/FFMPEG/in.mp4 -c:v libx264 -strict -2 -passlogfile /sdcard/FFMPEG/ -b:v 2600k -pass 2 -c:a copy /sdcard/FFMPEG/out3.mp4
  , and same error still happens.

  My question is, how to use ffmpeg "-pass" in termux successfully without especially entering the target folder ?

• Why Do Some of the Codecs in FFMPEG's Supported Codec List Show "encoders :" or "decoders :" in Parenthesis ?

  4 mai 2020, par spaceman

  If you open the Command Prompt, and run ffmpeg -codecs,
  
you will get a long list of Codecs that FFMPEG supports.

  



  Here's a small sample of the list :

  



   DEV.L. h261                 H.261
 DEV.L. h263                 H.263 / H.263-1996, H.263+ / H.263-1998 / H.263 version 2
 D.V.L. h263i                Intel H.263
 DEV.L. h263p                H.263+ / H.263-1998 / H.263 version 2
 DEV.LS h264                 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (encoders: libx264 libx264rgb)
 D.V.LS hevc                 H.265 / HEVC


  



  Now If you briefly go over the whole list,
  
you see that most Codecs in this list appear with their Name and Description,
  
but some of the Codecs also include parenthesis in the Description, and in the parenthesis,
  
they specify "encoders :" or "decoders :".

  



  For example :

  



  1)

  



   DEV.LS h264                 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (encoders: libx264 libx264rgb)


  



  2)

  



   DEVILS jpeg2000             JPEG 2000 (decoders: jpeg2000 libopenjpeg) (encoders: jpeg2000 libopenjpeg)


  



  3)

  



   DEV.L. msmpeg4v3            MPEG-4 part 2 Microsoft variant version 3 (decoders: msmpeg4) (encoders: msmpeg4)


  



  4)

  



   DEA.L. aac                  AAC (Advanced Audio Coding) (encoders: aac libvo_aacenc)


  



  5)

  



   DEA.L. amr_nb               AMR-NB (Adaptive Multi-Rate NarrowBand) (decoders: amrnb libopencore_amrnb) (encoders: libopencore_amrnb)
 DEA.L. amr_wb               AMR-WB (Adaptive Multi-Rate WideBand) (decoders: amrwb libopencore_amrwb) (encoders: libvo_amrwbenc)


  



  My question :

  



  Why do some Codecs have those parenthesis, specifying Encoders/Decoders,
  
while other (in fact : most) codecs don't have these parenthesis ?