Recherche avancée

Sur d’autres sites (4838)

• AWS Lambda and Fluent FFMPEG error "cannot read property "isStream" of undefined"

  29 mai 2021, par Travis Lee

  so here's the goal : convert a .webm file hosted in an S3 into a gif and upload that to a new bucket. This all works fine when run locally, but when trying to translate it into a lambda, fluent-ffmpeg throws errors when it runs the command.

  


  Here's the code snippet :

  


  ffmpeg(new URL(vid))
  .outputOptions("-vf", "scale=320:-1:flags=lanczos,fps=14")
  .on('progress', () => {
      console.log('progress');
  })
  .on('end', () => {
     //Do stuff with the result when it is done
  })
  .output(newKey)
  .run(newKey);


  


  in this snippet, "vid" is a presigned GET url for an S3 bucket containing the .webm video file, and "newKey" is the name of the new bucket (and a temporary writeStream/File that is created in the lambda to store the new .gif file until we upload it to S3 - not super relevant to this issue).

  


  What should happen (and does locally) is that a new output is created containing the converted .gif file

  


  What happens when it is deployed in a lambda is that it reaches the .outputOptions call and throws a type error saying that it cannot read property isStream of undefined.

  


  At first glance, this seems like I simply don't have FFMPEG installed in the lambda, but I do. I have tried with the prebuilt layer using NodeJS 10 found here : https://serverlessrepo.aws.amazon.com/applications/us-east-1/145266761615/ffmpeg-lambda-layer ,
with a NodeJS 12 layer that was built by some engineers here previously, and tried building a NodeJS 14 FFMPEG layer myself and using that. I tried for all three using no configuration and letting it call the PATH ffmpeg, using the FFMPEG_PATH and FFPROBE_PATH environment variables set to either what was specified in the previous layers, or what I made it in the newly built one, and even manually setting the path to the executables using the setFfmpegPath and setFfprobePath functions found on the fluent-ffmpeg object.

  


  Lastly, I even tried bundling the executables in with the actual lambda code itself and uploading it through an S3, trying all three above methods of getting it to point to the correct paths once again to no avail.

  


  I'm seriously in need of help if anyone else has encountered something similar or just might know what is going on. I'm at wit's end here trying to figure this out.

  


• FFMPEG drops every odd frame

  28 mars 2016, par Oleksiy Druzhynin

  At running of

  ffmpeg -i /usr/local/Videos/Ads/Samples/DX/DXd_src.ts -vf drawtext=fontfile=/usr/share/fonts/truetype/ubuntu-font-family/UbuntuMono-R.ttf:text=’%pict_type %pts:hms %pts:raw %eif:n:u’ : fontcolor=white@0.8:fontsize=40:x=7:y=200:box=1:boxcolor=black@0.8 -copyts -muxdelay 0 -muxpreload 0 -copytb 1 -vsync 0 -xerror /usr/local/Videos/Ads/Samples/DX/DXd.ts

  FFMPEG removes every odd frame in for some set of video. I couldn’t understand why ?

  See more on FFMpeg forum

• Batch converting multiple video formats in nested directories

  1er octobre 2020, par Dave Coffin

  I'm running Arch/Gnome and am trying to convert a few hundred gigs of family videos from various formats (mov, wmv, mkv, avi mainly, but a few curveballs too) into trusty mp4s.

  


  My scripting knowledge is strictly amateur, so far I have ;

  


  for i in *.avi; do ffmpeg -i "$i" "${i%.*}.mp4"; done

  


  That works fine for one directory. There are hundreds. I'd like to replace that one-liner with something more encompassing that I can just run and go to bed.

  


  Wish list ;

  


  


  • run recursively

    


  


  • convert from mov, wmv, mkv and avi without having to run separate scripts

    


  


  • delete old file upon successful completion

    


  


  • keep the same file name

    


  


  • if it finds an error, just skip the file and keep going - don't stop the process

    


  


  


  Any help with any and/or all of these bits to cobble something together that'll work would be most appreciated.