Recherche avancée

Sur d’autres sites (4118)

• What version of ffmpeg is bundled inside electron ?

  7 août 2020, par greghmerrill

  The prebuilt electron binaries for Windows include the file ffmpeg.dll. How can I determine what version of the underlying ffmpeg library is actually compiled to produce this dll ? I need this information to understand what known vulnerabilities (CVE's, etc) might be in a given version of electron via ffmpeg.

  



  As I understand it, the ffmpeg dll itself is taken from https://github.com/electron/nightlies/releases/ when I download my dependencies (I'm using electron-prebuilt-compile). But I'm not getting a clear picture of what the source for that binary is. I think it might be from https://chromium.googlesource.com/chromium/third_party/ffmpeg/ but then I'm not clear on the relationship of that repo with the original ffmpeg repo (e.g. how often are fixes merged from the ffmpeg repo to the chromium third-party repo, etc.)

  



  I tried searching the content of the dll as per cody's suggestion, but no luck :

  



  $ strings ffmpeg.dll  | grep -i ffmp
FFmpeg video codec #1
Huffyuv FFmpeg variant
Not yet implemented in FFmpeg, patches welcome
C:\projects\libchromiumcontent\src\out-x64\static_library\ffmpeg.dll.pdb
ffmpeg.dll


$ strings ffmpeg.dll  | grep -i version
H.263 / H.263-1996, H.263+ / H.263-1998 / H.263 version 2
MPEG-4 part 2 Microsoft variant version 1
MPEG-4 part 2 Microsoft variant version 2
MPEG-4 part 2 Microsoft variant version 3
H.263+ / H.263-1998 / H.263 version 2
On2 VP6 (Flash version)
On2 VP6 (Flash version, with alpha channel)
old standard qpel (autodetected per FOURCC/version)
direct-qpel-blocksize bug (autodetected per FOURCC/version)
edge padding bug (autodetected per FOURCC/version)
strictly conform to a older more strict version of the spec or reference software
minor_version
premiere_version
quicktime_version
Assume this x264 version if no x264 version found in any SEI


  


• api : add missing version bumps and APIChanges entries

  7 février 2018, par James Almer

  api : add missing version bumps and APIChanges entries
  avcodec bump missed in 7e8eba2d8755962d9dca5eade57bf8f591a73c0c
  
  avformat bump missed in ff46124b0df17a1d35249e09ae8eae9a61f16e04 and
  
  0694d8702421e7aff1340038559c438b61bb30dd
  
  avdevice bump missed in 0fd475704e871ef3a535947596a012894bae3cbd
  Signed-off-by : James Almer <jamrial@gmail.com>
  

  • [DH] doc/APIchanges
  • [DH] libavcodec/version.h
  • [DH] libavdevice/version.h
  • [DH] libavformat/version.h

• ffmpeg new version doesn't run the same line

  19 juillet 2021, par Azat Aleksanyan

  on my raspberry pi w 0, I used to run the following line when the version of ffmpeg was 3.2.14-1_deb9u1.

  


  ffmpeg -i *input video name* -vcodec h264_omx *output video name*


  


  But after occasional update to the version 3.2.15-0+deb9u2 the h264_omx gives the following error :

  


  Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width, or height

  


  need to mention just nothing changed, the same code works for the previous version and doesn't work for the newer one.

  


  So, is there any code change that I should do ?