Recherche avancée

Sur d’autres sites (7082)

• FFMPEG - Not finding codec parameters

  9 septembre 2024, par Tanner Smith

  I'm trying to convert a sequence of images into a mpeg movie via FFMPEG, although I keep getting an error saying that it could not find the code parameters (Video : mjpeg). A Google search did not bring much up that was useful.

  



  
ffmpeg -f image2 -i /tmp/img%03d.jpg video.mpgFFmpeg version SVN-r0.5.1-4:0.5.1-1ubuntu1, Copyright (c) 2000-2009 Fabrice Bellard, et al.
  configuration : —extra-version=4:0.5.1-1ubuntu1 —prefix=/usr —enable-avfilter —enable-avfilter-lavf —enable-vdpau —enable-bzlib —enable-libgsm —enable-libschroedinger —enable-libspeex —enable-libtheora —enable-libvorbis —enable-pthreads —enable-zlib —disable-stripping —disable-vhook —enable-runtime-cpudetect —enable-gpl —enable-postproc —enable-swscale —enable-x11grab —enable-libdc1394 —enable-shared —disable-static
  libavutil     49.15. 0 / 49.15. 0
  libavcodec    52.20. 1 / 52.20. 1
  libavformat   52.31. 0 / 52.31. 0
  libavdevice   52. 1. 0 / 52. 1. 0
  libavfilter    0. 4. 0 /  0. 4. 0
  libswscale     0. 7. 1 /  0. 7. 1
  libpostproc   51. 2. 0 / 51. 2. 0
  built on Mar  4 2010 12:35:30, gcc : 4.4.3
[mjpeg @ 0x9069870]dqt : 16bit precision
[mjpeg @ 0x9069870]mjpeg : unsupported coding type (c9)
[mjpeg @ 0x9069870]mjpeg : unsupported coding type (cf)
[mjpeg @ 0x9069870]only 8 bits/component accepted
[mjpeg @ 0x9069870]dqt : 16bit precision
[mjpeg @ 0x9069870]huffman table decode error
[mjpeg @ 0x9069870]mjpeg : unsupported coding type (ca)
[mjpeg @ 0x9069870]mjpeg : unsupported coding type (ce)
[mjpeg @ 0x9069870]mjpeg : unsupported coding type (cb)
[mjpeg @ 0x9069870]decode_sos : invalid len (60581)
[mjpeg @ 0x9069870]only 8 bits/component accepted
[mjpeg @ 0x9069870]decode_sos : invalid len (56833)
[mjpeg @ 0x9069870]invalid id 207
[mjpeg @ 0x9069870]mjpeg : unsupported coding type (cd)
[mjpeg @ 0x9069870]huffman table decode error
[image2 @ 0x90682c0]Could not find codec parameters (Video : mjpeg)
/tmp/img%03d.jpg : could not find codec parameters


  



  The images reside in the /tmp directory with names such as img001.jpg and img002.jpg.

  



  Any ideas ?

  



  Thanks
-Tanner

  


• Statically linking FFmpeg libraries into native C++ node addon

  11 juin 2019, par Suhail Doshi

  I trying to run a node addon that links to libraries without having to include their dynamic .dll library :

  When I try to include their static archive : .dll.a extension on Windows, the node addon returns an error :

  $ node index.js --client 
  
  internal/modules/cjs/loader.js:840 
  
    return process.dlopen(module, path.toNamespacedPath(filename));
  
                   ^
  
  
  
  Error: The specified procedure could not be found.

  This generally means that it was expecting to load some other function from a library but failed to find it. If there’s a way to debug this error message more specifically, I’d also love to know how !

  I’ve tried re-ordering the libraries, using different extensions, etc.

  I originally used just the .lib extension instead of the .dll.a extensions and the program works fine if I include the .dll’s.

  The code works fine if I use .lib files and place their corresponding .dlls in the same directory as the application I am executing.

  I’ve used these resources :

  • .lib’s are stubs for compile time & don’t solve the problem : Program statically linked to a library but still needs dll to run
  • Literature about .dll.a files : MinGW creating dll.a files ? What type of library files are those ?
  • Statically link ffmpeg : https://fritzone.wordpress.com/2010/05/11/link-with-static-ffmpeg/ but it ffmpeg-dev doesn’t have .a files, it has .dll.a files and I am already trying that route.

  I am using N-API and here’s what I am doing in binding.gyp :

  'libraries': [
  
              "ws2_32.lib",
  
  
  
              "C:\\Users\\$(username)\\Desktop\\workspace\\ffmpeg-win64-dev\\lib\\libavcodec.dll.a",
  
              "C:\\Users\\$(username)\\Desktop\\workspace\\ffmpeg-win64-dev\\lib\\libavutil.dll.a",
  
              "C:\\Users\\$(username)\\Desktop\\workspace\\ffmpeg-win64-dev\\lib\\libswresample.dll.a",

  I am expecting my application (node index.js --client) to run correctly without the need the .dlls I’ve had to include in the past.

  EDIT

  It’s possible this problem is as simple as : How do you statically link these FFmpeg libraries on Windows vs having anything to do with node specifically.

• Playing MP4 file in Powerpoint

  14 mai 2019, par BrewGold

  I have a huge MP4 file (4GB) an hour long video. I want to extract port of the file. So I used the following command to extract 70 seconds(00:01:10) of video starting from 11 minutes

  ffmpeg -i INPUT.mp4 -ss 00:11:00 -t 00:01:10 -c:v copy -c:a copy OUTPUT.mp4

  Now I got a small file extracted from Input.MP4
  The output.mp4 file size is still big(90 MB). So I used the following command

  ffmpeg -i OUTPUT.mp4 -c:v libx264 -crf 30 SmallSizeVideo.avi

  I got SmallSizeVideo.avi file which is approximately 6MB.

  I am using Powerpoint 2010. I want to insert the video in Powerpoint and play.

  Unfortunately when I embed SmallSizeVideo.avi Powerpoint is unable to play

  1) Is my approach correct ?
  2) What is the best way to situation like me to play small portion of clips in powerpoint

  Thank you