Recherche avancée

Sur d’autres sites (10147)

• Convert a file using FFMPEG and upload to AWS S3 Nodejs

  6 mai 2020, par codernoob8

  Hey everyone so quick question I want to allow a user to upload a WebM file and convert it using FFmpeg to mp4. I am using Nodejs for the backend and already have a route that uploads files to Amazon S3 file storage. But let's say I wanted to send that file and not store it anywhere but convert it to mp4 from the request itself is that possible ? If not is it possible to take an s3 file URL and convert it to mp4 ? Can anybody point me in the right direction as to what is possible and the best way to do this ?

  



  basically all I want to do is

  



  const objectUrl = createObjectURL(Blob);
ffmpeg -i objectURL S3OutputLocation


  



  or

  



  ffmpeg -i myS3InputLocation myS3OutputLocation


  


• How to send ffmpeg based HTTP stream to CloudFront [on hold]

  5 octobre 2017, par Tarun Maheshwari

  I have a live streaming server, where media is available as HTTP / RTMP / HLS format.
  I am able to access it and play from my desktop using following links.

   rtmp://52.xx.xx.192/live/tarun1 (RTMP)
  
   http://52.xx.xx.192:8080/hls/movie.m3u8 (HLS)
  
   http://52.xx.xx.190:7090/stream (HTTP)

  I want to forward any of the above streams to CloudFront with these steps.

• 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.